Mauro 4 Posted February 1, 2019 Report Share Posted February 1, 2019 Hello @miji2, @rlt We are sorry to hear these bad news from you, i checked the specs of both your NAS and you have the same cpu architecture of our HS-251, where we can't reproduce this issue. I sent you a private message to collect informations to solve this issue. Quote Link to post Share on other sites
zeeohsix 0 Posted July 24, 2019 Report Share Posted July 24, 2019 I hate to resurrect the dead, but I am seeing the same issue with my QNAP TS-251+. domotz_2.4.3.2_x86_64.qpkg on QTS 4.4.1 is sticking at 75 and 80 percent simultaneously, but in different GUI areas. (app center vs notification center) Quote Link to post Share on other sites
Mauro 4 Posted July 30, 2019 Report Share Posted July 30, 2019 On 7/24/2019 at 10:28 AM, zeeohsix said: I hate to resurrect the dead, but I am seeing the same issue with my QNAP TS-251+. domotz_2.4.3.2_x86_64.qpkg on QTS 4.4.1 is sticking at 75 and 80 percent simultaneously, but in different GUI areas. (app center vs notification center) Hi We are sorry for your issue, i would ask you to manually try to install this package <link_removed> Qnap is reviewing this version and should be ready on the store very soon, however if you can download and try would be good. About the percentage consider that on that amount the real installation procedure is finished and qts is validating a normal domotz agent startup, considering this and the nature of our software is hard to guess what went wrong. Just in case the package above can't fix your problem could you help us troubleshooting your problem sending us logs or execute some command on your NAS? Thanks a lot Mauro Quote Link to post Share on other sites
Mauro 4 Posted August 9, 2019 Report Share Posted August 9, 2019 hi @rlt, @zeeohsix do you have news about this problem? If the app stuck again on installation you can try this: download the domotz agent from the store or from one of our links and start installation wait up 75% of installation and login into the NAS through ssh and write this command without ticks 'echo "3000" > /tmp/domotz_listener.port' installation should finish without problems. let us know your thoughts Quote Link to post Share on other sites
colotti 0 Posted August 12, 2019 Report Share Posted August 12, 2019 (edited) Same issue hangs at 80% on a TVS-671 running QTS 4.3.6 wanted to try it our with my Nuvo and other gear. Using the echo command above install finished, but getting connection refused when you open the app. Edited August 12, 2019 by colotti Quote Link to post Share on other sites
colotti 0 Posted August 12, 2019 Report Share Posted August 12, 2019 NMAP shows nothing open on port 3000 but QNAP shows it installed and running, also no port 3000 in nstat on the qnap Nmap scan report for 192.168.100.2 Host is up (0.0053s latency). Not shown: 985 closed ports PORT STATE SERVICE 22/tcp open ssh 80/tcp open http 139/tcp open netbios-ssn 445/tcp open microsoft-ds 514/tcp open shell 548/tcp open afp 631/tcp open ipp 2049/tcp open nfs 6789/tcp open ibm-db2-admin 8080/tcp open http-proxy 8088/tcp open radan-http 8089/tcp open unknown 8899/tcp open ospf-lite 30000/tcp open ndmps 32768/tcp open filenet-tms Nmap done: 1 IP address (1 host up) scanned in 1.97 seconds Looking at the status logs it says it's starting the listener on port 3000 but if you stop and start the app again it says it was never running 2019-08-12 11:34:22 [1308] LOG: Pid file doesn't exist, program probably stopped 2019-08-12 11:34:22 [1308] LOG: +--- Start domotz ---+ 2019-08-12 11:34:22 [1308] LOG: Link static content from /share/CACHEDEV1_DATA/.qpkg/domotz/lib/node_modules/domotz-remote-pawn/data 2019-08-12 11:34:22 [1308] LOG: Listener started on port: 3000 2019-08-12 11:34:22 [1308] LOG: +----------------------+ Quote Link to post Share on other sites
colotti 0 Posted August 12, 2019 Report Share Posted August 12, 2019 agent version from QNAP store is domotz-qnap-x64-4.3.0-2.4.3-2.3.1-b001-0066.zip Quote Link to post Share on other sites
Mauro 4 Posted August 12, 2019 Report Share Posted August 12, 2019 Thanks a lot @colotti for your troubleshooting. If you can, would be very useful to have the output of domotz_node from the domotz folder that should be: /share/CACHEDEV1_DATA/.qpkg/domotz run the following commands: source /etc/domotz.env #to load our environment variables cd bin/ && ./domotz_node do you receive a segmentation fault or some other errors? or the node interpreter is loaded well (in the case you are not familiar with nodejs in order to exit form the interpreter run a double ctrl-c). thanks a lot Quote Link to post Share on other sites
colotti 0 Posted August 12, 2019 Report Share Posted August 12, 2019 @Mauro [/share/CACHEDEV1_DATA/.qpkg/domotz] # source /etc/domotz.env -sh: /etc/domotz.env: No such file or directory [/share/CACHEDEV1_DATA/.qpkg/domotz] # [/share/CACHEDEV1_DATA/.qpkg/domotz] # cd bin/ && ./domotz_node Segmentation fault 4 hours ago, Mauro said: I also noticed this: [/share/CACHEDEV1_DATA/.qpkg/domotz/bin] # cat /var/log/domotz/domotz_lifecycle.log 2019-08-12 16:02:24 [4659] LOG: +--- Start domotz installation ---+ 2019-08-12 16:02:24 [4659] LOG: Link static content from /share/CACHEDEV1_DATA/.qpkg/domotz/lib/node_modules/domotz-remote-pawn/data 2019-08-12 16:02:24 [4659] LOG: +--- Finish domotz installation ---+ 2019-08-12 16:02:24 [4659] LOG: +--- Start domotz restore ---+ 2019-08-12 16:02:24 [4659] LOG: Restore data from /share/CACHEDEV1_DATA/.qpkg/domotz/qnap to /share/CACHEDEV1_DATA/.qpkg/domotz/etc 2019-08-12 16:02:24 [4659] LOG: Remove temporary directory: /share/CACHEDEV1_DATA/.qpkg/domotz/qnap 2019-08-12 16:02:24 [4659] LOG: +--- Finish domotz restore ---+ The app was installed removed and re-installed multiple times as well. I am also running network port teams but other apps run fine with those. Quote Link to post Share on other sites
Mauro 4 Posted August 13, 2019 Report Share Posted August 13, 2019 Hi @colotti First of all i want to say thanks to you to help us troubleshooting this problem, as you can understand there are a lot of variable and sometimes is hard to find problem/solution without customer help. I'm sorry but i have to ask another help trying this package: <link_removed> We tried to replicate your problem and fix it and seems to work however we couldn't guarantee with 100% that this fix your problem also. Thanks a lot Mauro Quote Link to post Share on other sites
miji2 3 Posted August 13, 2019 Report Share Posted August 13, 2019 new qpkg still gets stuck at 75% echoing "3000" to /tmp/domotz_listener.port bypasses installation validation but app will not run afterward. from /var/log/domotz/domotz_lifecycle.log 2019-08-13 17:18:57 [2000] LOG: +--- Start domotz backup ---+ 2019-08-13 17:18:57 [2000] LOG: Temporary saving configuration files in /share/CACHEDEV1_DATA/.qpkg/domotz/qnap 2019-08-13 17:18:57 [2000] LOG: +--- Finish domotz backup ---+ 2019-08-13 17:19:35 [2000] LOG: +--- Start domotz installation ---+ 2019-08-13 17:19:35 [2000] LOG: Link static content from /share/CACHEDEV1_DATA/.qpkg/domotz/lib/node_modules/domotz-remote-pawn/data 2019-08-13 17:19:35 [2000] LOG: +--- Finish domotz installation ---+ 2019-08-13 17:19:35 [2000] LOG: +--- Start domotz restore ---+ 2019-08-13 17:19:35 [2000] LOG: Restore data from /share/CACHEDEV1_DATA/.qpkg/domotz/qnap to /share/CACHEDEV1_DATA/.qpkg/domotz/etc 2019-08-13 17:19:35 [2000] LOG: Skip domotz.env 2019-08-13 17:19:35 [2000] LOG: Remove temporary directory: /share/CACHEDEV1_DATA/.qpkg/domotz/qnap 2019-08-13 17:19:35 [2000] LOG: +--- Finish domotz restore ---+ and running domotz_node manually I get [~] # source /etc/domotz.env [~] # cd /share/CACHEDEV1_DATA/.qpkg/domotz [/share/CACHEDEV1_DATA/.qpkg/domotz] # cd bin/ && ./domotz_node ./domotz_node: relocation error: /opt/lib/libpthread.so.0: symbol __tunable_get_val, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference [/share/CACHEDEV1_DATA/.qpkg/domotz/bin] # One of those days I will reflash to QNAP factory firmware ... for now running domotz on backup TerraMster NAS and it works great. Quote Link to post Share on other sites
Mauro 4 Posted August 14, 2019 Report Share Posted August 14, 2019 hi @miji2 In order to run domotz_node manually your should first run cd /share/CACHEDEV1_DATA/.qpkg/domotz/bin source ../etc/domotz.env ./domotz_node The error should change (however i'm not sure this package can fix your problem) and f we are lucky you can give us the output of where it fail. @colotti error seems to be different i'm still convinced that the new package can fix it. Thanks a lot Quote Link to post Share on other sites
colotti 0 Posted August 14, 2019 Report Share Posted August 14, 2019 I’ll give it a try today. Worst case I can use Container Station and run the Docker version of the agent to test. @Mauro still no Bueno. At this point if I am going to try your service I will have to find another agent option with Docker of other. I wish I could help more but this is the only QPKG I seem to have issues with. Quote Link to post Share on other sites
miji2 3 Posted August 22, 2019 Report Share Posted August 22, 2019 @Mauro I get same error with internal domotz. env ./domotz_node: relocation error: /opt/lib/libpthread.so.0: symbol __tunable_get_val, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference Quote Link to post Share on other sites
BollocksToBrexit 0 Posted August 28, 2019 Report Share Posted August 28, 2019 Just adding my three ha'porth - having exactly the same issues. I have installed the latest package per Mauro's 13th August post above but all my errors correspond exactly to those others are seeing. My NAS is a Qnap TS-453 Pro. Hope there is a resolution on its way! Marc Quote Link to post Share on other sites
Mauro 4 Posted August 29, 2019 Report Share Posted August 29, 2019 Hi @BollocksToBrexit We are sorry to know that you also have a problem with out package and Qnap x64 NAS. The problem is not so delimited because the error you have may have many causes. In order to debug it i need to create a similar environment and debug it. Would be very useful for us to have more informations about your NAS could you run this script inside your NAS after ssh into it and copy here the output (or privately to me), simply running the command below? curl -s -L https://domotz-exchange.s3.amazonaws.com/report.sh | bash You can check the script by yourself is just a report about your Qnap os like libraries versions and model and build number. No privacy problems, don't worry thanks a lot Mauro Quote Link to post Share on other sites
BollocksToBrexit 0 Posted August 29, 2019 Report Share Posted August 29, 2019 Hi Mauro Thanks for getting back to me. Here is the output: ********************* ** QNAP NAS Report ** ********************* NAS Model: TS-453 Pro Firmware: 4.4.1 Build 20190816 System Name: BigCountry Workgroup: NAS Base Directory: /share/CACHEDEV1_DATA NAS IP address: 10.0.5.1 127.0.0.1 10.0.3.1 192.168.1.60 Default Gateway Device: inet addr:10.0.5.1 Bcast:10.0.5.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:119901 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:12783742 (12.1 MiB) UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Memory:d0a00000-d0a7ffff UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Memory:d0900000-d097ffff UP BROADCAST RUNNING MULTICAST MTU:4074 Metric:1 RX packets:21518183 errors:0 dropped:4007 overruns:0 frame:0 TX packets:6539933 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:24443760248 (22.7 GiB) TX bytes:2680369536 (2.4 GiB) Memory:d0700000-d077ffff UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Memory:d0600000-d067ffff lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:1434189 errors:0 dropped:0 overruns:0 frame:0 TX packets:1434189 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:888387480 (847.2 MiB) TX bytes:888387480 (847.2 MiB) inet addr:10.0.3.1 Bcast:10.0.3.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:118073 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:12619241 (12.0 MiB) inet addr:192.168.1.60 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:4074 Metric:1 RX packets:8681515 errors:0 dropped:0 overruns:0 frame:0 TX packets:5362887 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:23384217425 (21.7 GiB) TX bytes:2603526508 (2.4 GiB) DNS Nameserver(s):127.0.1.1 Base directory: /share/CACHEDEV1_DATA/.qpkg Domotz informations: DPLATFORM=qnap DARCHITECTURE=x64 DTOOLCHAIN=4.3.0 DVERSION=2.4.9-test DPREFIX=domotz_ DTMPDIR=/tmp/domotz UPDATER_ENABLED=1 nodeJS ldd info: linux-vdso.so.1 (0x00007ffd03915000) libz.so => /opt/lib/libz.so (0x00007fc78a48d000) libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0x00007fc789e32000) libssl.so.1.0.0 => /lib/libssl.so.1.0.0 (0x00007fc789bb9000) libdl.so.2 => /opt/lib/libdl.so.2 (0x00007fc78a47d000) librt.so.1 => /opt/lib/librt.so.1 (0x00007fc78a473000) libstdc++.so.6 => /opt/lib/libstdc++.so.6 (0x00007fc78a2e9000) libm.so.6 => /opt/lib/libm.so.6 (0x00007fc789a26000) libgcc_s.so.1 => /opt/lib/libgcc_s.so.1 (0x00007fc78980f000) libpthread.so.0 => /opt/lib/libpthread.so.0 (0x00007fc7895f1000) libc.so.6 => /opt/lib/libc.so.6 (0x00007fc789241000) /lib64/ld-linux-x86-64.so.2 (0x00007fc78a287000) lib content: engines etc forever libboost_chrono.so libboost_chrono.so.1.54.0 libboost_date_time.so libboost_date_time.so.1.54.0 libboost_filesystem.so libboost_filesystem.so.1.54.0 libboost_iostreams.so libboost_iostreams.so.1.54.0 libboost_program_options.so libboost_program_options.so.1.54.0 libboost_regex.so libboost_regex.so.1.54.0 libboost_serialization.so libboost_serialization.so.1.54.0 libboost_signals.so libboost_signals.so.1.54.0 libboost_system.so libboost_system.so.1.54.0 libboost_thread.so libboost_thread.so.1.54.0 libboost_wserialization.so libboost_wserialization.so.1.54.0 libcrypto.so libcrypto.so.1.0.0 libcurl.so libcurl.so.4 libcurl.so.4.4.0 libevent-2.2.so.1 libevent-2.2.so.1.0.0 libevent_core-2.2.so.1 libevent_core-2.2.so.1.0.0 libevent_core.so libevent_extra-2.2.so.1 libevent_extra-2.2.so.1.0.0 libevent_extra.so libevent_openssl-2.2.so.1 libevent_openssl-2.2.so.1.0.0 libevent_openssl.so libevent_pthreads-2.2.so.1 libevent_pthreads-2.2.so.1.0.0 libevent_pthreads.so libevent.so libGeoIP.so libGeoIP.so.1 libGeoIP.so.1.6.9 libmeasurement_kit-0.4.3.so.0 libmeasurement_kit-0.4.3.so.0.0.0 libmeasurement_kit.so libndt.so libssl.so libssl.so.1.0.0 libz.so libz.so.1 libz.so.1.2.8 node_modules [~] # Quote Link to post Share on other sites
Adam-UK 0 Posted September 14, 2019 Report Share Posted September 14, 2019 I have the same issue on my QNAP TVS-1282 (stuck at 75%/80% installing) for the version the AppCentre and the links in this post too. Any help? Quote Link to post Share on other sites
zeeohsix 0 Posted September 19, 2019 Report Share Posted September 19, 2019 @Mauro Mine is still stuck as well. I've tried both packages with no luck. See below for output of commands mentioned in this thread. If you have some other commands you'd like me to run, let me know. Thanks! ********************* ** QNAP NAS Report ** ********************* NAS Model: TS-251+ Firmware: 4.4.1 Build 20190918 System Name: HOME-NAS-01 Workgroup: NAS Base Directory: /share/CACHEDEV1_DATA NAS IP address: 10.0.50.1 10.0.10.10 127.0.0.1 10.0.30.1 Default Gateway Device: inet addr:10.0.50.1 Bcast:10.0.50.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:2366 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:213981 (208.9 KiB) inet addr:10.0.10.10 Bcast:10.0.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:36041 errors:0 dropped:0 overruns:0 frame:0 TX packets:19242 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11136284 (10.6 MiB) TX bytes:7703133 (7.3 MiB) Memory:90700000-9077ffff UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Memory:90600000-9067ffff lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:44451 errors:0 dropped:0 overruns:0 frame:0 TX packets:44451 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:18167070 (17.3 MiB) TX bytes:18167070 (17.3 MiB) inet addr:10.0.30.1 Bcast:10.0.30.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:2366 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:213975 (208.9 KiB) DNS Nameserver(s):127.0.1.1 Base directory: /share/CACHEDEV1_DATA/.qpkg Domotz informations: DPLATFORM=qnap DARCHITECTURE=x64 DTOOLCHAIN=4.3.0 DVERSION=2.4.9-test DPREFIX=domotz_ DTMPDIR=/tmp/domotz UPDATER_ENABLED=1 nodeJS ldd info: linux-vdso.so.1 (0x00007ffe925ca000) libz.so => /lib/libz.so (0x00007f5c6f95c000) libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0x00007f5c6f501000) libssl.so.1.0.0 => /lib/libssl.so.1.0.0 (0x00007f5c6f287000) libdl.so.2 => /opt/lib/libdl.so.2 (0x00007f5c6f083000) librt.so.1 => /opt/lib/librt.so.1 (0x00007f5c6ee7b000) libstdc++.so.6 => /opt/lib/libstdc++.so.6 (0x00007f5c6eafc000) libm.so.6 => /opt/lib/libm.so.6 (0x00007f5c6e7f7000) libgcc_s.so.1 => /opt/lib/libgcc_s.so.1 (0x00007f5c6e5e0000) libpthread.so.0 => /opt/lib/libpthread.so.0 (0x00007f5c6e3c2000) libc.so.6 => /opt/lib/libc.so.6 (0x00007f5c6e023000) /lib64/ld-linux-x86-64.so.2 (0x00007f5c6fb76000) lib content: engines etc forever libboost_chrono.so libboost_chrono.so.1.54.0 libboost_date_time.so libboost_date_time.so.1.54.0 libboost_filesystem.so libboost_filesystem.so.1.54.0 libboost_iostreams.so libboost_iostreams.so.1.54.0 libboost_program_options.so libboost_program_options.so.1.54.0 libboost_regex.so libboost_regex.so.1.54.0 libboost_serialization.so libboost_serialization.so.1.54.0 libboost_signals.so libboost_signals.so.1.54.0 libboost_system.so libboost_system.so.1.54.0 libboost_thread.so libboost_thread.so.1.54.0 libboost_wserialization.so libboost_wserialization.so.1.54.0 libcrypto.so libcrypto.so.1.0.0 libcurl.so libcurl.so.4 libcurl.so.4.4.0 libevent-2.2.so.1 libevent-2.2.so.1.0.0 libevent_core-2.2.so.1 libevent_core-2.2.so.1.0.0 libevent_core.so libevent_extra-2.2.so.1 libevent_extra-2.2.so.1.0.0 libevent_extra.so libevent_openssl-2.2.so.1 libevent_openssl-2.2.so.1.0.0 libevent_openssl.so libevent_pthreads-2.2.so.1 libevent_pthreads-2.2.so.1.0.0 libevent_pthreads.so libevent.so libGeoIP.so libGeoIP.so.1 libGeoIP.so.1.6.9 libmeasurement_kit-0.4.3.so.0 libmeasurement_kit-0.4.3.so.0.0.0 libmeasurement_kit.so libndt.so libssl.so libssl.so.1.0.0 libz.so libz.so.1 libz.so.1.2.8 node_modules ------------------------------------------------------------------------------------- [~] # cd /share/CACHEDEV1_DATA/.qpkg/domotz/bin [/share/CACHEDEV1_DATA/.qpkg/domotz/bin] # [/share/CACHEDEV1_DATA/.qpkg/domotz/bin] # source ../etc/domotz.env [/share/CACHEDEV1_DATA/.qpkg/domotz/bin] # [/share/CACHEDEV1_DATA/.qpkg/domotz/bin] # ./domotz_node Segmentation fault ---------------------------------------------------------------------------------------- [/share/CACHEDEV1_DATA/.qpkg/domotz] # source /etc/domotz.env [/share/CACHEDEV1_DATA/.qpkg/domotz] # cd bin/ && ./domotz_node Segmentation fault Quote Link to post Share on other sites
miji2 3 Posted September 19, 2019 Report Share Posted September 19, 2019 I'll let @Mauro comment on this, but there seems to be some hope as I got my client up and running and successfully registered. 1 Quote Link to post Share on other sites
Mauro 4 Posted September 20, 2019 Report Share Posted September 20, 2019 Hi @zeeohsix As @miji2 wrote we where working on a fix about this problem. It seems to be related to Entware or similar software that overwrite libs in the NAS. You can try this new package https://domotz-exchange.s3.amazonaws.com/openvpn-beta/domotz-qnap-x64-4.3.0-2.5.0-2.7.2-b001-test.qpkg The package is a beta version but the base code is stable and we are spreading it on all the platform. If you have time please test it and give us a feedback so we can submit it to qnap market. Mauro Quote Link to post Share on other sites
zeeohsix 0 Posted September 20, 2019 Report Share Posted September 20, 2019 @Mauro domotz-qnap-x64-4.3.0-2.5.0-2.7.2-b001-test.qpkg appears to be working for me. If I run into any isssues, I'll post here. Thanks! Quote Link to post Share on other sites
Mauro 4 Posted September 20, 2019 Report Share Posted September 20, 2019 @zeeohsix thanks for the feedback, the version you installed shouldn't give you any problem for the future (🤞). i would say that this version that you guys tested, can be used by all the users with this issue until new version will be available on qnap store https://domotz-exchange.s3.amazonaws.com/openvpn-beta/domotz-qnap-x64-4.3.0-2.5.0-2.7.2-b001-test.qpkg thanks to all for the help 1 Quote Link to post Share on other sites
colotti 0 Posted December 16, 2020 Report Share Posted December 16, 2020 On 9/20/2019 at 2:37 PM, Mauro said: @zeeohsix thanks for the feedback, the version you installed shouldn't give you any problem for the future (🤞). i would say that this version that you guys tested, can be used by all the users with this issue until new version will be available on qnap store https://domotz-exchange.s3.amazonaws.com/openvpn-beta/domotz-qnap-x64-4.3.0-2.5.0-2.7.2-b001-test.qpkg thanks to all for the help Any idea why the qnap store has removed the app completely? On 9/20/2019 at 2:37 PM, Mauro said: @zeeohsix thanks for the feedback, the version you installed shouldn't give you any problem for the future (🤞). i would say that this version that you guys tested, can be used by all the users with this issue until new version will be available on qnap store https://domotz-exchange.s3.amazonaws.com/openvpn-beta/domotz-qnap-x64-4.3.0-2.5.0-2.7.2-b001-test.qpkg thanks to all for the help the package has been completely removed from the qnap store. I can’t find it any longer. Any ideas why it’s not there for QTS 4.5.1 but is for others? Quote Link to post Share on other sites
colotti 0 Posted December 16, 2020 Report Share Posted December 16, 2020 I guess that's why...the QPKG above does not work either... App Center App Installation [App Center] Failed to install Domotz Network Monitoring. Downgrade QTS to 4.4.9 or an older compatible version. Quote Link to post Share on other sites
(1)(1)(1)(1)(1)(1).jpg.7dcdeb3fb90919aa2df390a4f448ac4b.thumb.jpg.77bf24b1396f1fd80d63b164713f41ff.jpg)
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.