Intermittent loss of connectivity to Roon Server and music stops

I had another occurrence of this this morning - 06:28 Pacific - music stopped playing, remote lost connectivity and the same syslog and apport entries as before. I was playing “(I Don’t Want to Destroy) Our Beautiful Thing” by David J from a local file.

ERROR: apport (pid 31304) Tue Dec  8 06:28:59 2020: another apport instance is already running, aborting
ERROR: apport (pid 31301) Tue Dec  8 06:28:59 2020: another apport instance is already running, aborting
ERROR: apport (pid 31305) Tue Dec  8 06:28:59 2020: another apport instance is already running, aborting
ERROR: apport (pid 31303) Tue Dec  8 06:28:29 2020: called for pid 31302, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 31303) Tue Dec  8 06:28:29 2020: executable: /opt/RoonServer/RoonMono/bin/mono-sgen (command line "/opt/RoonServer/RoonMono/bin/RoonAppliance --debug --gc=sgen --server RoonAppliance.exe -watchdogport=34307")
ERROR: apport (pid 31303) Tue Dec  8 06:28:29 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 31303) Tue Dec  8 06:29:08 2020: wrote report /var/crash/_opt_RoonServer_RoonMono_bin_mono-sgen.0.crash

Dec  8 06:28:29 Roon-Media NetworkManager[589]: <info>  [1607437709.1783] manager: NetworkManager state is now CONNECTED_SITE
Dec  8 06:28:29 Roon-Media start.sh[12100]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[12100]: #011Native Crash Reporting
Dec  8 06:28:29 Roon-Media start.sh[12100]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[12100]: Got a SIGSEGV while executing native code. This usually indicates
Dec  8 06:28:29 Roon-Media start.sh[12100]: a fatal error in the mono runtime or one of the native libraries
Dec  8 06:28:29 Roon-Media start.sh[12100]: used by your application.
Dec  8 06:28:29 Roon-Media start.sh[12100]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[11886]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[11886]: #011Native Crash Reporting
Dec  8 06:28:29 Roon-Media start.sh[11886]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[11886]: Got a SIGSEGV while executing native code. This usually indicates
Dec  8 06:28:29 Roon-Media start.sh[11886]: a fatal error in the mono runtime or one of the native libraries
Dec  8 06:28:29 Roon-Media start.sh[11886]: used by your application.
Dec  8 06:28:29 Roon-Media start.sh[11886]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[11886]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[11886]: #011Native stacktrace:
Dec  8 06:28:29 Roon-Media start.sh[11886]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x5098ec - /opt/RoonServer/RoonMono/bin/RoonAppliance :
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x509d17 - /opt/RoonServer/RoonMono/bin/RoonAppliance :
Dec  8 06:28:29 Roon-Media whoopsie[826]: [06:28:29] offline
Dec  8 06:28:29 Roon-Media systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec  8 06:28:29 Roon-Media dbus-daemon[586]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=589 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Dec  8 06:28:29 Roon-Media start.sh[12100]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[12100]: #011Native stacktrace:
Dec  8 06:28:29 Roon-Media start.sh[12100]: =================================================================
Dec  8 06:28:29 Roon-Media systemd[1]: Started Network Manager Script Dispatcher Service.
Dec  8 06:28:29 Roon-Media dbus-daemon[586]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x470941 - /opt/RoonServer/RoonMono/bin/RoonAppliance :
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x425704 - /opt/RoonServer/RoonMono/bin/RoonAppliance :
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x4257ba - /opt/RoonServer/RoonMono/bin/RoonAppliance :
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x5098ec - /opt/RoonServer/RoonMono/bin/RAATServer :
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x7faf67a113c0 - /lib/x86_64-linux-gnu/libpthread.so.0 :
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x509d17 - /opt/RoonServer/RoonMono/bin/RAATServer :
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x470941 - /opt/RoonServer/RoonMono/bin/RAATServer :
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x7faf6788a364 - /lib/x86_64-linux-gnu/libc.so.6 : __libc_malloc
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x425704 - /opt/RoonServer/RoonMono/bin/RAATServer :
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x4257ba - /opt/RoonServer/RoonMono/bin/RAATServer :
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x8ec2ab - /opt/RoonServer/RoonMono/bin/RoonAppliance : monoeg_malloc
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x7f70023673c0 - /lib/x86_64-linux-gnu/libpthread.so.0 :
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x8eaacb - /opt/RoonServer/RoonMono/bin/RoonAppliance :
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x8eaf01 - /opt/RoonServer/RoonMono/bin/RoonAppliance : monoeg_g_utf8_to_utf16
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x7f70021e0364 - /lib/x86_64-linux-gnu/libc.so.6 : __libc_malloc
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x75f396 - /opt/RoonServer/RoonMono/bin/RoonAppliance : mono_string_new_checked
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x8ec2ab - /opt/RoonServer/RoonMono/bin/RAATServer : monoeg_malloc
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x7ae829 - /opt/RoonServer/RoonMono/bin/RoonAppliance :
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x8eaacb - /opt/RoonServer/RoonMono/bin/RAATServer :
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x8eaf01 - /opt/RoonServer/RoonMono/bin/RAATServer : monoeg_g_utf8_to_utf16
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x70dd7a - /opt/RoonServer/RoonMono/bin/RoonAppliance :
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x6faca9 - /opt/RoonServer/RoonMono/bin/RoonAppliance :
Dec  8 06:28:29 Roon-Media start.sh[11886]: #0110x403820b2 - Unknown
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x75f396 - /opt/RoonServer/RoonMono/bin/RAATServer : mono_string_new_checked
Dec  8 06:28:29 Roon-Media start.sh[11886]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[11886]: #011Telemetry Dumper:
Dec  8 06:28:29 Roon-Media start.sh[11886]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x7ae829 - /opt/RoonServer/RoonMono/bin/RAATServer :
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x70dd7a - /opt/RoonServer/RoonMono/bin/RAATServer :
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x6faca9 - /opt/RoonServer/RoonMono/bin/RAATServer :
Dec  8 06:28:29 Roon-Media start.sh[12100]: #0110x40c35302 - Unknown
Dec  8 06:28:29 Roon-Media start.sh[12100]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[12100]: #011Telemetry Dumper:
Dec  8 06:28:29 Roon-Media start.sh[12100]: =================================================================
Dec  8 06:28:29 Roon-Media start.sh[12100]: Pkilling 0x7f6ffd47a700 from 0x7f6fef961700
Dec  8 06:28:29 Roon-Media start.sh[12100]: Pkilling 0x7f7002140780 from 0x7f6fef961700
Dec  8 06:28:29 Roon-Media start.sh[12100]: Pkilling 0x7f70012eb700 from 0x7f6fef961700
Dec  8 06:28:29 Roon-Media start.sh[12100]: Pkilling 0x7f6fefb62700 from 0x7f6fef961700
Dec  8 06:28:29 Roon-Media start.sh[12100]: Pkilling 0x7f6ffdeaa700 from 0x7f6fef961700
Dec  8 06:28:29 Roon-Media start.sh[12100]: Pkilling 0x7f6feef5c700 from 0x7f6fef961700
Dec  8 06:28:29 Roon-Media start.sh[12100]: Entering thread summarizer pause from 0x7f6fef961700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5eb45700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf45980700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faecfb11700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf64390700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5cae4700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae9511f700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf45b81700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae1b1ea700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae31dff700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf44d78700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faee64e9700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae93ff7700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae1b3eb700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf45f83700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5cbbf700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5c442700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5c204700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faeced0a700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae95603700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf4491c700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5c643700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5cb25700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf677ea780 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faecef0b700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae415fe700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5c844700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae928f6700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae417ff700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5cf9b700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae2045e700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae92af7700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae2f781700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae3fefc700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faecf30d700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faea7927700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae96e3f700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5e742700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5caa3700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf4537d700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faee7745700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faee6b72700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae20860700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae402fe700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf5cb66700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faee6d73700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae20a61700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faecd8d5700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faee487e700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7fae20c62700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Pkilling 0x7faf46c16700 from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Entering thread summarizer pause from 0x7faf5e541700
Dec  8 06:28:29 Roon-Media start.sh[11886]: Finished thread summarizer pause from 0x7faf5e541700.
Dec  8 06:28:29 Roon-Media start.sh[11886]: * Assertion: should not be reached at mini-exceptions.c:452
1 Like

