Roon Appliance Core Dump?

[Phil_Ryan]

Hello

Please be gentle, I have no knowledge of Linux, I simply used the info on the forum to perform an install of Linux Mint 20 and Roon plus Cockpit Roon an i5 NUC.

I seem to get intermittent play stops and I have to restart playing the queue.
Looking in Cockpit at the logs I can see the below, any Ideas ?

2:03 PM

Process 42244 (RoonAppliance) of user 0 dumped core. Stack trace of thread 42244: #0 0x00007f0eda65016c __malloc_fork_unlock_child (libc.so.6 + 0x9d16c) #1 0x00007f0eda6991b5 __libc_fork (libc.so.6 + 0xe61b5) #2 0x0000000000789322 n/a (mono-sgen + 0x389322) #3 0x0000000000789e5f n/a (mono-sgen + 0x389e5f) #4 0x0000000000509b0e n/a (mono-sgen + 0x109b0e) #5 0x0000000000509d17 n/a (mono-sgen + 0x109d17) #6 0x0000000000470941 n/a (mono-sgen + 0x70941) #7 0x0000000000425704 n/a (mono-sgen + 0x25704) #8 0x00000000004257ba n/a (mono-sgen + 0x257ba) #9 0x00007f0eda7d73c0 __restore_rt (libpthread.so.0 + 0x153c0) #10 0x00007f0eda650364 __GI___libc_malloc (libc.so.6 + 0x9d364) #11 0x00000000008ec2ab monoeg_malloc (mono-sgen + 0x4ec2ab) #12 0x00000000008eaacb n/a (mono-sgen + 0x4eaacb) #13 0x00000000008eaf01 monoeg_g_utf8_to_utf16 (mono-sgen + 0x4eaf01) #14 0x000000000075f396 mono_string_new_checked (mono-sgen + 0x35f396) #15 0x00000000007ae829 n/a (mono-sgen + 0x3ae829) #16 0x000000000070dd7a n/a (mono-sgen + 0x30dd7a) #17 0x00000000006faca9 n/a (mono-sgen + 0x2faca9) #18 0x000000004205e3b2 n/a (n/a + 0x0) #19 0xff01a8c000040008 n/a (n/a + 0x0)

systemd-coredump

2:03 PM

Process 27756 (RoonAppliance) of user 0 dumped core. Stack trace of thread 27768: #0 0x00000000004f8ba8 n/a (mono-sgen + 0xf8ba8) #1 0x0000000000469908 n/a (mono-sgen + 0x69908) #2 0x0000000000469ea8 n/a (mono-sgen + 0x69ea8) #3 0x000000000046a356 n/a (mono-sgen + 0x6a356) #4 0x000000000046b9bf n/a (mono-sgen + 0x6b9bf) #5 0x000000000046c6ac n/a (mono-sgen + 0x6c6ac) #6 0x0000000000789912 n/a (mono-sgen + 0x389912) #7 0x0000000000789d00 n/a (mono-sgen + 0x389d00) #8 0x0000000000789eb3 n/a (mono-sgen + 0x389eb3) #9 0x0000000000509b0e n/a (mono-sgen + 0x109b0e) #10 0x0000000000509d17 n/a (mono-sgen + 0x109d17) #11 0x0000000000470941 n/a (mono-sgen + 0x70941) #12 0x0000000000425704 n/a (mono-sgen + 0x25704) #13 0x00000000004257ba n/a (mono-sgen + 0x257ba) #14 0x00007f0eda7d73c0 __restore_rt (libpthread.so.0 + 0x153c0) #15 0x00007f0eda650364 __GI___libc_malloc (libc.so.6 + 0x9d364) #16 0x00000000008ec2ab monoeg_malloc (mono-sgen + 0x4ec2ab) #17 0x00000000008eaacb n/a (mono-sgen + 0x4eaacb) #18 0x00000000008eaf01 monoeg_g_utf8_to_utf16 (mono-sgen + 0x4eaf01) #19 0x000000000075f396 mono_string_new_checked (mono-sgen + 0x35f396) #20 0x00000000007ae829 n/a (mono-sgen + 0x3ae829) #21 0x000000000070dd7a n/a (mono-sgen + 0x30dd7a) #22 0x00000000006faca9 n/a (mono-sgen + 0x2faca9) #23 0x000000004205e3b2 n/a (n/a + 0x0) #24 0xff01a8c000040008 n/a (n/a + 0x0)

