I’ve been seeing this problem as well, the rest of the roon UI seems to still work, but the overview just sits there showing the animated logo forever. restarting the roon service on the core (Nuc running ubuntu 18.x) fixes the problem. This is with the OSX app as the remote.
Hello @SImon_Fell, when did this start happening for you?
So we can 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 we can have a clear understanding of how your devices are communicating.
Its happened a few times, the last time was Saturday afternoon 4/18. Running sudo systemctl restart roonserver on the core resolved the issue. Looking at the logs I restarted it at 16:59 (pacific time)
04/18 16:59:14 Info: Starting RoonServer v1.7 (build 528) stable on linuxx64
04/18 16:59:14 Trace: Checking if we are already running
04/18 16:59:14 Warn: get lock file path: /tmp/.rnsems0-roon
04/18 16:59:14 Trace: Nope, we are the only one running
04/18 16:59:14 Info: Is 64 bit? True
Looking at the log just before then, these look like pretty suspect items to me.
04/18 16:51:14 Debug: [easyhttp] [5393] GET to https://tidal.roonlabs.net/1/featured/new/albums?offset=0&count=30&c=tidal-us returned after 246 ms, status code: 304
04/18 16:51:14 Debug: [easyhttp] [5394] GET to https://tidal.roonlabs.net/1/featured/top/albums?offset=0&count=30&c=tidal-us returned after 258 ms, status code: 304
04/18 16:51:14 Warn: [tidal/http] GET https://api.tidal.com/v1/featured/recommended/playlists?countryCode=US&offset=0&limit=30 => Unauthorized {“status”:401,“subStatus”:11003,“userMessage”:“The token has expired. (Expired on time)”}
Looking back through the log there’s bunch of these
04/18 16:45:18 Info: [library/albumdetails] found 1 streaming service alternates
04/18 16:45:18 Debug: [easyhttp] [5383] POST to https://discover.roonlabs.net/1/profiles/59cbca49-fe07-4129-ba4e-d63c18381bf2/albums/newv2?count=400&c=tidal-us
04/18 16:45:18 Trace: [dbperf] flush 0 bytes, 0 ops in 9 ms (cumulative 864137412 bytes, 485049 ops in 141649 ms)
04/18 16:45:18 Debug: [easyhttp] [5386] POST to https://discover.roonlabs.net/1/profiles/59cbca49-fe07-4129-ba4e-d63c18381bf2/albums/newv2?count=400&c=tidal-us
04/18 16:45:18 Trace: [dbperf] flush 0 bytes, 0 ops in 8 ms (cumulative 864137412 bytes, 485049 ops in 141657 ms)
04/18 16:45:18 Debug: [easyhttp] [5389] POST to https://discover.roonlabs.net/1/profiles/59cbca49-fe07-4129-ba4e-d63c18381bf2/albums/newv2?count=400&c=tidal-us
04/18 16:45:18 Trace: [dbperf] flush 0 bytes, 0 ops in 8 ms (cumulative 864137412 bytes, 485049 ops in 141665 ms)
04/18 16:45:18 Debug: [easyhttp] [5381] GET to https://tidal.roonlabs.net/1/featured/new/albums?offset=0&count=30&c=tidal-us returned after 824 ms, status code: 304
04/18 16:45:18 Debug: [easyhttp] [5382] GET to https://tidal.roonlabs.net/1/featured/top/albums?offset=0&count=30&c=tidal-us returned after 832 ms, status code: 304
04/18 16:45:19 Debug: [easyhttp] [5385] GET to https://tidal.roonlabs.net/1/featured/top/albums?offset=0&count=30&c=tidal-us returned after 595 ms, status code: 304
04/18 16:45:19 Warn: [tidal/http] GET https://api.tidal.com/v1/featured/recommended/playlists?countryCode=US&offset=0&limit=30 => Unauthorized {“status”:401,“subStatus”:11003,“userMessage”:“The token has expired. (Expired on time)”}
04/18 16:45:19 Info: [tidal] got token expired. refreshing token
04/18 16:45:19 Debug: [easyhttp] [5384] GET to https://tidal.roonlabs.net/1/featured/new/albums?offset=0&count=30&c=tidal-us returned after 599 ms, status code: 304
04/18 16:45:19 Debug: [easyhttp] [5388] GET to https://tidal.roonlabs.net/1/featured/top/albums?offset=0&count=30&c=tidal-us returned after 346 ms, status code: 304
04/18 16:45:19 Warn: [tidal/http] GET https://api.tidal.com/v1/featured/recommended/playlists?countryCode=US&offset=0&limit=30 => Unauthorized {“status”:401,“subStatus”:11003,“userMessage”:“The token has expired. (Expired on time)”}
04/18 16:45:19 Info: [tidal] got token expired. refreshing token
04/18 16:45:19 Debug: [easyhttp] [5387] GET to https://tidal.roonlabs.net/1/featured/new/albums?offset=0&count=30&c=tidal-us returned after 350 ms, status code: 304
04/18 16:45:19 Warn: [tidal/http] GET https://api.tidal.com/v1/featured/recommended/playlists?countryCode=US&offset=0&limit=30 => Unauthorized {“status”:401,“subStatus”:11003,“userMessage”:“The token has expired. (Expired on time)”}
04/18 16:45:19 Info: [tidal] got token expired. refreshing token
04/18 16:45:19 Debug: [easyhttp] [5380] POST to https://metadata.roonlabs.net/1/works/translate?c=tidal-us returned after 936 ms, status code: 200
04/18 16:45:21 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
Core & Remote are running Roon 1.7 build 528 which it shows as the latest version.
Roon Core is running on an intel i5 NUC running Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-174-generic x86_64). Audio files are on a Synology NAS.
The remote is running on OSX 10.14.6 I didn’t try any other remotes when i hit this issue.
The endpoint is a Lumin U1 Mini.
All devices are connected via wired ethernet with Ubiquiti unifi hardware.
This setup has successfully run Roon for a few years at this point.
I can send you the complete logs for before and after the restart if there’s an easy way to get them to you.
Cheers
Simon
Hello @SImon_Fell,
I’d like to get this data over to our development team for a closer look, and in order to do that, I wanted to gather some more information from you:
-
Could you please provide your setup details, including info on your core, remotes, network infrastructure, devices, etc.?
-
Could you send me a copy of this log you’re referencing? I’d like to give the devs a copy of that too. Please upload those logs here.
I uploaded the logs. the System details are at the bottom of the previous post.
sorry that I can’t reproduce it knowingly. but also had the ever-loading symbol running on QNAP several times. restart of Roon solved it.
Hey @SImon_Fell,
We recently released build 536 which may include some helpful changes for issues like this. I’d recommend updating and testing to see if this issue still occurs.
You can read the full release notes here:
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.