Thanks for the suggestion, I do not have logging switched on. That was something suggested by Nativ support so they know about that issue.
@dylan On the advice of Nativ support I have done a Recovery process to reinstall the system from scratch. This seems to have fixed the dropout problem based on just a few minutes of testing. I will test throughout the day and keep you posted.
However, it seems now the cover art is not displaying on the Nativ screen but I am chasing that with Nativ Support.
Thanks for all you help, I’ll let you know how my testing goes.
1 Like
@dylan Sorry for the delay in getting back to you. I have not had time to do extensive testing. However, I am getting some very inconsistent results. Sometimes it works just fine with no disconnects, sometimes I get disconnects from not just the Nativ Vita but also other endpoints, Windows 10 and Sonos. When I get the disconnects, restarting the roonserver seems to resolve it. Until this morning. roonserver now won’t connect…
mdekonin@roonserver:~$ sudo systemctl restart roonserver
mdekonin@roonserver:~$ sudo systemctl status roonserver
● roonserver.service - RoonServer
Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2018-12-11 00:26:01 UTC; 1min 7s ago
Main PID: 41071 (start.sh)
Tasks: 50 (limit: 4624)
CGroup: /system.slice/roonserver.service
├─41071 /bin/bash /opt/RoonServer/start.sh
├─41082 /opt/RoonServer/RoonMono/bin/RoonServer --debug --gc=sgen --server RoonServer.exe
├─41101 /opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=46649
├─41109 /opt/RoonServer/Server/processreaper 41101
└─41253 /opt/RoonServer/RoonMono/bin/RAATServer --debug --gc=sgen --server RAATServer.exe
Dec 11 00:27:04 roonserver start.sh[41071]: writing to log: System.ArgumentException: array too small. numBytes/offset wrong.
Dec 11 00:27:04 roonserver start.sh[41071]: Parameter name: array
Dec 11 00:27:04 roonserver start.sh[41071]: at (wrapper managed-to-native) System.IO.MonoIO.Write(intptr,byte[],int,int,System.IO.MonoIOError&)
Dec 11 00:27:04 roonserver start.sh[41071]: at System.IO.MonoIO.Write (System.Runtime.InteropServices.SafeHandle safeHandle, System.Byte[] src, System.Int32 src_offset, System.Int32
Dec 11 00:27:04 roonserver start.sh[41071]: at System.IO.FileStream.FlushBuffer () [0x00051] in <370a0c27f4b74d1a81431037df6d75bf>:0
Dec 11 00:27:04 roonserver start.sh[41071]: at System.IO.FileStream.WriteInternal (System.Byte[] src, System.Int32 offset, System.Int32 count) [0x000b4] in <370a0c27f4b74d1a81431037
Dec 11 00:27:04 roonserver start.sh[41071]: at System.IO.FileStream.Write (System.Byte[] array, System.Int32 offset, System.Int32 count) [0x00090] in <370a0c27f4b74d1a81431037df6d75
Dec 11 00:27:04 roonserver start.sh[41071]: at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x0007e] in <370a0c27f4b74d1a81431037df6d75bf>
Dec 11 00:27:04 roonserver start.sh[41071]: at System.IO.StreamWriter.Flush () [0x00006] in <370a0c27f4b74d1a81431037df6d75bf>:0
Dec 11 00:27:04 roonserver start.sh[41071]: at Base.StreamLogWriter.WriteLine (System.String s) [0x0001d] in <8e2bbba085c347469d381b30fe73c82a>:0
[1]+ Stopped sudo systemctl status roonserver
mdekonin@roonserver:~$
I’ll reboot the server for now and see what happens.
Thanks for the update here and apologies for the continued troubles. We are currently communicating with Nativ regarding a solution here and will update you once we have more information.
Have you updated to the latest version of Roon (1.6)? If not, give this a try and let us know how things are performing.
Thanks!