systemd-coredump

[Rugby (aka Daniel or Big Dan)]

I’ve always used ubuntu if I was using Linux. Tested Roon with 10 different distros and found it to be the easiest to work with. Arch linux works but is not as easy to setup.

Why not Rock, if you don’t mind my curiosity.

[Phil_Ryan]

Looking at some post people seemed to want the use a full OS, and having no skills it seemed to be the easiest. way of seeing if the OS was running and monitor it, I didn’t really understand the Rock install process.

The NUC only runs Roon so I’m quite happy to do a rebuild if I continue to have issues…

[fr3akX (Just a music geek)]

having similar problem on ubuntu, from time to time play stops, roons server has crashed with
Native stacktrace:
=================================================================
0x5098ec - /app/RoonServer/RoonMono/bin/RoonAppliance :
0x5098ec - /app/RoonServer/RoonMono/bin/RAATServer :
0x509d17 - /app/RoonServer/RoonMono/bin/RoonAppliance :
0x509d17 - /app/RoonServer/RoonMono/bin/RAATServer :
0x470941 - /app/RoonServer/RoonMono/bin/RoonAppliance :
0x470941 - /app/RoonServer/RoonMono/bin/RAATServer :
0x425704 - /app/RoonServer/RoonMono/bin/RoonAppliance :
0x425704 - /app/RoonServer/RoonMono/bin/RAATServer :
0x4257ba - /app/RoonServer/RoonMono/bin/RoonAppliance :
0x4257ba - /app/RoonServer/RoonMono/bin/RAATServer :
0x7f908ef150e0 - /lib/x86_64-linux-gnu/libpthread.so.0 :
0x7f937191f0e0 - /lib/x86_64-linux-gnu/libpthread.so.0 :
0x7f908e9c8f3c - /lib/x86_64-linux-gnu/libc.so.6 : __libc_malloc
0x7f93713d2f3c - /lib/x86_64-linux-gnu/libc.so.6 : __libc_malloc
0x8ec2ab - /app/RoonServer/RoonMono/bin/RAATServer : monoeg_malloc
0x8ec2ab - /app/RoonServer/RoonMono/bin/RoonAppliance : monoeg_malloc
0x8eaacb - /app/RoonServer/RoonMono/bin/RAATServer :
0x8eaacb - /app/RoonServer/RoonMono/bin/RoonAppliance :
0x8eaf01 - /app/RoonServer/RoonMono/bin/RAATServer : monoeg_g_utf8_to_utf16
0x8eaf01 - /app/RoonServer/RoonMono/bin/RoonAppliance : monoeg_g_utf8_to_utf16
0x75f396 - /app/RoonServer/RoonMono/bin/RoonAppliance : mono_string_new_checked
0x75f396 - /app/RoonServer/RoonMono/bin/RAATServer : mono_string_new_checked
0x7ae829 - /app/RoonServer/RoonMono/bin/RAATServer :
0x7ae829 - /app/RoonServer/RoonMono/bin/RoonAppliance :
0x70dd7a - /app/RoonServer/RoonMono/bin/RAATServer :
0x70dd7a - /app/RoonServer/RoonMono/bin/RoonAppliance :
0x6faca9 - /app/RoonServer/RoonMono/bin/RoonAppliance :
0x6faca9 - /app/RoonServer/RoonMono/bin/RAATServer :
0x402e93d2 - Unknown
0x41bc9b82 - Unknown

[Phil_Ryan]

I’m still getting the odd instance of this, not enough to be annoying.

I wonder if a Rock install would be the way forward?

No idea about these things on Linux, can you monitor Rock or do you have to update it?

