Roon Server on Ubuntu Server
Every few hours I need to reboot/restart the roon server for a OOM error. This is new/much more frequent since last update. See attached screen shot.
I have read the older topics, I never had this before. Use Roon since >1year quite often. Since last update becomes a real painful problem with more than daily restarts.
JP
How much memory does your system have, and what other processes are running? Likewise, how large is your library, and what CPU do you use?
Note that oom-kill is a kernel process, and the process affected isn’t necessarily the culprit (it’s a consequence of the kernel over allocating memory.) Typically, it is the process that uses (allocated) the most memory that is killed first.
Getting the same here, oom killing roonservice. Never had issue until latest release.
Need to restart every morning, 16G ram standalone server.
Keith
Same thing here, have to restart every day, it could run for weeks previously
Hi Martin, I’m running Ubuntu vs 22.04 on a NUC i5 with 64Gb RAM. According to TOP, Roon is taking 23% of memory at the moment (now it works, had to restart this morning) and approximately 10-15% of CPU.
Example from my side
roonserver.service - RoonServer
Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; vendor preset: enabled)
Active: failed (Result: oom-kill) since Mon 2023-03-13 20:39:08 GMT; 1 day 1h ago
Main PID: 3623317 (code=killed, signal=TERM)
CPU: 4h 1min 34.346s
Mar 13 02:02:03 philippe-NUC10i7FNH start.sh[3623321]: Initializing
Mar 13 02:02:03 philippe-NUC10i7FNH start.sh[3623321]: 01 days, 06:28:58.148 Debug: RoonServer, before attempting to start RoonAp>
Mar 13 02:02:03 philippe-NUC10i7FNH start.sh[3623321]: 01 days, 06:28:58.158 Debug: RoonServer, after starting RoonAppliance
Mar 13 02:02:03 philippe-NUC10i7FNH start.sh[3623321]: Started
Mar 13 02:02:04 philippe-NUC10i7FNH start.sh[3192143]: aac_fixed decoder found, checking libavcodec version…
Mar 13 02:02:04 philippe-NUC10i7FNH start.sh[3192143]: has mp3float: 1, aac_fixed: 1
Mar 13 02:02:05 philippe-NUC10i7FNH start.sh[3623321]: Running
Mar 13 20:39:07 philippe-NUC10i7FNH systemd[1]: roonserver.service: A process of this unit has been killed by the OOM killer.
Mar 13 20:39:08 philippe-NUC10i7FNH systemd[1]: roonserver.service: Failed with result ‘oom-kill’.
Mar 13 20:39:08 philippe-NUC10i7FNH systemd[1]: roonserver.service: Consumed 4h 1min 34.346s CPU time.
…skipping…
× roonserver.service - RoonServer
Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; vendor preset: enabled)
Active: failed (Result: oom-kill) since Mon 2023-03-13 20:39:08 GMT; 1 day 1h ago
Main PID: 3623317 (code=killed, signal=TERM)
CPU: 4h 1min 34.346s
Running Ubuntu 22.04 on a NUC i7 with 8Gb RAM
Looks a very similar issue to me. Any idea if the Roon engineers will fix the software bug @Martin_Webster do you have an idea?
Is it possible that my roon server software on the NUC is not up to date? How can I check that?
Thx
@JP_Bogers, I’m a fellow user like you, so don’t know whether this is a bug or a local issue. My Linux core is currently turned off, and I’ve not had an opportunity to check it yet.
To check versions, go to Roon Settings > About.
Current versions are shown here:
Hey @JP_Bogers,
Ben here with the support team, thanks for your patience while our team continues to work through each thread. I wanted to check the status of your issue here?
If possible, could you please take note of the date and time the next time you run into this OOM error?
With that, I’d be curious to see how things run on a fresh database:
Continue to test things before restoring from a backup. 
This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.
