Suddenly clients can't connect any more

All the sudden non of my clients can connect to core. I’m running it on Ubuntu. Here’s the status on the server:

@zulu:/var/roon/RoonServer/Logs$ systemctl status roonserver
● roonserver.service - RoonServer
Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-05-12 23:09:53 UTC; 18min ago
Main PID: 6677 (start.sh)
Tasks: 41 (limit: 4915)
Memory: 5.7G
CGroup: /system.slice/roonserver.service
├─6677 /bin/bash /opt/RoonServer/start.sh
├─6682 /opt/RoonServer/RoonDotnet/RoonServer RoonServer.dll
├─8644 /opt/RoonServer/RoonDotnet/RoonAppliance RoonAppliance.dll -watchdogport=39761
└─8645 /opt/RoonServer/Server/processreaper 8644

May 12 23:27:35 zulu start.sh[6677]: Started
May 12 23:27:38 zulu start.sh[6677]: Not responding
May 12 23:27:53 zulu start.sh[6677]: 00:18:00.275 Debug: PathForResource, filename: …/.update
May 12 23:27:53 zulu start.sh[6677]: 00:18:00.275 Debug: PathForResource, candidate: /opt/RoonServer/Server/…/.update
May 12 23:27:53 zulu start.sh[6677]: Error
May 12 23:27:55 zulu start.sh[6677]: 00:18:02.275 Debug: PathForResource, filename: …/Appliance/RoonAppliance
May 12 23:27:55 zulu start.sh[6677]: 00:18:02.275 Debug: PathForResource, candidate: /opt/RoonServer/Server/…/Appliance/RoonAppliance
May 12 23:27:55 zulu start.sh[6677]: Initializing
May 12 23:27:55 zulu start.sh[6677]: Started
May 12 23:27:58 zulu start.sh[6677]: Not responding

And, here’s what I see in the logs:

@zulu:/var/roon/RoonServer/Logs$ tail -100 RoonServer_log.txt

05/13 00:34:36 Info: Starting RoonServer v1.8 (build 943) stable on linuxx64
05/13 00:34:36 Trace: [roondns] loaded 27 last-known-good entries
05/13 00:34:36 Trace: Checking if we are already running
05/13 00:34:36 Warn: get lock file path: /tmp/.rnsems0-roon
05/13 00:34:36 Trace: Nope, we are the only one running
05/13 00:34:36 Info: Is 64 bit? True
05/13 00:34:36 Info: Command Line Argument: -watchdogport=39761
05/13 00:34:36 Trace: [realtime] fetching time from NTP server
05/13 00:34:36 Trace: [realtime] Got time from NTP: 5/13/2022 12:34:36 AM (3861390876260ms)
05/13 00:34:36 Trace: [realtime] Updated clock skew to -00:00:00.0153668 (-15.3668ms)
05/13 00:34:36 Trace: [ipaddresses] enumerating addresses
05/13 00:34:36 Trace: [ipaddresses] FOUND lo 127.0.0.1
05/13 00:34:36 Trace: [ipaddresses] FOUND eno1 192.168.50.66
05/13 00:34:36 Trace: [ipaddresses] SKIPPED wlp0s20f3: no ipv4
05/13 00:34:36 Trace: [ipaddresses] SKIPPED docker0: not up
05/13 00:34:37 Info: [stats] 22144mb Virtual, 828mb Physical, 568mb Managed, 93 Handles, 24 Threads

Looks like the server keeps bouncing. Any ideas where to look to figure out the problem?

My core is a NUC running Ubuntu 18.10.
Roon server is v1.8 (build 943) stable on linuxx64

Since the issue is that the server keeps dying, I don’t think the remote devices and other networking info matters much. But, I have remotes on ios, mac, and windows. Audio devices using bridge connected to mac and windows.

Hi, @Zulu,

Your topic has been moved to the support section of the forum as I think it will get more traction here.

In order for Roon’s @support team to better assist you, please provide a brief description of your current setup using this link as a guide.

Make sure to describe your network configuration/topology, including any networking hardware currently in use, so they can have a clear understanding of how your devices are communicating.

@Zulu , ssh into the server and manually restart the service from a terminal;

sudo systemctl restart roonserver.service 

I have on occasionally run into to this problem after an update on Debian.

Give it a try.

Thanks for the suggestion, Andy, I’ve restarted several times to no avail.

Is there a way to turn on additional debugging in the log file? I can see that every minute the server tries to come up but then dies and the log gets rotated, but there isn’t any useful info or error message in the log.

@Zulu have you restarted from the terminal? Not a physical restart of the machine, but just the service?

Yes. I’ve done both. Systemctl starts the roonserver, the server dies, then the system respawns it. This happens once every minute. Incidentally, it fills up /tmp with pipes and fifos, 4 files per minute.

What part does docker0 play in your setup?

Not entirely sure, must have been pulled in by some package or upgrade. Docker0 is actually UP but not RUNNING (according to ifconfig), if that makes any difference.
Update: I went ahead and completely removed docker as well as the docker0 interface. Problem remains.

Don’t know, I have never used Docker knowingly. But it is being reported by your Roon log.