I had this working perfectly then all of a sudden I couldn’t connect. I am using the latest qpkg and have tried 4.3.3.0154 and the latest firmware. Any ideas?
I tried deleting RoonServer App and reloading it. The version is 2017-02-02. I can see the qnap from my devices. The address is 10.1.10.12. I am getting an occasional DNS error. I can’t find anything wrong with the IP address or the default gateway. I’m certainly no expert though. I also tried upgrading to the current firmware in qnap and then back to the 4.3.3.0154 version that had been working for me.
Hi @Henry_Lindsey,
Where and when are you getting a DNS error?
Can you download this txt-file and place it in the RoonServer shared folder of your QNAP (next to the RoonServer and RAATServer folder)?
It should look like this afterwards:
Then stop and start RoonServer in the AppCenter again and check that textfile again. If it has any content now, please forward it to me.
24.05.17-19:07:46 --- Starting RoonServer ...
24.05.17-19:07:46 --- ROON_DATABASE_DIR: /share/CACHEDEV2_DATA/RoonServer
24.05.17-19:07:46 --- ROON_DIR: /share/CACHEDEV1_DATA/.qpkg/RoonServer
24.05.17-19:07:46 --- Model: TVS-471
24.05.17-19:07:46 --- QNAP Serial: Q172I04948
24.05.17-19:07:46 --- Architecture: x86_64
24.05.17-19:07:46 --- QTS Version: 4.3.3
24.05.17-19:07:46 --- PKG Version: 2017-02-02
24.05.17-19:07:46 --- Hostname: NAS10D991
24.05.17-19:07:46 --- MTU: 1500 1500 1500
24.05.17-19:07:46 --- Loading additional 64-bit libs: false
24.05.17-19:07:46 --- ROON_DEBUG_ARGS:
24.05.17-19:07:46 --- RoonServer PID: 27663
########## Installed RoonServer Version ##########
100300223
1.3 (build 223) stable
stable
##################################################
e[0;37;1me[0;0m00:00:00.000 e[0;31;1mError: Failed to acquire exclusive locke[0;0m
/share/CACHEDEV1_DATA/.qpkg/RoonServer/RoonServer/start.sh: line 34: kill: (27677) - No such process
I was getting the DNS error when I would first open 4.3.3 and click on AppCenter. I am no longer getting an error message today.
This error message is normally displayed if either RoonServer is already running, or if it has no write access to its tmp directory. Are you familiar with ssh?
No
I wonder what changed. This was working perfectly.
I was just reading about ssh. What do you suggest?
Just sent you a PM.
I sorry, but where do I go to get private messages on this site
Chris. I just sent you a PM
Just an update for others who might read this: It is very likely it was caused by different subnets of the remote and core.
Maybe @Henry_Lindsey can give an update when he tried to have all devices in the same subnet range.
Thanks to Chris this was resolved. Because of a lightning strike and some rewiring of my network my wifi was on a different subnet. Chris spotted this problem and I resolved it quickly. Now everything is working perfectly. Thanks Chris.
1 Like