[Ticket In] B1643: Roon Server on QNAP stopped starting up after update

Early Access
1

Immediately after update to B1643 Roon Server stopped starting up.

Several restarts of QNAP RoonOnNas app and whole NAS didn’t help.

QNAP app reports:

Status : Stopped
Version : 2.63 (build 1643) earlyaccess

1 Like
Roon on QNAP no longer showing up on my network
2

Hi, @Piotr_Pekala, thank you for the report. Could you please submit the following info:

  1. RoonServer logs
  2. System level logs (how to get them – article)

Put both into a zip archive and upload them here

Thanks!

–
Ivan

3

I’ve uploaded QNAP logs, but Roon logs exceed 100 MB (~150 MB) and cannot be uploaded

4

Thanks! I will take a look at the system logs. I think that should be ok for now.

–
Ivan

5

Same problem here with B1643 on QTS 5.2.9 B3410

RoonServer is listed as ´halted´ in QTS Appcenter and does not start.

6

Thanks, @Arindal!

@Piotr_Pekala, @Arindal, does anyone of you have ssh access to your QNAP? If yes, can you please, do this:

  1. SSH into your NAS via Terminal
  2. Run this command cat /var/log/messages
  3. Copy and save the output
  4. Upload it to the same link I referenced above

Thanks!

–
Ivan

1 Like
7

Output is empty in my case

-rw-r–r-- 1 admin administrators 0 2026-03-16 19:47 messages

8

Tried to, via external Terminal app, but I do not get any response despite from SSH being activated, sorry.

9

Have uploaded both QNAP logs and RoonServer logs in one ZIP

(Moved to production build in between to do a backup. Everything flawless under B1641)

10

Hi, got the same issue on my QNAP. Checking logs indicates that there has been updates to the runtime environment.

Latest Roon Early Access, 2.63 seem to have a bumped dotnet (10.0) runtime that depends on newer /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21’. Current QTS has does not provide it.

1 Like
11

@ivan , Do you expect any solution/workaround soon?

Can I migrate to any other version (Production?) without losing DB and all the settings?

12

@roony_toony, thank you for your input, I will pass this data to our dev team, that’s very helpful!

@Piotr_Pekala, I don’t have any timeframe for the fix, since our dev team only started working on the investigation, but you can move back to the production version, it won’t affect your settings or database. Do you have any recent backups just in case?

Thanks and apologies for troubles.

–
Ivan

14

I have moved to production build B1641 temporarily and can confirm that all settings, database and remote stuff works flawlessly.

2 Likes
15

Anyone aware if B1644 has fixed the QNAP issue? In this case, I would move back to EA…

Thanks!

16

Hi, @Arindal, no, unfortunately, our dev team is still looking into this one.

Thanks!

–
Ivan

1 Like