Roon client won't connect anymore. Help

Support
22

I looked at the process ID of the RoonServer on my NAS and ran lsof -p PID against this as well as looking for what was listening on port 9003 which I also think is the server listening port. This shows the PID of the RAATServer. Output below and all seems to look ok.

[~] # lsof -p 31383
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
start.sh 31383 admin cwd DIR 0,15 540 2247 /
start.sh 31383 admin rtd DIR 0,15 540 2247 /
start.sh 31383 admin txt REG 0,15 951968 6016 /bin/sh
start.sh 31383 admin mem REG 0,15 51624 7693 /lib/libnss_files-2.21.so
start.sh 31383 admin mem REG 0,15 47512 7769 /lib/libnss_nis-2.21.so
start.sh 31383 admin mem REG 0,15 88928 7697 /lib/libnsl-2.21.so
start.sh 31383 admin mem REG 0,15 31480 7778 /lib/libnss_compat-2.21.so
start.sh 31383 admin mem REG 0,15 1706000 7634 /lib/libc-2.21.so
start.sh 31383 admin mem REG 0,15 14560 7767 /lib/libdl-2.21.so
start.sh 31383 admin mem REG 0,15 144904 8140 /lib/ld-2.21.so
start.sh 31383 admin mem REG 0,15 1607712 45259 /usr/lib/locale/locale-archive
start.sh 31383 admin 0r CHR 1,3 0t0 1034 /dev/null
start.sh 31383 admin 1w FIFO 0,9 0t0 16498632 pipe
start.sh 31383 admin 2u CHR 1,3 0t0 1034 /dev/null
start.sh 31383 admin 3w REG 251,0 6 288096270 /share/CACHEDEV1_DATA/.qpkg/RoonServer/RoonServer.pid
start.sh 31383 admin 255r REG 251,0 1311 315031576 /share/CACHEDEV1_DATA/.qpkg/RoonServer/RoonServer/start.sh
[~] # lsof -i :9003
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
RAATServe 19225 admin 14u IPv4 40243947 0t0 UDP *:9003
RAATServe 19225 admin 16u IPv4 40243949 0t0 UDP *:9003
RAATServe 19225 admin 18u IPv4 40243951 0t0 UDP *:9003
RAATServe 19225 admin 20u IPv4 40243953 0t0 UDP *:9003
RAATServe 19225 admin 23u IPv4 40243956 0t0 UDP *:9003

23

So I got home, decided I would start the process of backing up 14TB of data to another NAS and would blast away my current config and start afresh. Yep, a little bit over the top but nothing but time to lose.

I did decide however to try 1 last time, de-authorised the machine I set up earlier and low and behold the NAS authorised and is now visible again to all client!

So it looked like de-auth-ing and re-auth-ing cleared out something in the server config that previously wasn’t quite right™

Pretty strange as I had removed and reinstalled numerous times before, and I have made zero changes to anything else.

Very random and very very frustrating but at least I am back in business.

24

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.