Roon server stuck in scanning mode after initial track scan (ref#PMXQPW)

Support
1

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

When starting the Roon server, it goes through the process of scanning tracks and completes, however a few seconds later it begins "scanning" again, from what is presumably the last file number, but is now stuck in scanning mode and does not progress.

Adding and removing files still seems to work, however the option to force a rescan is greyed out.

Describe your network setup

Custom Windows 11 PC (Server) connected via Gb ethernet
Synology NAS (Files) connected via Gb ethernet
Single unmanaged Gb switch between the above

2

Hey @Jason_Schubert,

Thanks for writing in! Sorry to hear about your library issues.

We were able to review a fresh diagnostic report from your Roon Server, and saw issues in relation to the following content: Rod Stewart/Essentials [2019]

If you remove the following content from your watched folder, do you still run into issues?

We’ll be on standby for your results! :raised_hands:

3

Hi @benjamin,

I tried removing the “Essentials” folder, however the same issue still occurs, just with a different number of “scanned” files.

Note that the folder.jpg file from this directly, along with multiple other cover art files that appear in “Skipped files”, have been there for up to several years and have never caused Roon to trip up before. Also, previous corrupt files that have caused issues stopped the scan half way through. In this case, the scan appears to complete correctly, but then starts again, presumably where it left off, and gets immediately stuck.

I forgot to mention in my original request that I did at one stage check the exact time the error occurred and looked at the relevant server logs. The following is the entries during that time (error took place around 1:18:14). Nothing here appears to suggest a corrupt file of any kind.

Blockquote
04/27 01:18:04 Trace: [storage] [directory] initial scan of U: took: 303145 ms
04/27 01:18:09 Info: [stats] 2107172mb Virtual, 4000mb Physical, 1628mb Managed, 2084 Handles, 79 Threads
04/27 01:18:13 Trace: [storage] [directory] timer delay: 500, retrycount: 1
04/27 01:18:14 Trace: [roondns] flushed 36 last-known-good entries
04/27 01:18:14 Debug: [easyhttp] [242] POST to https://api.roonlabs.net/device-map/1/register returned after 294 ms, status code: 200, request body size: 6 KB
04/27 01:18:14 Trace: [devicemap] device map updated
04/27 01:18:24 Debug: [easyhttp] [243] POST to https://api.roonlabs.net/device-map/1/register returned after 272 ms, status code: 200, request body size: 6 KB
04/27 01:18:24 Trace: [devicemap] device map updated
04/27 01:18:24 Info: [stats] 2107178mb Virtual, 4000mb Physical, 1628mb Managed, 2118 Handles, 83 Threads
04/27 01:18:39 Info: [stats] 2107171mb Virtual, 4000mb Physical, 1626mb Managed, 2102 Handles, 78 Threads
04/27 01:18:53 Info: [remoting/serverconnectionv2] Client disconnected: 192.168.132.112:53659
04/27 01:18:53 Trace: [raat_ll/client] [System Output] OnDisconnected: BeginRead SocketException(0)
04/27 01:18:53 Trace: [raatserver] [System Output] lost client connection. Retrying(1)
04/27 01:18:53 Info: [raatserver] [System Output] connecting (attempt 1)
04/27 01:18:53 Info: [transport] destroyed zone This PC was playing? False
04/27 01:18:53 Trace: [zone This PC] Suspend
04/27 01:18:53 Info: [zone This PC] Canceling Pending Sleep
04/27 01:18:53 Info: [zone This PC] Canceling Pending Sleep
04/27 01:18:53 Trace: [raatserver] [RaatServer STUDY-PC @ 192.168.132.112:9200] lost client connection. Retrying(0)
04/27 01:18:53 Warn: [raat_ll/client] [System Output] failed to connect(0) Cannot access a disposed object.
Object name: ‘System.Net.Sockets.Socket’.
04/27 01:18:53 Trace: [raatserver] [RaatServer STUDY-PC @ 192.168.132.112:9200] connecting (attempt 1)
04/27 01:18:54 Info: [stats] 2107181mb Virtual, 3923mb Physical, 1404mb Managed, 2012 Handles, 85 Threads
04/27 01:18:55 Info: [library stats] tracks: 89851 (hidden: 5898), albums: 6136 (hidden: 370), artists: 1327, works: 41712, performances: 69906

Thanks
Jason

5

Hi @Jason_Schubert,
Thanks for providing that timestamp it was instructive. I found a trace in your logs indicating that while Roon was scanning your storage location it was modified which resulted in an error.

Unhandled storage exception in ScanDirectory, ex: System.InvalidOperationException: Collection was modified; enumeration operation may not execute.

Is there any other software that is set to modify your watched folder? That could cause the scan to fail and need to be repeated.

6

Hi @daniel,

There is nothing else set up to modify anything in the directory. It is also accessed by Plex, so I tried turning off the Plex server and rescanning, however the problem still occurred.

I think the above error is more likely caused by me copying new albums into the directory or as it is scanning or manually renaming existing files, that should be the only time files are changed as nothing is set up to change the files themselves. These have always previously been updated without issue.

Regards
Jason

8

Hi @Jason_Schubert ,

I was looking over your logs and I noticed recurring traces regarding these albums as well:

Blue Öyster Cult/The Symbol Remains [2020]
The Pillows/FLCL Original Soundtrack, 1 Vol. 1꞉ Addict [2000]

Can you please try to exclude these as well and let us know if this helps? Thanks!

9

Hi @noris,

No, I can’t. We are talking about files that have been in the library potentially many years.

  • Roon can’t read them - fine
  • Roon skips over them - fine
  • If Roon suddenly is unable to skip over them - not fine and this is still Roon’s problem

However I am not going to continue removing random files to see if something that should make no difference is making a difference. If you were checking the logs correctly you would have seen these at the same time as the Rod Stewart image file, or in fact the Close Encounters soundtrack image file that you seem to have not noticed yet. These are not the problem.

Once again:

  • The scan finishes without error
  • Roon then starts rescanning a few seconds after the initial scan is finished and appears to be stuck scanning forever.
  • There are no errors on any of the files you have mentioned that happen at any time anywhere near when the rescan starts.
  • This issue began immediately after “upgrading” to the latest build, you know, the one where your techs were fiddling around with this exact functionality that wasn’t working properly and was also blamed on the users rather than the build before taking several months to fix.

I’m tired of being an unpaid tester for this product. Please escalate this problem to someone who knows more than how to search for the word “skipped” in a log file.

Oh, and just in case you have missed it, I am less than impressed with this support.

11

Hi @Jason_Schubert,
I’m really sorry for the frustration you’ve experienced. We absolutely understand how disheartening it can be when things don’t work the way they should. Please know that we’ve escalated your case to our developers so we can get a deeper look into what’s going on. We truly appreciate your patience, and as soon as we have any news or next steps, we’ll be sure to update you right away. We’re here with you until it’s resolved.

12

Thanks,

Unfortunately, in giving reinstalling the app a go, it crashed my system and somehow broke remoting into it. I have currently stopped all Roon processes pending a rebuild of the system, which was in the works to add/remove some hard drives and clean up, but has now moved up the schedule.

I am hoping to get this done in the next couple of days and will let you know if the problem persists.

Jason