I just installed the latest stable low-latency kernel from the 5.6 branch (5.6.17), just to see how things work out on a more recent kernel. If there is a problem with the 667 build’s mono runtime, I’d expect to see the same SIGSEGV events to occur.

Don’t know if all the problems in this thread are occurring to folks who are running RoonServer, but I had nothing but trouble with RoonServer.

Maybe try running full Roon as a test?

This is on Ubuntu Linux - no full Roon available for Linux.

oops :flushed:

Just saw a thread were someone experienced similar SIGSEGV behavior after the 667 upgrade, but with the core running on a QNAP… which is Linux as well, after all.

Just an update to keep documented facts current, In the past day or so I have performed a dist-upgrade to Ubuntu 5.4.0-56.62-generic 5.4.73 - the symptoms are still being experienced since this action.

In my logs I see another SIGSEGV occurrence today 06:15 am, without streaming at the moment. If these events were hourly or more often it would drive me crazy… and there’s no response by Roon support, even when other users experience the same. As it is, I can use Roon all day long with no problems, but something is not right.

I can also deal with once a day and not grumble too much about it. Reflecting back though, my original post from last week was started because I was experiencing disconnects multiple times in the course of an evening. Sometimes it would be multiple times listening to just one album. I disabled IGMP snooping and for a few days I thought that had resolved the issue, but after extended testing it became apparent there was still a problem. I wonder if I had multiple things going on? I might re-enable IGMP snooping this evening and see if I return the original state with more frequent disconnects and then analyze the log files.

