OpenDCT - timing issue causing "Halt detected in Recording" messages?

[mgpaulus]

Hi,

I just rebooted and cleared out my System Messages, and I noticed that I have gotten several "Halt detected in Recordings" messages. So I decided to go investigate.

Seems like there is some kind of either error, or a timing issue. I will attach the relevant OpenDCT.log and sagetv_x.txt files. However, one thing I see are several of these messages in my sagetv_x.txt file:
Sat 2/24 13:57:26.360 [Seeker@1479697] Error communicating with encoding server:java.lang.NumberFormatException: For input string: "ERROR failed request"

This makes it look like the request never got to OpenDCT, and then when Seeker goes to look for data, it isn't there, because the encoder was never informed to start doing anything.

There is a problem with a Bobby Flay episode "LikeFatherLikeDaughter", and there is a problem with an olympics episode, "2018WinterOlympics-SpeedSkatingMensCrossCountrySkiing" and a couple of others. Timing seems to be all right around 13:57 or 13:58, and there are 5 messages all at once.

I've also attached the segment of wrapper.log which covers today, where I noticed there is a Java Fatal Error - Maybe this is the root of my problem??

INFO | jvm 1 | 2018/02/24 13:57:19.340 | #
INFO | jvm 1 | 2018/02/24 13:57:19.340 | # A fatal error has been detected by the Java Runtime Environment:
INFO | jvm 1 | 2018/02/24 13:57:19.340 | #
INFO | jvm 1 | 2018/02/24 13:57:19.340 | # Internal Error (numberSeq.cpp:102), pid=2100, tid=7836
INFO | jvm 1 | 2018/02/24 13:57:19.340 | # guarantee(var >= 0.0) failed: variance should not be negative
INFO | jvm 1 | 2018/02/24 13:57:19.340 | #
INFO | jvm 1 | 2018/02/24 13:57:19.340 | # JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15)
INFO | jvm 1 | 2018/02/24 13:57:19.340 | # Java VM: Java HotSpot(TM) Client VM (24.80-b11 mixed mode windows-x86 )
INFO | jvm 1 | 2018/02/24 13:57:19.340 | # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
INFO | jvm 1 | 2018/02/24 13:57:19.340 | #
INFO | jvm 1 | 2018/02/24 13:57:19.340 | # An error report file with more information is saved as:
INFO | jvm 1 | 2018/02/24 13:57:19.340 | # c:/ProgramData/OpenDCT/logs/hs_err_pid2100.log
INFO | jvm 1 | 2018/02/24 13:57:19.440 | #
INFO | jvm 1 | 2018/02/24 13:57:19.440 | # If you would like to submit a bug report, please visit:
INFO | jvm 1 | 2018/02/24 13:57:19.440 | # http://bugreport.java.com/bugreport/crash.jsp
INFO | jvm 1 | 2018/02/24 13:57:19.440 | #
ERROR | wrapper | 2018/02/24 13:57:19.440 | JVM exited unexpectedly.
STATUS | wrapper | 2018/02/24 13:57:23.640 | Reloading Wrapper configuration...
STATUS | wrapper | 2018/02/24 13:57:23.642 | Launching a JVM...

and I've attached the hs_err_pid log file from the message.

Should I update my java version to see if that will clear up this fatal bug issue?

[EnterNoEscape]

I'm not 100% certain, but that crash looks like there's an issue with the version of Java you have installed. I say this because the JVM crashed getting the current time to write a log entry which is a little strange.

[mgpaulus]

Originally Posted by EnterNoEscape

I'm not 100% certain, but that crash looks like there's an issue with the version of Java you have installed. I say this because the JVM crashed getting the current time to write a log entry which is a little strange.

I thought I responded to this and mentioned that I upgrade to jdk1.7.0_161, but maybe I was having a nightmare and thought I typed it in. Anyway, I decided to upgrade to the latest 170 that I could find. Keeping my eyes peeled to see if it happens again. Thanks for the reply and 2nd set of eyes.

[EnterNoEscape]

Originally Posted by mgpaulus

I thought I responded to this and mentioned that I upgrade to jdk1.7.0_161, but maybe I was having a nightmare and thought I typed it in. Anyway, I decided to upgrade to the latest 170 that I could find. Keeping my eyes peeled to see if it happens again. Thanks for the reply and 2nd set of eyes.

I think you responded on another thread, but I didn't see that until I had already responded. Good luck with the new Java release.