Can’t connect to QNAP core after upgrade to QTS 4.3

I have also problem to connect to the core with remotes since upgrade to QTS 4.3

Something odd I have 2 RoonServer directories

Screenshot 2017-07-01 10.43.19.png

Roon itself hangs in all remotes

Screenshot 2017-07-01 10.45.08.png

Can you check if you have the current qpkg installed?
If you still have 1.0.2 or below please update to the latest one (version 2017-02-02).

The 2 RoonServer mounts can occour if you mount the shared folder twice (by afp and smb).

I did upgrade now (was indeed on old version). For some reason roon could not see my watch folders anymore. I browse to them and it is now rescanning. Not sure if this is the rescanning but the connection to the core by remote is unstable and unusable. It loops through loosing connection to core finding it, Then it has this ‘Error loading page, check your network connection’ flashing. I took a bad video because it was too fast

It is not that the remote does not connect at all. It does for brief period, in one of those I could see that Roon was (1) not seeing mapped drives (2) scanning the newly mapped one (I am waiting it is finished with that). Not sure what to do really. Things where ok until I moved to QTS 4.3.

How did you perform the qpkg update? Did you uninstall the old one and then install the new one or did you just install it over the existing old one?
Can you also try to reboot your QNAP and see if this will bring things back to normal?

In general QTS 4.3 should be better suited for RoonServer compared to the previous QTS versions.

I had just installed over the existing old one. So I tried

  1. restarting the nas - same looping
  2. removing Roon Core and re-instal latest - same looping
  3. reboot again the nas with the clean version - same loop of trying to connect

Can you create an empty file in your “RoonServer” share called “ROON_DEBUG_EXTERNAL_LOG.txt”
(you can also download it here and just place it in your RoonServer share, if you are struggling with automatically added file extensions with text-editor).

It should look like this:

Then stop and start RoonServer again in the App Center. It will now write some debug information to this new textfile. Like info about your QNAP and also errors that would display on the command line.

Can you send me the content of the textfile, once you’ve seen the disconnect/reconnect behaviour?

Here you go. Is is the an Asian file name it does not like?

03.07.17-22:14:27 --- Starting RoonServer ...
03.07.17-22:14:27 --- ROON_DATABASE_DIR: /share/external/DEV3303_1
03.07.17-22:14:27 --- ROON_DIR: /share/CACHEDEV1_DATA/.qpkg/RoonServer
03.07.17-22:14:27 --- Model: TVS-1282T
03.07.17-22:14:27 --- QNAP Serial: xxxxxxxxxx
03.07.17-22:14:27 --- Architecture: x86_64
03.07.17-22:14:27 --- QTS Version: 4.3.3
03.07.17-22:14:27 --- PKG Version: 2017-02-02
03.07.17-22:14:27 --- Hostname: MilkyWay
03.07.17-22:14:27 --- MTU: 1500 1500 1500 1500 1500
03.07.17-22:14:27 --- Loading additional 64-bit libs: false
03.07.17-22:14:27 --- ROON_DEBUG_ARGS: 
03.07.17-22:14:27 --- RoonServer PID: 13855


########## Installed RoonServer Version ##########
100300234
1.3 (build 234) stable
stable
##################################################


Initializing
Started
wapi_FindNextFile: Bad encoding for '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Multimedia/My Music/My Music/䨀攀愀渀 搀攀 䰀愀 䘀漀渀琀愀椀渀攀'
Consider using MONO_EXTERNAL_ENCODINGS

Running
wapi_FindNextFile: Bad encoding for '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Multimedia/My Music/My Music/䨀攀愀渀 搀攀 䰀愀 䘀漀渀琀愀椀渀攀'
Consider using MONO_EXTERNAL_ENCODINGS

wapi_FindNextFile: Bad encoding for '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Multimedia/My Music/My Music/䨀攀愀渀 搀攀 䰀愀 䘀漀渀琀愀椀渀攀'
Consider using MONO_EXTERNAL_ENCODINGS

Error
Initializing
Started
wapi_FindNextFile: Bad encoding for '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Multimedia/My Music/My Music/䨀攀愀渀 搀攀 䰀愀 䘀漀渀琀愀椀渀攀'
Consider using MONO_EXTERNAL_ENCODINGS

Running
wapi_FindNextFile: Bad encoding for '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Multimedia/My Music/My Music/䨀攀愀渀 搀攀 䰀愀 䘀漀渀琀愀椀渀攀'
Consider using MONO_EXTERNAL_ENCODINGS

wapi_FindNextFile: Bad encoding for '/share/CACHEDEV1_DATA/.qpkg/RoonServer/roonmnt/Multimedia/My Music/My Music/䨀攀愀渀 搀攀 䰀愀 䘀漀渀琀愀椀渀攀'
Consider using MONO_EXTERNAL_ENCODINGS

Error
Initializing
1 Like

To check that if the directory was the problem I deleted restarted (putting new fresh error log file):
I get the loop without the mention of the directory

03.07.17-22:46:19 --- Starting RoonServer ...
03.07.17-22:46:19 --- ROON_DATABASE_DIR: /share/external/DEV3303_1
03.07.17-22:46:19 --- ROON_DIR: /share/CACHEDEV1_DATA/.qpkg/RoonServer
03.07.17-22:46:19 --- Model: TVS-1282T
03.07.17-22:46:19 --- QNAP Serial: xxxxxxxxxx
03.07.17-22:46:19 --- Architecture: x86_64
03.07.17-22:46:19 --- QTS Version: 4.3.3
03.07.17-22:46:19 --- PKG Version: 2017-02-02
03.07.17-22:46:19 --- Hostname: MilkyWay
03.07.17-22:46:19 --- MTU: 1500 1500 1500 1500 1500
03.07.17-22:46:19 --- Loading additional 64-bit libs: false
03.07.17-22:46:19 --- ROON_DEBUG_ARGS: 
03.07.17-22:46:19 --- RoonServer PID: 16438


########## Installed RoonServer Version ##########
100300234
1.3 (build 234) stable
stable
##################################################


Initializing
Started
Running
Error
Initializing
Started
Running
Error
Initializing
Started
Running
Error
Initializing
Started
Running
Error
Initializing
Started
Running
Error
Initializing
Started
....
1 Like

I then cleared the cache thinking it could have been corrupted and remember the bad directory name, and bingo it now works for now

1 Like

Thank you Chief Tinkerer !

Previous version was more tolerant of this corrupted directory it seems.

Glad you got it working again. The qpkg did not differ, except that the 64-bit libraries from the QTS are used now (the old and in the qpkg bundled ones caused RoonServer to crash on QTS 4.3).
I can’t say for sure, but maybe the cache got corrupted during the crash-loop with the old qpkg on QTS 4.3…?

PS: You can stop RoonServer then again, delete the txt file in the RoonServer share and then start RoonServer again.

This is interesting - why is QTS 4.3 better suited than 4.2.X ?

Because QTS 4.3 comes with all required 64-bit libraries that are required to run RoonServer. They needed to be bundled for QTS 4.2.2 and below to make RoonServer work.
Before QTS 4.3, only the kernel was 64-bit. Because of that, there was a risk, that with a kernel upgrade the bundled 64-bit libraries no longer work and need to be updated as well.

Oh I see! Performance wise there shouldn’t be much of a difference though?

Did not do any benchmarks. But I don’t see a reason for performance in-/decrease…

Ok - thanks! So the current QPKG works fine for 4.2.x and 4.3.x - and is getting the very latest stable version of Roon automatically ?

Correct.
``

1 Like

Dear Jean-Marc, how did you clear the cache?
i’m having exactly the same problem. thx