What’s happening?
Qobuz playback impossible, artwork missing, rescan stuck.
Describe the issue
First symptom noticed:
Qobuz album suddenly stopped playback. Client showed message “Qobuz is slow to
load” (or similar), but Qobuz server status shows no anomalies and the Qobuz
web player plays back just fine.
Playback keeps failing from that point. Restarts don’t help.
That’s when I noticed all Qobuz albums in my library missing artwork.
Clearing the client image cache doesn’t help. In fact, it may have worsened things?
All of my library now shows broken artwork (no artwork or “genre” stock image on
everything).
Client is noticably slow, running at 67% CPU continuously.
Server is running at 27% CPU, 2GiB RAM, which is also elevated from normal.
Restarting (server or clients) doesn’t help.
Then I tried to add a new album - which I happened to need to listen for work.
It’s a folder of mp3s [sic] on my local fileserver. It does NOT show up.
Forcing a rescan doesn’t help. Restarting the server also doesn’t help, but NOW
the client shows a rescan is stuck.
No amount of restarts allows the rescan to complete. Manually identifying an
album doesn’t work at this time: the UI blocks (probably on the same process
that the rescan is stuck on? Even more potentially, this might be related to
the Qobuz integration??)
Restarting the server with the fileshare offline alleviates some of the symptoms:
- Server CPU and RAM normal (990MiB and 0.6% CPU)
- A test Qobuz album plays back
- The client rescan indicator doesn’t show and manual album Edit/Identify is possible
- However, client CPU usage is still ~70% and almost all album art still missing.
Of course, now all my local albums are offline.
Restarting the fileserver… immediately gets the Roon server stuck on the
rescan. Manually Identifying an album hangs the UI again. I can no longer
laterally navigate different versions of an album I know exist on Qobuz. Qobuz
playback fails again.
Describe your network setup
- Everything wired 1Gb ethernet.
- Roon on dedicated linux box.
- Wifi and ipv6 disabled.
- All software up-to-date (in fact, ~2 days ago(?) so might be causal?)
Summary
In conclusion, my analysis leads me to believe the rescan lockup is a large factor in this, but
(a) why did it happen (It happened spontaneously without me changing things on the fileshares)
(b) why does it block Qobuz / Identify
(c) what’s going on with the artwork and high load?