I have recently moved my core to an Ubuntu 18.04 LTS server from Windows 10 desktop. I am now having trouble with roon on my Nativ Vita.
If I play a track, 20 seconds in I get a disconnected msg flashing up very briefly on the Control display and playback stops. If I restart in plays for a few seconds then the same happens.
Every 35 seconds, regardless of whether or not any music is paying, the Control display flashes a message “select an audio zone” the it goes away, and the zone remains as it was. It appears the connection is momentarily lost and reconnects immediately. But enough to stop playback every time.
Playing music over my network to this device outside of Roon works fine so I am not looking at the network as the cause of this.
Checking the roonserver status in Ubuntu I get a bunch of messages indicating connection was reset by peer …
● roonserver.service - RoonServer
Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-11-08 10:26:43 UTC; 2 days ago
Main PID: 3544 (start.sh)
Tasks: 95 (limit: 4627)
CGroup: /system.slice/roonserver.service
├─3544 /bin/bash /opt/RoonServer/start.sh
├─3549 /opt/RoonServer/RoonMono/bin/RoonServer --debug --gc=sgen --server RoonServer.exe
├─3576 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=42877
├─3579 /opt/RoonServer/Server/processreaper 3576
└─3652 /opt/RoonServer/RoonMono/bin/RAATServer --debug --gc=sgen --server RAATServer.exe
Nov 11 08:16:13 vm_ubuntu1804lts start.sh[3544]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046] in <dbe6654a3c7d484f8a29922407cdd746>:0
Nov 11 08:16:47 vm_ubuntu1804lts start.sh[3544]: System.Net.Sockets.SocketException (0x80004005): Connection reset by peer
Nov 11 08:16:47 vm_ubuntu1804lts start.sh[3544]: at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult asyncResult) [0x00012] in <126998f2e5ae42fe95554117eb649feb>:0
Nov 11 08:16:47 vm_ubuntu1804lts start.sh[3544]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046] in <dbe6654a3c7d484f8a29922407cdd746>:0
Nov 11 08:17:23 vm_ubuntu1804lts start.sh[3544]: System.Net.Sockets.SocketException (0x80004005): Connection reset by peer
Nov 11 08:17:23 vm_ubuntu1804lts start.sh[3544]: at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult asyncResult) [0x00012] in <126998f2e5ae42fe95554117eb649feb>:0
Nov 11 08:17:23 vm_ubuntu1804lts start.sh[3544]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046] in <dbe6654a3c7d484f8a29922407cdd746>:0
Nov 11 08:17:57 vm_ubuntu1804lts start.sh[3544]: System.Net.Sockets.SocketException (0x80004005): Connection reset by peer
Nov 11 08:17:57 vm_ubuntu1804lts start.sh[3544]: at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult asyncResult) [0x00012] in <126998f2e5ae42fe95554117eb649feb>:0
Nov 11 08:17:57 vm_ubuntu1804lts start.sh[3544]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046] in <dbe6654a3c7d484f8a29922407cdd746>:0
It would seem that the peer (Nativ Vita) sent a RST packet to the server rather than the network dropping out. What do you mean by “If I restart in plays for a few seconds then the same happens.”? What do you restart? A device, playback?
Can you describe you setup and what music you’re playing etc.?
Hi Martin,
Sorry, that was pretty ambiguous … I hit play again. Although powering down everything and restarting has no impact, the problem persists.
I have a HP Proliant DL380 G6 running XenServer as a hypervisor. On this I run an Ubuntu 18.04 LTS guest. Physically, this server is connected to a DLINK Taipan ADSL modem/router.
The Nativ Vita device is also connected to the same router. Both via ethernet, not wifi.
The music is stored on the same Ubuntu guest on which Roon Core is installed.
The DAC is an ANK DAC 3.1 connected via coax from the Nativ Vita. This is a low tech, back to basics R-2R ladder DAC with tube output stage. I mention that because it has no complex electronics sending any control signals back to the Nativ Vita.
Nothing special about the music, happens on both hi res and 44.1/16.
Please let me know if I can provide any more information. Thanks for your help.
When you changed Roon Server to Ubuntu did you update Nativ Vita settings?
How do I update music services and ROON on my Vita? Read More
To update your music services (e.g. Spotify) or ROON please do not update from inside the app itself, but proceed as follows:
To update ROON please go to MY MUSIC and keep the finger pressed on the SWITCH TO ROON button. Select UPDATE from the pop-up and the Vita will download the latest version.
To update music services please go to MUSIC SERVICES and tap on the “…” icon next to each music service. Select UPDATE from the pop-up.
Long shot, but something has confused if for it to send the reset. I’m not familiar with this product but assume it will download Roon Bridge.
@Martin_Webster … Thanks for the advice. However, it is at the latest version. I have also been in contact with Nativ support. They have sent me a link to the latest beta version of the software which is currently with Roon for certification so I’ll try that and let you know.
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
I have updated to Nativ 1.6.0 FINAL Beta … no change
I have reproduced the issue at 14/11/2018 08:54 local time UTC+11
My Ubuntu log is in UTC :
mdekonin@vm_ubuntu1804lts:/usr/data$ sudo systemctl status roonserver
● roonserver.service - RoonServer
Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2018-11-12 11:37:05 UTC; 1 day 10h ago
Main PID: 843 (start.sh)
Tasks: 95 (limit: 4624)
CGroup: /system.slice/roonserver.service
├─ 843 /bin/bash /opt/RoonServer/start.sh
├─ 854 /opt/RoonServer/RoonMono/bin/RoonServer --debug --gc=sgen --server RoonServer.exe
├─1128 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=33327
├─1130 /opt/RoonServer/Server/processreaper 1128
└─1257 /opt/RoonServer/RoonMono/bin/RAATServer --debug --gc=sgen --server RAATServer.exe
Nov 13 21:53:32 vm_ubuntu1804lts start.sh[843]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046] in :0
Nov 13 21:54:06 vm_ubuntu1804lts start.sh[843]: System.Net.Sockets.SocketException (0x80004005): Connection reset by peer
Nov 13 21:54:06 vm_ubuntu1804lts start.sh[843]: at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult asyncResult) [0x00012] in <126998f2e5ae42fe95554117eb649feb>:0
Nov 13 21:54:06 vm_ubuntu1804lts start.sh[843]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046] in :0
Nov 13 21:54:40 vm_ubuntu1804lts start.sh[843]: System.Net.Sockets.SocketException (0x80004005): Connection reset by peer
Nov 13 21:54:40 vm_ubuntu1804lts start.sh[843]: at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult asyncResult) [0x00012] in <126998f2e5ae42fe95554117eb649feb>:0
Nov 13 21:54:40 vm_ubuntu1804lts start.sh[843]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046] in :0
Nov 13 21:55:14 vm_ubuntu1804lts start.sh[843]: System.Net.Sockets.SocketException (0x80004005): Connection reset by peer
Nov 13 21:55:14 vm_ubuntu1804lts start.sh[843]: at System.Net.Sockets.Socket.EndReceive (System.IAsyncResult asyncResult) [0x00012] in <126998f2e5ae42fe95554117eb649feb>:0
Nov 13 21:55:14 vm_ubuntu1804lts start.sh[843]: at Sooloos.RnetJsonClient+<>c__DisplayClass65_0.<_BeginRead>b__0 (System.IAsyncResult ar) [0x00046] in :0
mdekonin@vm_ubuntu1804lts:/usr/data$
You have my sincere apologies for the delay here! After your last message I enabled diagnostics on your account but the diagnostics report did not reach us. I have tried to enable diagnostics once more and the next time that your Core is active the diagnostics report should be uploaded to our servers. I’ll be sure to keep you updated here once the report has been received and the team has had a chance to review.
Hi Dylan,
no problem, I too must apologise. When I didn’t initially get a response from you I did a bit more work myself and decided to create a clean Ubuntu image from scratch and install Roon Server on it. This could be why you didn’t get any reports. I finished this over the weekend and when I connected a roon control to it (Windows 10) I saw the new (uncertified) RAAT client on the Nativ Vita as a new device. I did not see this immediately after I upgraded the software so maybe I had not actually tested it last time.
So the upshot of all this is that initially the same problem presented itself, disconnecting (resetting) every 20 seconds or so. But the more I restarted playback, the longer it ran for. Now it seems to run for several minutes, randomly. First time about 24 minutes of playback, then on and off for shorter periods but certainly much less frequently than previously. A major improvement.
I’ll set playback going this evening so you can capture some diagnostics in your next report. And I can actually get some listening in while it remains connected for minutes at a time rather than seconds!
.
Thanks for your help
Michael
Hi @dylan,
My new roonserver on a fresh Ubuntu 18.04 is running as I write this post. The problem is back to it’s initial frequency, every few seconds … initially on 44.1/24 Van Morrison, Astral Weeks, then 44.1/16 Alison Moyet, Raindancing … just to eliminate any format issues.
I notice my CPU utilisation is significantly higher than normal, all attributed to the roonappliance process, I assume this is the diagnostics logging?
Time of this test on the server in UTC is Nov 19, 10:10:01 when I started the server, first connection reset at 10:12:38.
On the Nativ Vita UTC + 11 - 21:12:38
As I am typing this I notice it has run for over 4 minutes … I’ll keep watching.
I wanted to reach out because I’ve been keeping an eye on our servers, waiting for the aforementioned diagnostics report.
For some reason it is not reaching our servers, even after I tried re-enabling diagnostics on your account. I also ran a quick test and I was able to submit a similar report from my setup here, so something else is going on.
So we can move forward, I was hoping for now you could use the directions found here and send us over a set of logs using a shared Dropbox link.
Hi @dylan The easiest way to find them would be to look for the restart of the roonserver because I started everything from scratch to recreate it last time. It happened immediately every few seconds for several attempts. Then the time between disconnects stretched out to (I think) 24 minutes and then over 3 hours. Oddly though, now when I issue systemctl status roonserver immediately after an apparent disconnect, the connection reset messages are no longer there.
@dylan sorry, ignore my last post. I was confused because I stopped the roonserver process to copy the logs.
So, I was playing Van Morrison, Astral Weeks. It was approximately 21:12 on Nov 19. So in UTC time in the logs that would be 10:12 on Nov 19.
Let me know if you need anything else.
Michael
Do you by any chance have the system log turned on on the Vita?
I also have the frequent dropouts if the system log is on.
Turning it off somewhat fixed the issue (it occurs maybe once or twice a day with the music on all the time)
Apologies for the delay here. I spoke with the team about this, and we just recently got this hardware in-house, so we are scheduling some time to do some testing in our QA labs to try to reproduce the behavior you’re seeing. Once the team has completed their investigation I’ll be sure to let you know ASAP.