I tried on the Roon forum, I will try here as well.

[AudioDoctor]

I am running Roonserver on a very minimal Arch install on my CAPS, and it appeared to work fine until one day I had to reboot my server and suddenly, despite the fact that my remotes could see the server, I could browse all my music, I could see and browse Qobuz, all my files appeared properly, and the server itself reported Roonserver was up and running properly, when I pressed play I would get a message that says "playback was interrupted because a track failed to load." After spending a good day or more trying everything I could think of, I uninstalled, and then reinstalled Roon Server using their Easy Set up scripts. Everything appeared to work great, except the same problem was there. I went over permissions for the drives, but thought if that were the problem then I wouldn't even be able to see the files. Finally, I tried a terminal command that worked for someone on the Roon forum and it worked. Upon every reboot I have to open a terminal and type "systemctl restart roonserver" to get my Roon Server to work and play music.

 

Anyone here have any idea what may be causing this?

[The Computer Audiophile]

That’s a tough one. Rebooting obviously does the same thing (restarts Roonserver), but at a different time. It seems like roonserver is loading before something else it requires or part of loading roonserver does something that can’t be done at the time it loads at boot up. 
 

Have you checked the Roon logs to see what happens at initial load?

 

Are there any related logs in /var/log?

[charlesphoto]

Why not just keep it up and running? Why all the reboots? Most gear is best left on anyway. But I have no idea about CAPS gear, I'm just running ROCK on a NUC. That said, whenever I update Roon or if my NUC is powered down, I have to totally reset the database from a backup or the rotes won't find it. IMO Roon isn't quite as plug and play as they like to make it out to be. 

[lmitche]

1 hour ago, charlesphoto said:

Why not just keep it up and running? Why all the reboots? Most gear is best left on anyway. But I have no idea about CAPS gear, I'm just running ROCK on a NUC. That said, whenever I update Roon or if my NUC is powered down, I have to totally reset the database from a backup or the rotes won't find it. IMO Roon isn't quite as plug and play as they like to make it out to be. 

I have seen this with Archlinux and Roon several times when trying to play a Tidal track. I could be wrong, but it is likely a DNS setup problem.

 

Goto the command line and try to ping www.google.com . If you get an address related error, that proves it. 

 

In archlinux this can be fixed a dozen different ways, all are well documented, so pick one that meets your needs and go for it. You will probably need to change teh contents of your /etc/resolv.conf file.

[AudioDoctor]

7 hours ago, charlesphoto said:

Why not just keep it up and running? Why all the reboots? Most gear is best left on anyway. But I have no idea about CAPS gear, I'm just running ROCK on a NUC. That said, whenever I update Roon or if my NUC is powered down, I have to totally reset the database from a backup or the rotes won't find it. IMO Roon isn't quite as plug and play as they like to make it out to be. 

 

I actually forget why it needed to be rebooted, which led to this discovery, but rebooting it isn't something that happens often.

[AudioDoctor]

6 hours ago, lmitche said:

I have seen this with Archlinux and Roon several times when trying to play a Tidal track. I could be wrong, but it is likely a DNS setup problem.

 

Goto the command line and try to ping www.google.com . If you get an address related error, that proves it. 

 

In archlinux this can be fixed a dozen different ways, all are well documented, so pick one that meets your needs and go for it. You will probably need to change teh contents of your /etc/resolv.conf file.

 

No errors at all.

[AudioDoctor]

8 hours ago, The Computer Audiophile said:

That’s a tough one. Rebooting obviously does the same thing (restarts Roonserver), but at a different time. It seems like roonserver is loading before something else it requires or part of loading roonserver does something that can’t be done at the time it loads at boot up. 
 

Have you checked the Roon logs to see what happens at initial load?

 

Are there any related logs in /var/log?

 

"have you checked the Roon logs..."

no, that would make too much sense. Going to do that now.  ha

[lmitche]

1 hour ago, AudioDoctor said:

 

No errors at all.

Are you running headless or the GUI version of Archlinux? Which network manager you are using?

 

If you like post the contents of /etc/hosts /etc/hostname and /etc/resolv.conf.

 

[AudioDoctor]

19 minutes ago, lmitche said:

Are you running headless or the GUI version of Archlinux? Which network manager you are using?

 

If you like post the contents of /etc/hosts /etc/hostname and /etc/resolv.conf.

 

 

headless, but with a monitor attached so I can do CLI stuff there if I need to. I am still learning at this.

 

networkmanager.service is the network manager?

[The Computer Audiophile]

33 minutes ago, AudioDoctor said:

 

headless, but with a monitor attached so I can do CLI stuff there if I need to. I am still learning at this.

 

networkmanager.service is the network manager?

Just configure ssh, then you can get to the command line from your computer, tablet, or phone. 

[lmitche]

58 minutes ago, AudioDoctor said:

 

headless, but with a monitor attached so I can do CLI stuff there if I need to. I am still learning at this.

 

