SageTV crash Aborted java

[wayner]

My SageTV server wasn't working yesterday. I am not 100% sure if this was an unRAID issue or a Sage issue, but I rebooted.

Today I noticed that the SageTV server process was not working. Looking at the logs for the docker I see:

/usr/local/bin/startsagecore: line 75: 316 Aborted java -Djava.awt.headless=$HEADLESS $JAVAMEM -XX:+UseAdaptiveSizePolicy -XX:MaxGCPauseMillis=25 -XX:GCTimeRatio=24 $(if [[ $EUID -eq 0 ]]; then echo '-XX:ThreadPriorityPolicy=1'; fi) $JAVAOPTS -cp Sage.jar:JARs/lucene-core-3.6.0.jar:/:$(echo JARs/*.jar | sed 's/ */:/g') sage.Sage 0 0 x "sagetv Sage.properties" 0>&-

Anyone have any insight as to what the issue could be? Are there any other logs I can look at to see what may have happened?

This is a server I built in January of 2022 and it was been running flawlessly since then.

I am running unRAID 6.10.o-rc2 which hasn't changed since the initial install and

[jusjoken]

If you restart the docker do you get the same error?

If so, can you post the full log?

k

[wayner]

I restarted and it has been good for about 30 hours so far.

[wayner]

It crashed again this morning:

Aug 25 06:17:01 85951431ed37 CRON[24690]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 25 06:25:01 85951431ed37 CRON[24699]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Aug 25 06:35:50 85951431ed37 syslog-ng[23]: Configuration reload request received, reloading configuration;
Aug 25 06:35:50 85951431ed37 syslog-ng[23]: Configuration reload finished;
/usr/local/bin/startsagecore: line 75: 295 Aborted java -Djava.awt.headless=$HEADLESS $JAVAMEM -XX:+UseAdaptiveSizePolicy -XX:MaxGCPauseMillis=25 -XX:GCTimeRatio=24 $(if [[ $EUID -eq 0 ]]; then echo '-XX:ThreadPriorityPolicy=1'; fi) $JAVAOPTS -cp Sage.jar:JARs/lucene-core-3.6.0.jar:/:$(echo JARs/*.jar | sed 's/ */:/g') sage.Sage 0 0 x "sagetv Sage.properties" 0>&-
Aug 25 07:17:01 85951431ed37 CRON[24778]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Aug 25 08:17:01 85951431ed37 CRON[24783]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

I don't know if this is a coincidence or not but the crash appeared to be between 6:35 and 7:17. I believe the previous crash was at a similar time. The sagetv_0.txt log was last updated at 7:01. I have saved that file if that will be helpful.

Here is the tail of the sagetv_0.txt log:

Thu 8/25 7:01:19.364 [Fork-MUWSG-513715@3e894be4] Updating Disk Space Bar
Thu 8/25 7:01:19.374 [Fork-MUWSG-513715@3e894be4] Got used/avail video diskspace
Thu 8/25 7:01:19.374 [Fork-MUWSG-513715@3e894be4] Calculate size of partial recordings
Thu 8/25 7:01:19.374 [Fork-MUWSG-513715@3e894be4] Found 0 partials using 0 bytes
Thu 8/25 7:01:19.393 [Fork-MUWSG-513715@3e894be4] Calculate space required for upcoming manual/favourite airings for next X hours and display
Thu 8/25 7:01:19.412 [Fork-MUWSG-513715@3e894be4] VideoDiskspaceReqProportion: 0.4791175137689226
Thu 8/25 7:01:19.412 [Fork-MUWSG-513715@3e894be4] VideoDiskspaceFreeProportion: 0.4670321524575521
Thu 8/25 7:01:19.412 [Fork-MUWSG-513715@3e894be4] Disk Space Bar Update complete for UI context 80e82cca01a0
Thu 8/25 7:01:19.431 [ActiveRender-80e82cca01a0@5081bd22] ZRoot is aborting this draw because its unnecessary
Thu 8/25 7:01:34.786 [ThreadMonitor@4e4150cf] Top 10 Cumulative CPU(sec) Scanner-0:1218 FinalRender-0023a50009c7:397 FinalRender-0023a5000654:393 MiniUIClientReceiver:319 MiniUIClientReceiver:277 Fork-MUWSG-513715:107 ActiveRender-80e82cca01a0:86 ActiveRender-0023a50009c7:84 ActiveRender-0023a5000654:83 EPG:37
Thu 8/25 7:01:34.787 [ThreadMonitor@4e4150cf] Top 10 %CPU (last 300s)

[jusjoken]

Perhaps look at what cron jobs are running at 0617 to 0635. Could be related

If those are the last lines in sage log and based on the aborted message my guess is something else killed sage. Do other dockers keep operating?

k

[wayner]

Other dockers are fine and continue to operate properly. It seems like the SageTV docker is still alive but the SageTV process within the docker aborts.

Are there any other log files that are created or something to check when the Java process crashes?

[wnjj]

You can look for hs_err_pid* files. Java writes those when the engine itself crashes.