I just wanted to give you an update on this. We’ve narrowed the problem down to what appears to be an infinite loop in the code that generates the index for searches in 1.3. This was added to make searching with large libraries not painfully fast, but it’s a bunch of new C code and has received relatively less testing due to it’s newness.
I’m currently working on attempting to reproduce the loop here from your logs and database dump, and should be able to solve the problem quite quickly once that’s done. In case I can’t manage that, we’re also planning on adding a new command line flag to generate a file that will let us ‘replay’ the inserts and removals from the index, which should make reproducing this sort of problem much easier in the future.
Thanks for your patience, and I’m sorry my code is causing you so much trouble.
Are you getting different results with the same library on the Mac Mini? That would be an interesting result to me, although I guess I’m not sure what I’d do with it if so.
Build 200 of Roon added a command line flag to record everything added or removed to the search index. Can you:
1: Update your Ubuntu RoonServer to build 200. This might require re-downloading from https://roonlabs.com/downloads.html, depending on exactly where it’s hanging
2: Run RoonServer with the -searchindexreplay flag and wait until it gets stuck
3: This will generate a file called “searchindexreplay.txt” in your logs directory. Can you get me that file?
We’re also working through the code, but because we can reproduce the problem we can’t tell whether we’ve fixed it or not.
Hmm … if I run it that way, from the command line, it asks me to sign into Roon and then asks where I keep my music – as though it were a fresh install.
No, I made a mistake. One of the funny side effects of always running a dev version of Roon that I’ve just compiled.
New and improved way to run on Linux with command line arguments: Add them to the end of the last line in the script at “/opt/RoonServer/Appliance/RoonAppliance”, then kill start.sh and wait for the restart.
You probably also want to remove them after collecting the new log file.