Sage crashes after reboot of docker container

[Brewer]

Rebooted my sage docker container today in order to get the latest sage update...now sage service doesn't stay up. Is this a known problem? If so, is there a setting I can set to use the previous version?

I do have an hs_err_pid.log and sagetv_0.txt if someone wants more info.

[EnterNoEscape]

Please post the logs.

[Brewer]

Attached are the 2 log files. Thanks for taking a look...

[Brewer]

What is the best way to revert back to the previous sage version?

[EnterNoEscape]

The bug you're seeing is related to your HDHomeRun tuners. I'm surprised you're just seeing it now. Technically you should have seen this problem before too since nothing has changed in that area for a while. I've played with the built in support and unfortunately all I can say is what's normal in the logs and what's not. Oddly enough 1 is the value stored in mmc/country_code which is where as far as I can tell is where that 5th parameter is coming from, yet in practice the logging appears to be returning a memory address when things are running normally. What's happening in your case is instead of the address, I'm seeing the actual value held in the address in the logging and then that fails essentially reporting that it tried to read an inaccessible memory address.

This is normal:

Sat 1/28 15:21:44.225 [Scheduler@9602829] HDHR_setInput0(0x7f69dc719fd0, 100, 0, Air, 140088948293633, 140088948293633)

This is not normal:

Sat 1/28 15:21:47.176 [Scheduler@9602829] HDHR_setInput0(0x7f69dc719e00, 100, 0, Air, 1, 140088948293633)

Try creating a file named NATIVE_LOG.ENABLE all caps in the SageTV server folder, then restart SageTV. You should then get a new log file called Native.log. Post that too.

[Brewer]

I finally succeeded in getting things working. Ended up removing the hdhomerun sources, then adding back in and doing a channel rescan. Now it boots up fine. Not sure why it occurred in the first place. Thanks for your help!