RoonServer starting, running, error, restart and so on

Support
#8

Hi @Paul_Hermans,

I wanted to reach out because I’ve been keeping an eye on our servers, waiting for the aforementioned diagnostics report.

For some reason it is not reaching our servers, even after I tried re-enabling diagnostics on your account. I also ran a quick test and I was able to submit a similar report from my setup here, so something else is going on.

So we can move forward, I was hoping for now you could use the directions found here and send us over a set of logs using a shared Dropbox link.

#9

Hi @dylan

Logs at https://www.dropbox.com/s/z29h98avmai89if/paul%40proxml.be.zip?dl=0

#10

Hi @Paul_Hermans,

These logs don’t look quite right The date they’re showing is from February. Are these directly from the Core machine or a remote device?

#11

@dylan
Apologies.
Thought my database was on the NAS where version Roon 1.5 did run for a while.
These are the correct ones.

https://www.dropbox.com/s/z5kvslyw8swfkqz/paul%40proxml.be_roon_macpro.zip?dl=0.

#12

I was streaming a local file when I ran into issues, but this sounds almost identical to what I’m reporting in Clients suddenly unable to connect to server. Maybe our situations are related?

#13

A post was split to a new topic: Troubles connecting to RoonServer when logging in to TIDAL

#14

Indeed, looks the same to me.

#15

@dylan
To clarify I experienced the issue using RoonServer. One of the things I tried out was installing Roon (core+client) on the same server but it gave the same behaviour. Hence the 2 logs.
I have a third setup since then on my MacBook, but again the same. If you need I can supply this one also.

#16

Thanks, @Paul_Hermans — The logs are with the team now for analysis and I’ll be sure to update you as soon as I have their feedback.

#17

@dylan,

Yes,
I have backups from 5 to 9 december 03:00 AM
Ther behaviour started the evening of 9 december late.

#18

Hi @Paul_Hermans,

Can you try using a fresh database and let us know if this changes things here?

  • Stop RoonServer on the Core
  • Navigate to your Roon’s Database Location
  • Find the folder that says “Roon”
  • Rename the “RoonServer” folder to “RoonServer_old”
  • Restart/Reinstall the Roon App to generate a new Roon folder
#19

@dylan Done.

App is busy now importing my Qobuz library. No issues so far.

Now Tidal; also no issues.

Now loading local files; no issues so far.

Unfortunately I have to go now. The only thing to be checked is applying all settings again.

#20

@dylan

For the moment all is running without issues.
What to do next to get my playlists back?

Do I send you the corrupted databases?

#21

Hi @Paul_Hermans,

The team is currently investigating this issue. You can try to restore a backup that you might prior to this issue occurring, but it’s hard to say just yet if the issue will return. For now, I recommend using the current database while we wait for feedback from the team’s investigation. Once I have their feedback I’ll be sure to reach out ASAP.

#22

OK, will do.

#23

@dylan No update on this one yet?

#24

Hi @Paul_Hermans,

I checked with the team on this and received an update — Apologies for the delay.

The team thinks that this behavior is stemming from data stemming from certain albums. They’ve asked that I check to see if you have backups of Roon from before this issue occurred — If you do please let me know and I can send over next steps.

#25

@dylan I did forget that my NAS only keeps backups for 14 days and since the issue appeared a month has passed. So not anymore.

#26

Hi @Paul_Hermans,

To be clear — Did you start doing backups of the new database that you made and have replaced all of the old database ones?

Do you still have the RoonServer_Old folder from before when you made the new database?

#27

Hi @dylan,

Yes, all the old backups have indeed been replaced.
And I don’t have the RoonServer_Old folder from before either.

So I’m afraid, we’re done.