Roon core crashes on boot on Ubuntu server

Core Machine (Operating system/System info/Roon build number)
Ubuntu server
Roon running in Docker container (using this image)
Container managed via compose file
This setup worked absolutely fine a few days ago so whatever did this was a recent change to Roon.

Description Of Issue
After running docker-compose up the container is properly created and started, however the app crashes shortly afterwards with following stacktrace

    roon-server  |e[0m aac_fixed decoder found, checking libavcodec version...
    roon-server  |e[0m has mp3float: 1, aac_fixed: 0
    roon-server  |e[0m Running
    roon-server  |e[0m terminate called after throwing an instance of     'OpenHome::NetworkError'
    roon-server  |e[0m Stacktrace:
    roon-server  |e[0m 
    roon-server  |e[0m   at <unknown> <0xffffffff>
    roon-server  |e[0m   at (wrapper managed-to-native)     OpenHome.Net.ControlPoint.CpDeviceListUpnpServiceType.CpDeviceListCreateUpnpServic    eType     (intptr,intptr,uint,OpenHome.Net.ControlPoint.CpDeviceList/CallbackDevice,intptr,OpenHome.    Net.ControlPoint.CpDeviceList/CallbackDevice,intptr) [0x00030] in     <21295a8acb1a4b59920209b723ef0864>:0
    roon-server  |e[0m   at OpenHome.Net.ControlPoint.CpDeviceListUpnpServiceType..ctor     (string,string,uint,OpenHome.Net.ControlPoint.CpDeviceList/ChangeHandler,OpenHome.Net.    ControlPoint.CpDeviceList/ChangeHandler) [0x00042] in     <21295a8acb1a4b59920209b723ef0864>:0
    roon-server  |e[0m   at     OpenHome.Net.ControlPoint.CpUpnpDeviceListFactory.CreateListServiceType     (string,string,uint,OpenHome.Net.ControlPoint.CpDeviceList/ChangeHandler,OpenHome.Net.    ControlPoint.CpDeviceList/ChangeHandler) [0x00007] in     <21295a8acb1a4b59920209b723ef0864>:0
    roon-server  |e[0m   at Sooloos.Broker.Transport.SongcastDirect.ReInit () [0x00235] in     <b547e688cd0442d6941264aab090c074>:0
    roon-server  |e[0m   at Sooloos.Broker.Transport.SongcastDirect..ctor     (Sooloos.Broker.State,Sooloos.Broker.Transport.Module) [0x0007e] in         <b547e688cd0442d6941264aab090c074>:0
    roon-server  |e[0m   at Sooloos.Broker.Transport.Module.Enable () [0x001e9] in     <b547e688cd0442d6941264aab090c074>:0
    roon-server  |e[0m   at Sooloos.Broker.Transport.Module.UpdateEnabled () [0x00035] in     <b547e688cd0442d6941264aab090c074>:0
    roon-server  |e[0m   at Sooloos.Broker.Transport.Module.Init (Sooloos.Broker.Database)     [0x000bf] in <b547e688cd0442d6941264aab090c074>:0
    roon-server  |e[0m   at Sooloos.Broker.State._InitTransportThreadAsync () [0x0000c] in     <b547e688cd0442d6941264aab090c074>:0
    roon-server  |e[0m   at Sooloos.SynchronizationContextThread/<>c__DisplayClass45_0.    <Post>b__0 (object) [0x00006] in <dc03b11aba8c4db1b75c29f20078d986>:0
    roon-server  |e[0m   at Sooloos.SynchronizationContextThread._Dispatch     (Sooloos.SynchronizationContextThread/SendOrPostWrapper&) [0x0001e] in     <dc03b11aba8c4db1b75c29f20078d986>:0
    roon-server  |e[0m   at Sooloos.SynchronizationContextThread._Go () [0x00025] in     <dc03b11aba8c4db1b75c29f20078d986>:0
    roon-server  |e[0m   at System.Threading.ThreadHelper.ThreadStart_Context (object)     [0x0001f] in <370a0c27f4b74d1a81431037df6d75bf>:0
    roon-server  |e[0m   at System.Threading.ExecutionContext.RunInternal     (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool)     [0x00073] in <370a0c27f4b74d1a81431037df6d75bf>:0
    roon-server  |e[0m   at System.Threading.ExecutionContext.Run     (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool)     [0x00004] in <370a0c27f4b74d1a81431037df6d75bf>:0
    roon-server  |e[0m   at System.Threading.ExecutionContext.Run     (System.Threading.ExecutionContext,System.Threading.ContextCallback,object) [0x0002f] in     <370a0c27f4b74d1a81431037df6d75bf>:0
    roon-server  |e[0m   at System.Threading.ThreadHelper.ThreadStart () [0x00014] in     <370a0c27f4b74d1a81431037df6d75bf>:0
    roon-server  |e[0m   at (wrapper runtime-invoke) object.runtime_invoke_void__this__     (object,intptr,intptr,intptr) [0x0004f] in <370a0c27f4b74d1a81431037df6d75bf>:0
    roon-server  |e[0m /proc/self/maps:
    roon-server  |e[0m 00400000-0096e000 r-xp 00000000 08:02 924781                                 /app/RoonServer/RoonMono/bin/mono-sgen
    roon-server  |e[0m 00b6d000-00b71000 rw-p 0056d000 08:02 924781                                 /app/RoonServer/RoonMono/bin/mono-sgen
    roon-server  |e[0m 00b71000-00bc8000 rw-p 00000000 00:00 0 
    roon-server  |e[0m 01294000-01b7e000 rw-p 00000000 00:00 0                                      [heap]
    roon-server  |e[0m 41a25000-41a35000 rwxp 00000000 00:00 0 
    roon-server  |e[0m 41a6d000-4207d000 rwxp 00000000 00:00 0

What version of Roon are you running now and what version of Roon was running when it previously work?

I’m unable to determine what version was running before when it was working now but the container pulls the fresh installer from so it’s the newest available one that fails.

Build 528 is the latest but it’s been out for almost a month now … I suspect the problem you are seeing is more likely a network stack environment issue than any change to Roon … but not knowing what version of Roon was running when it did work of cause means that can’t be conclusive.

If you still have the logs from that time … you might be able to identify the build number.

Let’s see if @support can shed any light … but iirc running Roon in docker is not officially supported.

Fingers crossed the root cause can be identified.

This type of error is typically caused by other software (Emby and Plex were often mentioned in the past) already using ports that Roon Server tries to claim for itself. Please note that Running Roon Server in a Docker image is not supported. The thread might get moved to #tinkering.

See also:

I am running Plex on the same machine (also in a container). I’ll look into it, thanks.

Roon is able to start once I changed network mode on the Plex container from bridged to host. I don’t know what other issues this will create, will report back.
@Carl Why isn’t Docker officially supported as a deployment option? A lot of folks want to run Roon as one of multiple services on their server/nas.

Hi @Yethal,

I moved your post over to #tinkering.

The currently supported Roon Cores are listed in our Minimum Requirements doc. While the Docker container may or may not work as expected, we don’t perform any testing on Docker/VMs in the QA lab, so we can’t really say for sure how Roon is expected to run in such environments.

In that case, can I put in a feature request to add Docker as official installation method? That would involve (aside from testing) pushing a ready-to-use docker-image to Docker Hub whenever there is a Core update. That would greatly simplify use of Roon on platforms such as FreeNas or UnRaid.

Thanks for the feedback here. Since your proposed setup is not currently officially supported, I would suggest you post your suggestion in the feature request section of the site.

Our product team and developers keep a close eye on that category, so that’s definitely the best place to propose a change like this and get feedback from the Community.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.