QNAP - Ready, connection lost!, initializing

[jumpcuts (lpr)]

Core Machine (Operating system/System info/Roon build number)

QNAP TS 251+
Firmware: 4.5.1.1465
Version : 1.7 (build 667) stable

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Netgear R7000
Ethernet

Description Of Issue

Inititial problem:

QNAP - Ready, connection lost! & initializing loop

Since a couple of days I can’t use Roon anymore on my QNAP 251+. When I can connect to the server, I can log for like 30sec then I get a connection lost and it re-initializes. If I don’t connect and just open the app on the mac os or ipad and I go on the Choose your Roon Core page. I can see my server doing the same thing: Ready, Connection Failed, Initializing - It’s doing this about every 3 to 5 minutes. I have rebooted the NAS and Re-installed the server. I just can’t load an old backup bec…

What I have found out since:

As soon as I try to scan audio files located on an external nas (not the one that is running the Roon server) this is happening. I remove the shares from this external storage and I have no more crashes. This used to work flawlessly, but not anymore.

Path is mounted via autorun.rh

Moving my music files to the host server is not an option for the time being as it involves additional hardware investment…

Thanks for looking into this and helping me.

[dylan (Dylan Caudill)]

Hi @jumpcuts,

The next time that Roon is in this state can you stop RoonServer and use the directions found here and send us over a set of logs using a shared Dropbox link? Thanks!

[jumpcuts (lpr)]

Here you go:

jumpcuts_roon_log.zip

Thanks.

[dylan (Dylan Caudill)]

Hi @jumpcuts,

I’m definitely seeing some traces in the logs that are pointing to difficulties stemming from trying to access the files on your watched folder. We have scheduled a meeting to discuss with our technical team but in the meantime would you be able to provide some information about this path being used? Are you able to share screenshots of Settings > Storage when it is up and running? Anything you can provide about what might make this watched folder act different than a typical NAS share would be helpful.

Thanks!

[jumpcuts (lpr)]

Hello,

This is how I mount my path to the nas running the Roon server in autorun.rh:

mount /ip.address/music -t cifs /share/diskstation/music -o

When I add a folder in Roon I point to this path /diskstation/music

Hope this helps.

[noris]

Hi @jumpcuts,

Thanks again for sending the logs. We our technical team has reviewed them, but they are inconclusive.

Can we please ask that you note the next 3 exact local time + date this issue occurs and send us a new log set (with all the Roon logs contained, not just one of them)?

If we have multiple timestamps we can try to identify patterns between the logs, thanks!

[jumpcuts (lpr)]

Here’s a couple of days of me trying to scan music folders on a virgin database.

Thanks in advance.

jumpcuts_logs.zip

[noris]

Thanks @jumpcuts, let me get this over to the team for closer inspection.

Do you recall approximate time and date of the issue to cross-reference in the logs?

[jumpcuts (lpr)]

FYI, I bough new hardware to be able to host my music files from the QNAP server running Roon. So this bug won’t affect me anymore but it may be still worth looking at.

Thanks for your time.

[noris]

Hi @jumpcuts,

Thanks for letting us know that the new hardware you have is able to run Roon better.

I checked in with QA regarding your case and after further review of the logs, it is possible that the issue was due to a problematic media file, specifically this one:
/diskstation/music/_VOLUME_01/_FLAC/Amon - Nona/01 - Amon - nona.flac

Do you by any chance still have this file on your new Roon server / storage locations? Has it already been imported into your Roon database without any issues?

[jumpcuts (lpr)]

Improvements and Bug Fixes for Build 710:

• Fixed problems with monitoring watched folders which were set using symlink on linux

Nice, I guess this would have taken care of my problem. Thanks for the fix!