Sage server crashing

[Batman7349]

Window 10 performed an update 2 days ago. Ever since it seems that my server quits and does not restart. I have to reboot the system, then power down my 4 HD 300’s so that the configuration loading screen appears before things work again. Just turning off the HD 300’s after a reboot will not work, just no signal or blank screen. Anybody else having issues after last update? This has been a once or twice a day event.

[wnjj]

Does the log file sagetv_0.txt have anything of interest at the bottom after the crash? Are there any hs_err_pid.log files?

[Batman7349]

I thought the issue had resolved itself, but last night the sagetv service crashed 3 times in a ten minute span. I tried stopping and restarting the service but that did not work. I had to reboot the system. I'm not an expert reading the file so I have uploaded it. Maybe the comskip plug in. Or maybe i need to increase the ram on the server. Running Windows 10 with 4GB ram on an older EP45-UD3P motherboard.

[tmiranda]

Originally Posted by Batman7349

I thought the issue had resolved itself, but last night the sagetv service crashed 3 times in a ten minute span. I tried stopping and restarting the service but that did not work. I had to reboot the system. I'm not an expert reading the file so I have uploaded it. Maybe the comskip plug in. Or maybe i need to increase the ram on the server. Running Windows 10 with 4GB ram on an older EP45-UD3P motherboard.

There is no smoking gun in the logfile. The logging just suddenly stops with no errors at all.

Was the server running when you grabbed this logfile or had it crashed already?

[wnjj]

Are there any hs_err_pid*.log files in the Sage directory? Those are left behind if the Java engine crashes hard and can sometimes help.

[Batman7349]

The Sage service box said service running but none of my 3 HD300's could find an IP address. I would stop then restart the service but again the HD300's can not find an IP address. Reboot the computer and then the HD300's can obtain the IP address. Maybe its an issue with the PC. I'm going down to look for the java log....