[Andreas_Philipp1]

Roon doesn’t get on nicely with NetworkManager which manages network devices and connections both on Ubuntu Desktop and Linux Mint. You have basically two options:

If your Roon core runs on a headless Linux server, I would simply install Ubuntu server which doesn’t suffer from this problem. I have done so myself.

The other option is to reconfigure your Linux so that it doesn’t use NetworkManager to manage network devices. Instead it can delegate to networkd which is default on Ubuntu Server.

Please refer to this thread for further illustration about the problem and a workaround:

Intermittent loss of connectivity to Roon Server and music stops

Core Machine (Operating system/System info/Roon build number) Roon Server installed 1.7 (Roon Version 1.7 (build 667) stable) on Ubuntu 20.04.1 LTS. Roon Server installed on hardware with i5 -9500T with 16GiB DDR4 SODIMM and Western Digital SN720 NVMe SSD. 76000+ tracks stored on external USB 3.0 (connected to core) Western Digital EasyStore HDD formatted as EXT4 (10TiB). Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet) Core and endpoint are hardwired t…

Here you’ll find instructions on how to reconfigure Ubuntu Desktop:

Crashing on Linux

Hi @Harald_Pott, I had a very similar problem as you have. The hypothesis is that the network configuration tool NetworkManager used by Ubuntu Desktop may be involved. So I ended up reinstalling my machine with Ubuntu Server which does not use this tool for Ethernet interfaces. But there are ways to reconfigure Ubuntu Desktop so it won’t use NetworkManager to configure Ethernet but networkd, another tool. Please note that this only is about Ethernet interfaces, not WiFi. For WiFi configuratio…

@dylan and @noris know about the problem. Let’s hope the Roon QA team can come up soon with a solution to the root cause of this problem. I am sure there are quite a lot of users affected.

[Phil_Ryan]

Thanks for the info, I’ll have a good read and try and make the changes in the morning.

[Phil_Ryan]

Hi Andreas

Can I just confirm I’m understanding the file creation?
Sorry my knowledge in this area is limited to what I can read and understand

My IP is 192.168.1.190/24

So if I’m reading correctly I create a new file as below
addresses: [192.168.1.254, 8.8.8.8] these being my router IP and the google DNS.

network:
version: 2
renderer: NetworkManager
ethernets:
eno1:
renderer: networkd
match:
name: eno1
dhcp4: false
addresses: [192.168.1.190/24]
gateway4: 192.168.1.254
nameservers:
addresses: [192.168.1.254, 8.8.8.8]

Many thanks Phil

[Andreas_Philipp1]

@Phil_Ryan

network:
   version: 2
   renderer: NetworkManager
   ethernets:
      eno1:
         renderer: networkd
         match:
            name: eno1
         dhcp4: false
         addresses: [192.168.1.190/24]
         gateway4: 192.168.1.254
         nameservers:
            addresses: [192.168.1.254, 8.8.8.8]

Yes, but you’ll have to mind the indents, that’s the tricky part. And your file assumes that your ethernet interface is named ‘eno1’ on your NUC. You can find the name using ip a on the command line. This also assumes that you effectively use this ethernet interface to connect to your network.

By this configuration you declare that you wish NetworkManager to take care of devices and network communication per default, but that the ethernet device ‘eno1’ should be managed by networkd. You at the same time configure ‘eno1’ with a static IP, assigning the gateway and name servers.

Please mind that I don’t have any experience with Linux Mint. I have tested this configuration on Ubuntu 20.04, but if you find the /etc/netplan directory on your NUC we can assume that Mint, too, uses Netplan to declare network configuration. In that case, this should work.

Good luck!

[Phil_Ryan]

Yes its the same name…

2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 1c:69:7a:66:a1:d4 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.190/24 brd 192.168.1.255 scope global dynamic noprefixroute eno1

[Andreas_Philipp1]

Phil, another thing I just remembered… please make sure you use spaces to indent the configuration file, not tabs. Using tabs it won’t work.