Migrated Core, NAS Storage, Playlists Now (Mostly) Empty

[rcrawley]

@noris I’ve just uploaded the full library. Let me know if you need anything else.

FWIW, I’m now back to a point where even restores (including completely removing RoonServer and re-installing then restoring) aren’t working to reset the playlists. No matter what I do restoring doesn’t reset the playlists.

[rcrawley]

@noris One more data point that I just noticed. I create playlists for greatest hits and I just noticed that all of them except one are empty. No idea why Hall & Oates is fine while the rest are all empty, but I thought it might help your team see the differences between empty and not empty playlists in the DB. Thx again!

[rcrawley]

@noris Just pinging this thread so the support ticket stays open. Thanks!

[rcrawley]

Tested with 2.0 and had the same result but caught it happening this time and have full logs to share. Can I post them to the same URL as I’ve shared other details with this issue?

Here’s what I did and what I saw:

• Upgraded the stable NAS core to 2.0, playlists were working as expected (they always do on the NAS)
• Make a snapshot backup of the DB
• Did a fully clean and fresh install of 2.0 on the MBP
• Restored the 2.0 snapshot from the NAS onto the MBP
• Remapped storage locations after restore to local USB storage (music on the MBP core is coming from a filesystem clone of the NAS on local USB storage)
• Check playlists, were complete and working after DB restore on the MBP
• Stopped Core on the NAS so only version of Core on the network is the MBP
• Roon 2.0 ran great on the MBP for a few days
• This morning started seeing frequent “Waiting for Roon Core…” messages when playing an album (not from a playlist)
• Restarted Core on the MBP, “Waiting for Roon Core…” messages stopped and played albums fine
• Checked playlists, now reverted to the “5 songs” playlists

They seem to have flipped immediately after stopping/starting the Core on the MBP. Only log entries after the restart that I could find:

% grep -i playlist RoonServer_log.txt
09/25 07:38:22 Info: [playlistdb] opened. migration version = 1 current version = 1
09/25 07:38:46 Trace: [storage] [directory] Begin queuing fs events, ignoreitunes: True, ignoreplaylists: True
09/25 07:38:46 Trace: [storage] [directory] Begin queuing fs events, ignoreitunes: True, ignoreplaylists: True
09/25 07:38:47 Trace: [storage] [directory] Begin queuing fs events, ignoreitunes: True, ignoreplaylists: True

I’m not sure how to affect “ignoreitunes” to test setting it to False, beyond selecting “Yes” in Storage → Location → Edit → Import iTunes playlists", but I have confirmed I have no XML files in my Roon storage locations.

[rcrawley]

Finally gave up on RoonCore running successfully on MacOS, rebuilt the MBP running Ubuntu 22 a bit over two weeks ago. So far, so good. I hope I don’t jinx it but playlists are still complete and fully functioning after going through the same Backup NAS → Restore DB on MBP process as outlined above for MacOS. It’s also been much more stable on Ubuntu; no “Waiting for Roon Core” issues locally in the house (I still see them with Arc but I’m chalking that up to an Arc issue since I don’t see the same on the local network). Assuming this holds, it looks like a pointer to something going on with RoonCore and DB management just on MacOS.

If anything changes over the next few weeks I’ll update this thread.