networkmanager.service is the network manager?

Archlinux has several network management sub-systems. I don't use networkmanager.service so can't be of much help.

 

I can tell you that every time I've seen this error from Roon, it was a network configuration error that caused the problem.

 

Good luck.

[AudioDoctor]

1 hour ago, The Computer Audiophile said:

Just configure ssh, then you can get to the command line from your computer, tablet, or phone. 

 

It's on the list of stuff to do.

[AudioDoctor]

34 minutes ago, lmitche said:

Archlinux has several network management sub-systems. I don't use networkmanager.service so can't be of much help.

 

I can tell you that every time I've seen this error from Roon, it was a network configuration error that caused the problem.

 

Good luck.

 

Well, that gives me a good place to start looking.

 

DO you have a suggestion for what I should be using?

[lmitche]

1 hour ago, AudioDoctor said:

 

Well, that gives me a good place to start looking.

 

DO you have a suggestion for what I should be using?

AL uses systemd.networkd.

[AudioDoctor]

6 minutes ago, lmitche said:

AL uses systemd.networkd.

 

Al right, some quick reading and I am going to ditch networkmanager.service and switch that back on. i'll report back.

 

I did just verify it's not running.

[AudioDoctor]

Not going to work on it tonight though. I'm going to leave it on and maybe get to it this weekend, maybe next.

[One and a half]

14 hours ago, charlesphoto said:

Why not just keep it up and running? Why all the reboots? Most gear is best left on anyway. But I have no idea about CAPS gear, I'm just running ROCK on a NUC. That said, whenever I update Roon or if my NUC is powered down, I have to totally reset the database from a backup or the rotes won't find it. IMO Roon isn't quite as plug and play as they like to make it out to be. 

Running Roon on a NAS has problems about keeping it on all the time.

 

See here, and search "The Bad".

 

i agree with you about Roon's claim for plug and play. It's a  lot of effort to maintain metadata as it is quite fickle & pedantic so that serach can actually find something. Try restoring a 10,000 track database, and be prepared for days to complete.

[AudioDoctor]

Luckily my CAPS isnt a NAS.

[The Computer Audiophile]

8 hours ago, AudioDoctor said:

Luckily my CAPS isnt a NAS.

CAPS20 runs Roon better than anything on the market 😀

[charlesphoto]

10 hours ago, One and a half said:

Try restoring a 10,000 track database, and be prepared for days to complete.

Hmm, do you mean restore the database from a backup? My 65,000 plus tracks library takes about half hour at most to restore from a USB drive plugged into my NUC 7i5. Or do you mean re-analyse? 

[AudioDoctor]

6 hours ago, The Computer Audiophile said:

CAPS20 runs Roon better than anything on the market 😀

 

I am going to have to agree here.

[One and a half]

11 hours ago, charlesphoto said:

Hmm, do you mean restore the database from a backup? My 65,000 plus tracks library takes about half hour at most to restore from a USB drive plugged into my NUC 7i5. Or do you mean re-analyse? 

Have lived through analyse, not going there, understood. An existing HDD was close to capacity, so purchased a 10TB drive and fitted that to another machine once the copy was complete. The copying of the physical data took less than 30 hours something.

 

Prior to copying the files, Roon (config & database) was backed up to another drive on the network.

 

Roon was told where the new files were, and the config & database restored. This is similar process to Jriver's library restore, initially the library is restored in a short time maybe 10 mins, then takes 4-6 hours to produce thumbnails (not sure why).

 

In Roon's case, the restore took closer to 40 hours to complete for 11,000 tracks. I presume it re-analysed by itself, unless there's a hidden command somewhere. 

 

If the original and unmoved files are restored, the process would be quicker. To the Human mind, the files are the same, since nothing has changed other than the location, but Roon decided it needed full control since it lost it when a drive location letter changed.

 

[bobfa]

I turn off background analysis and set on-demand to fast.  The antipodes folks like it set that way so it does not cause the processor to go wacko doing work that can be delayed.

 

I have a 67k track library and I have moved servers around, etc. no really long issues like that.

 

 

[One and a half]

1 hour ago, bobfa said:

I turn off background analysis and set on-demand to fast.  The antipodes folks like it set that way so it does not cause the processor to go wacko doing work that can be delayed.

 

I have a 67k track library and I have moved servers around, etc. no really long issues like that.

 

 

Yup, like this, from day one:

 

[AudioDoctor]

1 hour ago, bobfa said:

I turn off background analysis and set on-demand to fast.  The antipodes folks like it set that way so it does not cause the processor to go wacko doing work that can be delayed.

 

I have a 67k track library and I have moved servers around, etc. no really long issues like that.

 

 

 

Doing that has never occurred to me. While analyzing my library took approximately 2 days on my mini, it took a few hours on the new CAPS server and then it's done until I add an album. I don't see what the benefit of that is except for the time it takes at the beginning.