Roon Core on QNAP does not start anymore

Support
1

Roon Core Machine

Installed on QNAP TS-451S
Version : 2.0 (build 1234) production
QPKG-Version : 2021-10-03

Networking Gear & Setup Details

No VPN, Cisco Router 897, everything wired no Wireless

Connected Audio Devices

Aqua LinQ, Auralic Altair G2.1 Streamer, Sonos Play 1, MacBook Pro with Roon Edge

Number of Tracks in Library

about 10,000 tracks

Description of Issue

Hi, yesterday everything was working just fine, this morning every Roon client doesn’t connect to the Core anymore (from Macs and iOS as well). Nothing has been changed or modified in the meanwhile.

This is the log collected:

22.03.23-11:37:52 — e[0;37;1me[0;0m00:00:00.002 e[0;31mWarn: get lock file path: /tmp/.rnsgem0-e[0;0m
22.03.23-11:37:53 — Initializing
22.03.23-11:37:53 — e[0;37;1me[0;0m00:00:00.158 e[0;32mDebug: RoonServer, before attempting to start RoonAppliance binary at path: /share/CE_CACHEDEV1_DATA/.qpkg/RoonServer/RoonServer/Server/…/Appliance/RoonAppliancee[0;0m
22.03.23-11:37:53 — e[0;37;1me[0;0m00:00:00.193 e[0;32mDebug: RoonServer, after starting RoonAppliancee[0;0m
22.03.23-11:37:53 — Started
22.03.23-11:37:58 — Not responding
22.03.23-11:38:18 — e[0;37;1me[0;0m00:00:25.456 e[0;32mDebug: RoonServer, after RoonAppliance exit, exitcode: 137e[0;0m
22.03.23-11:38:18 — Error
22.03.23-11:38:20 — e[0;37;1me[0;0m00:00:27.456 e[0;32mDebug: RoonServer, before attempting to start RoonAppliance binary at path: /share/CE_CACHEDEV1_DATA/.qpkg/RoonServer/RoonServer/Server/…/Appliance/RoonAppliancee[0;0m
22.03.23-11:38:29 — Initializing
22.03.23-11:38:29 — e[0;37;1me[0;0m00:00:27.486 e[0;32mDebug: RoonServer, after starting RoonAppliancee[0;0m
22.03.23-11:38:29 — Started
22.03.23-11:38:29 — Not responding
22.03.23-11:38:40 — e[0;37;1me[0;0m00:00:47.122 e[0;32mDebug: RoonServer, after RoonAppliance exit, exitcode: 137e[0;0m
22.03.23-11:38:40 — Error
22.03.23-11:38:42 — Initializing
22.03.23-11:38:42 — e[0;37;1me[0;0m00:00:49.129 e[0;32mDebug: RoonServer, before attempting to start RoonAppliance binary at path: /share/CE_CACHEDEV1_DATA/.qpkg/RoonServer/RoonServer/Server/…/Appliance/RoonAppliancee[0;0m
22.03.23-11:38:42 — e[0;37;1me[0;0m00:00:49.136 e[0;32mDebug: RoonServer, after starting RoonAppliancee[0;0m
22.03.23-11:38:42 — Started
22.03.23-11:38:43 — Not responding
22.03.23-11:38:58 — e[0;37;1me[0;0m00:01:05.766 e[0;32mDebug: RoonServer, after RoonAppliance exit, exitcode: 137e[0;0m
22.03.23-11:38:58 — Error
22.03.23-11:39:00 — e[0;37;1me[0;0m00:01:07.766 e[0;32mDebug: RoonServer, before attempting to start RoonAppliance binary at path: /share/CE_CACHEDEV1_DATA/.qpkg/RoonServer/RoonServer/Server/…/Appliance/RoonAppliancee[0;0m
22.03.23-11:39:00 — Initializing
22.03.23-11:39:00 — e[0;37;1me[0;0m00:01:07.798 e[0;32mDebug: RoonServer, after starting RoonAppliancee[0;0m
22.03.23-11:39:00 — Started
22.03.23-11:39:03 — Not responding
22.03.23-11:39:16 — e[0;37;1me[0;0m00:01:24.058 e[0;32mDebug: RoonServer, after RoonAppliance exit, exitcode: 137e[0;0m
22.03.23-11:39:17 — Error
22.03.23-11:39:18 — e[0;37;1me[0;0m00:01:26.059 e[0;32mDebug: RoonServer, before attempting to start RoonAppliance binary at path: /share/CE_CACHEDEV1_DATA/.qpkg/RoonServer/RoonServer/Server/…/Appliance/RoonAppliancee[0;0m
22.03.23-11:39:19 — Initializing
22.03.23-11:39:19 — e[0;37;1me[0;0m00:01:26.076 e[0;32mDebug: RoonServer, after starting RoonAppliancee[0;0m
22.03.23-11:39:19 — Started
22.03.23-11:39:23 — Not responding
22.03.23-11:39:38 — e[0;37;1me[0;0m00:01:45.969 e[0;32mDebug: RoonServer, after RoonAppliance exit, exitcode: 137e[0;0m
22.03.23-11:39:38 — Error
22.03.23-11:39:40 — Initializing
22.03.23-11:39:40 — e[0;37;1me[0;0m00:01:47.970 e[0;32mDebug: RoonServer, before attempting to start RoonAppliance binary at path: /share/CE_CACHEDEV1_DATA/.qpkg/RoonServer/RoonServer/Server/…/Appliance/RoonAppliancee[0;0m
22.03.23-11:39:40 — e[0;37;1me[0;0m00:01:47.990 e[0;32mDebug: RoonServer, after starting RoonAppliancee[0;0m
22.03.23-11:39:40 — Started
22.03.23-11:39:43 — Not responding
22.03.23-11:40:02 — e[0;37;1me[0;0m00:02:09.949 e[0;32mDebug: RoonServer, after RoonAppliance exit, exitcode: 137e[0;0m
22.03.23-11:40:02 — Error
22.03.23-11:40:04 — e[0;37;1me[0;0m00:02:11.950 e[0;32mDebug: RoonServer, before attempting to start RoonAppliance binary at path: /share/CE_CACHEDEV1_DATA/.qpkg/RoonServer/RoonServer/Server/…/Appliance/RoonAppliancee[0;0m
22.03.23-11:40:04 — Initializing
22.03.23-11:40:04 — e[0;37;1me[0;0m00:02:11.963 e[0;32mDebug: RoonServer, after starting RoonAppliancee[0;0m
22.03.23-11:40:04 — Started
22.03.23-11:40:08 — Not responding

Any help will be appreciated. Thank you

2

03/22 11:40:05 Info: Starting RoonServer v2.0 (build 1234) production on linuxx64
03/22 11:40:05 Info: Local time is 3/22/2023 11:40:05 AM, UTC time is 3/22/2023 10:40:05 AM
03/22 11:40:05 Trace: [roondns] loaded 30 last-known-good entries
03/22 11:40:05 Trace: Checking if we are already running
03/22 11:40:05 Warn: get lock file path: /tmp/.rnsems0-roon
03/22 11:40:05 Trace: Nope, we are the only one running
03/22 11:40:05 Info: Is 64 bit? True
03/22 11:40:05 Info: Command Line Argument: -watchdogport=44171
03/22 11:40:05 Trace: [realtime] fetching time from NTP server
03/22 11:40:05 Trace: [realtime] Got time from NTP: 3/22/2023 10:40:05 AM UTC (3888470405572ms)
03/22 11:40:05 Trace: [realtime] Updated clock skew to -00:00:00.3289605 (-328.9605ms)

3

Fixed rebooting the NAS, thank you.

4

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