I also want to say that I’m a little frustrated with the lack of response from @support too.

My drops are back to at least every hour or two, FWIW…

To me this looks like it all starts with the NetworkManager restarting. Roon as a network dependent process seems to bail out then. I ask myself if the restarts of the NetworkManager also occur when Roon Server isn’t running at all?

I don’t have another Linux box to do tests nor can I easily port the Roon server to another PC, but this is something which should be relatively easy to debug. What I can do is try and restart NetworkManager and see what Roon server does…

I just restarted NetworkManager and Roon kept playing… wasn’t affected.

I am considering to do a clean reinstall of Ubuntu Server on my Roon Core box, to go back to a well-known standard configuration…

1 Like

A couple of days ago I re-enabled IGMP snooping on my router and that, for better or worse, has no effect at all. My remotes can discover the server and work well either way. And the SIGSEGVs we see in the logs don’t have nothing to do with IGMP snooping as configured on our routers.

For many days I had no disconnection occur while playing music on the server. But it is necessary to understand what is triggering those events, to resolve the problem for those who experience this several times a day or hour.

1 Like

Hi @Robem / @Andreas_Philipp1,

Thank you for sharing that additional information, it certainly does looks strange that you are both getting similar errors. Let me check in with our QA team if they can provide additional context surrounding these traces.

@Robem, @Lawrence_Klein, & @Andreas_Philipp1 — Is your Core set up with a static IP or DHCP? If DHCP, how often does it renew?

Mine is static (address of Sonic Transporter)

@dylan - I use a reserved IP address

Mine is static with address reservation on the router.

Reading up on some current info with regard to network configuration under Ubuntu Linux, I seem to grasp the following:

  1. From 18.04 onward, Ubuntu uses Netplan, a new network configuration tool.

  2. Netplan can be configured to set an interface up directly with static address, or it can delegate management of the interface to one of two network daemons - NetworkManager or networkd.

  3. On Ubuntu Desktop, the default is NetworkManager.

  4. Conversely, on Ubuntu Server the default is networkd.

  5. What we users with the SIGSEGV problem seem to have in common is that our network interfaces are being managed by NetworkManager, or so it seems from looking at syslog where always immediately before the segmentation error NetworkManger was active. This was pointed out by @BlackJack in this thread.

  6. Even if we configure on our routers a reserved address for the Roon core server, the NetworkManager-configured interface still may be using DHCP4 calls to the router. To ensure that does not happen, we would have to configure the interface explicitly as static, using Netplan on the server. This is something I did not do on my machine.

  7. I initially had installed my server using Ubuntu desktop, so NetworkManager was the default network management tool on my box. I yesterday decided to reinstall the Roon core server using Ubuntu server, so now the default management tool is networkd. It now has been up near 24 hours, and in syslog I haven’t seen any trace of NetworkManager - it isn’t active anymore. It still is little time to tell, but I haven’t had a SIGSEGV in those 24 hours.

  8. Even now my network configuration uses DHCP4 calls to the server:

    2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel      state UP group default qlen 1000
     link/ether 04:d9:f5:f2:f6:aa brd ff:ff:ff:ff:ff:ff
     inet 10.0.4.116/24 brd 10.0.4.255 scope global dynamic enp3s0
     valid_lft 58251sec preferred_lft 58251sec
     inet6 fe80::6d9:f5ff:fef2:f6aa/64 scope link 
     valid_lft forever preferred_lft forever
    
  9. To turn off completely the use of DHCP4 I would have to configure the interface as static by a configuration file in /etc/netplan, using the YAML syntax demanded by the tool. I won’t do this for the moment, waiting a week or so to watch if under networkd I’ll see similar SIGSEGV events as there were under NetworkManager.

4 Likes