Errors in systemctl status

Hi,
are these errors something that has to be investigated or I can ignore it?

thanks

systemctl status roonserver
● roonserver.service - RoonServer
Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2021-01-31 03:10:32 CET; 4 days ago
Main PID: 1205 (start.sh)
Tasks: 103
Memory: 2.3G
CPU: 3h 10min 53.847s
CGroup: /system.slice/roonserver.service
├─1205 /bin/bash /opt/RoonServer/start.sh
├─1232 /opt/RoonServer/RoonMono/bin/RoonServer --debug --gc=sgen --server RoonServer.exe
├─2213 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=36541
├─2214 /opt/RoonServer/Server/processreaper 2213
└─2284 /opt/RoonServer/RoonMono/bin/RAATServer --debug --gc=sgen --server RAATServer.exe

Jan 31 02:11:51 ronn-core start.sh[1205]: Not responding
Jan 31 02:11:51 ronn-core start.sh[1205]: aac_fixed decoder found, checking libavcodec version…
Jan 31 02:11:51 ronn-core start.sh[1205]: has mp3float: 1, aac_fixed: 0
Jan 31 02:12:01 ronn-core start.sh[1205]: Running
Feb 02 20:30:47 ronn-core start.sh[1205]: System.Net.Sockets.SocketException (0x80004005): Connection reset by peer
Feb 02 20:30:47 ronn-core start.sh[1205]: at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult asyncResult) [0x00012] in <a42f1dd5b444
Feb 02 20:30:47 ronn-core start.sh[1205]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046]
Feb 03 02:19:30 ronn-core start.sh[1205]: System.Net.Sockets.SocketException (0x80004005): interrupted
Feb 03 02:19:30 ronn-core start.sh[1205]: at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult asyncResult) [0x00012] in <a42f1dd5b444
Feb 03 02:19:30 ronn-core start.sh[1205]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046]
lines 1-24/24 (END)

Hi @John_Smith,

Are you seeing any symptoms in Roon when this happens?

yes kind of drop outs while playbacking Tidal

Hi @John_Smith ,

Can you please verify if this is the issue you are seeing?

@noris
hi i don’t think so, i am not losing connectivity, i am having drop outs while playback… apparently u have some serious bug in the core…

there are many messages in log like these:
[zoneplayer/raat] long rtt sync snd_rpi_hifiberry_dacplus: realtime=4068113287253 rtt=31500us offset=194682287us delta=-15030us drift=-1706us in 6.238s (-273.569ppm, -984.848ms/hr)

02/19 17:22:43 Info: [stats] 1770mb Virtual, 1092mb Physical, 335mb Managed, 0 Handles, 82 Threads
Warn: [XXX] [zoneplayer/raat] long rtt sync snd_rpi_hifiberry_dacplus: realtime=4070179973828 rtt=44500us offset=194693973us delta=11686us drift=9980us in 8.281s (1205.175ppm, 4338.629ms/hr)

02/19 17:24:03 Trace: [snd_rpi_hifiberry_dacplus] [raatclient] GOT [53] {“samples”:22050,“status”:“Dropout”}

I think it wood be helpful if you described your setup in more detail including network between Core and endpoints.

sounds like never ending question here …

the network is stable - Ethernet cable.

How do you know? If you would like some help I politely ask that you answer my question.

thats okay… its Core and clients all connected via ethernet. I dont know … if there might be a network issues … no clue ;/

Hi @John_Smith ,

What does your network setup look like, can you list the model/manufacturer of your networking gear?
Do you notice the issue occurring on any other zones or only the HiFiBerry zone?

hi, @noris
i am not sure i understand the question, i already described the network, dont I? Ethernet 1gbit.

Mostly on that device, yes. I assume the Log message should have some meaning as its logged. What the meaning of such an log message? Can you ask your dev team?

Hi @John_Smith

Based on what we’re seeing here, and from similar cases, often times this type of issue stems from networking trouble between your Core and our servers and other gear over the local network. We asked about the network, specifically the type of model of router you’re using and any other devices, because we’ve seen a few of these issues stem from settings or issues on certain networking gear. Knowing what kind of gear you’re using can definitely help us make suggestions for what to try next.

One thing to try is Google DNS — We’ve found in the past that setting this on your router can help improve TIDAL playback performance.

hi,
is there such a list of problematic gear avail? thanks

Hello @John_Smith ,

Apologies for the delay! Our team’s queue is longer than typical at the moment, but we’re working to get back to everyone as quickly as we can.

While there is no set of networking gear that we endorse, we have a list of networking gear with known modifications required at the end of our Networking Best Practices Guide.

You can also find review from other Roon forum members in the following thread:

Hope this helps!