Roon not starting after Linux server crash and backup restore attempt (ref#LEOXNL)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Using Roon for several years. Linux server with +1000 days uptime recently crashed. Roon did not detect Sonore UPNP bridge. Tried to restore a backup. Now Roon is not starting up anymore (authorisation issues, I have a life time licsense) Please advice

Tell us about your home network

· Debian Linux Resonable sized server

This is from the logs of restoring a RoonServer backup (self made backup) one week old

01/04 20:44:44 Info: Starting RoonServer v2.57 (build 1598) production on linuxx64
01/04 20:44:44 Info: Local time is 1/4/2026 8:44:44 PM, UTC time is 1/4/2026 7:44:44 PM
01/04 20:44:44 Trace: [roondns] loaded 55 last-known-good entries
01/04 20:44:44 Debug: Init DefaultBackingApi: HttpWebRequest
01/04 20:44:44 Debug: [easyhttp] default backing API HttpClient → HttpWebRequest. This may cancel all in progress http requests
01/04 20:44:44 Trace: Checking if we are already running
01/04 20:44:44 Info: get lock file path: /tmp/.rnsems0-
01/04 20:44:44 Info: GetLockFile, fd: 61
01/04 20:44:44 Info: GetLockFile, res: 0
01/04 20:44:44 Trace: Nope, we are the only one running
01/04 20:44:44 Info: Is 64 bit? True

OK, partially solved. I was able to start the latest restore. Whole library with approx 8000 albums is perfectly restored.

My remaining problem is and this was the reason for trying a restore is that the Sonor upnp bridge which renders my Naim NDS streamer compatible with roon is not detected by roon anymore.

61.101 is the roon server, 61.27 is the upnp bridge from small green computer

tcp 0 0 0.0.0.0:3483 0.0.0.0:* LISTEN
tcp 0 0 192.168.61.101:3483 192.168.61.27:49840 ESTABLISHED
udp 0 0 0.0.0.0:3483 0.0.0.0:*

to me it appears that there is a connection already established.

However the NDS or the Sonor UPNP Bridge does not appear in Roon’s audio devices.
There is no LMS server in my network

The Sonor upnp bridge is running on Firmware 2.7.
Never had any issues.

Can you please advice how roon server will detect the upnp bridge?

Thank you.

p.s.

This is the Sonore UPNP Bridge:

https://forums.sonicorbiter.com/forum/support-for-sonore-products/quick-start-guides/22-sonoreupnp-bridge

Here are some logs from the NDS via UPNP bridge some days before the server with +1000 days uptime crashed (due to a power outage)

RoonServer_log.14.txt:12/25 23:05:13 Trace: [Naim NDS Reference] [Lossless, 16/44 TIDAL FLAC => 16/44] [12% buf] [PLAYING @ 4:11/4:26] Nothin For Nothin - The Wailers Band / The Wailers
RoonServer_log.17.txt:12/24 15:59:05 Trace: [zone Naim NDS Reference] Playing 12 Items
RoonServer_log.17.txt:12/24 15:59:05 Trace: [zone Naim NDS Reference] Selecting Source state=Paused
RoonServer_log.17.txt:12/24 15:59:05 Info: [zone Naim NDS Reference] Canceling Pending Sleep
RoonServer_log.17.txt:12/24 15:59:05 Trace: [zone Naim NDS Reference] Playing TransportItem
RoonServer_log.17.txt:12/24 15:59:05 Info: [zone Naim NDS Reference] Canceling Pending Sleep
RoonServer_log.17.txt:12/24 15:59:05 Trace: [zone Naim NDS Reference] Selecting Source state=Stopped
RoonServer_log.17.txt:12/24 15:59:05 Trace: [zone Naim NDS Reference] queue got oversized. trimming 12 items from start
RoonServer_log.17.txt:12/24 15:59:05 Debug: [zone Naim NDS Reference] Remove(12 items, for_replace=False)


Can be closed. I found an old perl based squeezebox implementation running. After termination, roon identifies the Sonos UPNP Brdge. Thank you!

Hi @kkaaii,

Thanks for the update — glad to hear you were able to identify the cause.

Since everything is now working as expected, we’ll mark this thread as resolved.

Thanks for following up and for sharing the resolution — it may help others who run into a similar situation.

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