#195 Subsonic Server silently crashes (Raspberry Pi)

[Anonymous]

Subsonic server silently crashes on the Raspberry Pi 2 with Raspbian light (Jessie). The logs don't show anything.

I am using OpenJDK JRE 7.0 and SubSonic 6.0. I noticed that over time memory usage is increasing more and more.

[Anonymous]

I notice the Garbage Collector is called a lot of times. These are latest logs (after restarting subsonic server)
[GC 67963K->42199K(92880K), 0.0368660 secs]
[GC 67927K->42211K(92880K), 0.0368260 secs]
[GC 67939K->42213K(92880K), 0.0346610 secs]
[GC 67941K->42233K(92880K), 0.0307930 secs]
[GC 67961K->42297K(92880K), 0.0297790 secs]
[GC 68024K->42221K(92880K), 0.0268600 secs]
[GC 67949K->42234K(92880K), 0.0215350 secs]
[GC 67962K->42287K(92880K), 0.0192170 secs]
[GC 68014K->42215K(92880K), 0.0173190 secs]
[GC 67943K->42202K(92880K), 0.0156890 secs]
[GC 67930K->42206K(92880K), 0.0170300 secs]
[GC 67929K->42252K(92880K), 0.0146920 secs]

[Anonymous]

I finally got this error captured:

fatal error: caught unhandled signal 11

[Anonymous]

I am experiencing the same. Subsonic is not running within a day from starting. There is nothing in the logs.

[Anonymous]

To provide more info: I tried Subsonic using Oracle Java 8 (INFO SettingsService - Java: 1.8.0_65, OS: Linux). Same story. First a lot of garbage collecting, until it collapse and just crashes.

[Anonymous]

We've struggled with this as well. Unexpected failures without anything in a log. Out of the desperate we downgraded back to 5.3.

Failures with empty log continued... We realized that we also moved to amazon nano instance with only 500MB RAM witch ubuntu configured without swap. In dmesg we found out that OOM killer is killing our job despite we set up subsonic/java to run only with --max-memory 150MB.

We added 8GB swap to the machine, and we increased --max-memory to 500MB. Let's see if this helps... after few hours it looks stable. Since you see a lot of garbage collector runs, it might be also the memory problem.

However, "fatal error: caught unhandled signal 11!" looks pretty strange to me. Looks like unrelated problem. I am not Java programer, but signal 11, is segfault, which is common if there is bug in C++, but AFAIK pretty difficult to create in Java program (when programmer is staying in common java practices and don't need anything really low level.)

Good luck!

[Anonymous]

So there is definitely a memoryleak somewhere.
I will be happy to hear from you Sindre!

[Anonymous]

Have tried adding swap, and increased max memory to 350mb (the amount i still had left), some problem, but it only takes a little longer before it crashes from ~3 hours to ~ 5 hours.
I have a temporary workaround for now: I have a Cronjob running every 3 hours that will restart subsonic. for from ideal, but hey! it works!

Let's wait for a fix from Sindre

[Anonymous]

No problems with Subsonic 6.0 on my Raspberry Pi 3 running latest Raspbian and Oracle Java 8u65. Running since months. Ok, with casual reboots for updates...

[Anonymous]

I am having the same issue on subsonic 6.1.3 open jdk 7.
I setup a second jail on my Nas4free system on BSD 10, open jdk 8 jre with subsonic 6.0 and the same media folders. to test to see if crashes.

If no crash, Ill upgrade the subsonic version to see if that is the cause.