How do I access the RoPieee system logs?

[Adrian_Berry]

To help work out why Roon Live Radio drops out on my system, Roon Support have asked me get the RoPieee system logs from the device itself.( Playback and Interface Freezing with "No Audio Devices Found" Error (ref#8NX1XX) )
I’ve opened the RoPieee web interface in a browser and been through all the pages. But I’m not finding any references to log files. Where should I look?
I’m running RoPieee 2026.05 (3719) [STABLE] on a Raspberry Pi 4 Model B Rev 1.2 with 2GB RAM and 32GB SSD

[spockfish (Harry ten Berge)]

You can’t reach the system logs yourself.

There’s an option to ‘send feedback’ from the advanced tab, which sends the logs to RoPieee HQ so I can have a look.

[Adrian_Berry]

Ok, done. Reference is 198962fa9310dfc3. My RoPieee is set to Europe/London time

This is where it all went wrong in the Roon Server log
06/26 10:22:35 [Local 06/26 11:22:35] Trace: [Kitchen Pie] [LowQuality 23.4x, 24/48 MP3 => 24/96] [PLAYING @ 25:03] Born To Run - Bruce Springsteen
06/26 10:22:35 [Local 06/26 11:22:35] Trace: [raat_ll/client] [HIFI DSD] OnDisconnected: BeginRead ead count is 0
06/26 10:22:35 [Local 06/26 11:22:35] Trace: [raatserver] [HIFI DSD] lost client connection. Retrying(1)

[spockfish (Harry ten Berge)]

Your log file is empty, which means there’s something wrong.
Are you on wireless or wired?

Can you reboot the unit and try to send me a new feedback?

[Adrian_Berry]

Hi, it’s hardwired with CAT5e cable. House ethernet runs at 1gB.
I’ve rebooted, started play again and clicked on Send Feedback. It wurdled for a minute or so then gave me this reference number e620c330f608d524

[spockfish (Harry ten Berge)]

And this log has captured the issue at hand?

Your logs do show something I normally don’t see (or I never noticed it)

06/27 15:02:51 Trace: [RAAT::HIFI DSD] [drift] update remote clock -401287765215us at local clock 30578018us error=-585us correction=0us neterror=-585us (-56 samples @ 96000hz)
06/27 15:02:53 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.44947 rtt= 0.695
06/27 15:02:53 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.34068 rtt= 0.412334
06/27 15:02:53 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.32349 rtt= 0.418778
06/27 15:02:53 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.5302 rtt= 0.757611
06/27 15:02:53 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.40419 rtt= 0.484223
06/27 15:02:53 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] synced to master clock. offset=-401318343.34068 nominal remote time 401350934540845 rtt 0.412334
06/27 15:02:53 Trace: [RAAT::HIFI DSD] [drift] update remote clock -401285752120us at local clock 32591220us error=-691us correction=0us neterror=-691us (-66 samples @ 96000hz)
06/27 15:02:55 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.50445 rtt= 0.659
06/27 15:02:55 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.44447 rtt= 0.48763
06/27 15:02:55 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.43239 rtt= 0.469963
06/27 15:02:55 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.51786 rtt= 0.601481
06/27 15:02:55 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.47846 rtt= 0.615408
06/27 15:02:55 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] synced to master clock. offset=-401318343.43239 nominal remote time 401352952642744 rtt 0.469963
06/27 15:02:55 Trace: [RAAT::HIFI DSD] [drift] update remote clock -401283734202us at local clock 34609229us error=-783us correction=0us neterror=-783us (-75 samples @ 96000hz)
06/27 15:02:57 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.51662 rtt= 0.576629
06/27 15:02:57 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.50295 rtt= 0.523666
06/27 15:02:57 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.47191 rtt= 0.396519
06/27 15:02:57 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.54074 rtt= 0.520574
06/27 15:02:57 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] got clock sync response, offset= -401318343.4964 rtt= 0.497092
06/27 15:02:57 Trace: [RAAT::HIFI DSD] [lua@0x7f580011c8] [192.168.1.98:44678]  [roon] synced to master clock. offset=-401318343.47191 nominal remote time 401355001176742 rtt 0.396519
06/27 15:02:57 Trace: [RAAT::HIFI DSD] [drift] update remote clock -401281685747us at local clock 36657724us error=-823us correction=0us neterror=-823us (-79 samples @ 96000hz)

Maybe you should contact Support about this.

Thanks

[Adrian_Berry]

Thanks Harry. I’m not sure what it means but have added it to my original thread for Support’s review.

Playback and Interface Freezing with "No Audio Devices Found" Error (ref#8NX1XX)

Hi @Adrian_Berry, Thank you for the update and for running the system for 2.5 days - that’s a very useful data point. We have now reviewed the logs from this morning’s stop in detail. The good news is that the Roon Server itself did not freeze or stall - its log runs continuously through the event with no gaps, and memory and GC activity were within normal range at the time. The disconnect originated on your ropieeeKitchen device - the Pi at 192.168.1.253 cleanly closed its TCP connection to…