|
SageTV v7 Customizations This forums is for discussing and sharing user-created modifications for the SageTV version 7 application created by using the SageTV Studio or through the use of external plugins. Use this forum to discuss plugins for SageTV version 7 and newer. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Server crashing...comskip?
I have been having an issue with my server shutting off every night (between 11:10-11:50) for the past two weeks. My server is running Win 7 x64 on an AMD Athlon II quad core CPU (3.1 Ghz) and 4 GB of RAM. Three HDPVRs (my only tuners) Sage 7.19.256. and commercial detector 1.00.
The event viewer (system) shows the same four events every-time it happens. All telling me the system "uncleanly shut down". I have actually witness it happening. Comskip is processing three files and then with no warning the server shuts off. There is nothing that is scheduled to run at that time other then compskip processes recordings. Commercial detector is configured to process 3 recordings at the same time. "Play nice" is enabled and live TV processing is turned off. Also the are no BSOD dump files. I have tried comskip (donators) 81_023 and 81_052 both with the same results. However if I disable Commercial detector and all relating plugins, the server stays over night. I have scanned my server with Windows security essentials and Defender and nothing was found. I have scanned all my HDs with a short self test and they have all passed. I have double checked all my power settings and its configured to never sleep or hibernate unless running on my UPS battery. I have attached my log (Trace) can some take a look? Right now I'm at a loss...this is very frustrating!! THANX! |
#2
|
|||
|
|||
Could the processor be overheating and causing a shutdown?
__________________
Windows 10 Sagetv 9 64bit (9.2.5) HVR-2255 x3 OTA |
#3
|
|||
|
|||
Possible but not likely. The CPU is not overclocked. Both sides of the case are removed, so there is great air flow through the entire case. Also I would expect to see BSOD dump files for something like that, and I don't.
|
#4
|
|||
|
|||
I just fixed a problem with my system that would randomly shutdown without warning one or more times a week. It was caused by bad electrolytic capacitors on the motherboard and video card. Capacitors were bulged out. Might be worth looking into.
__________________
HTPC: Gigabyte GA-Z170XP-SLI, I7-6700, 16GB, Windows 10 Pro x64, Hauppauge HVR-1600, WinTV-dualHD, Colossus 2, Samsung 850 EVO 120GB, Seagate 3TB, WD 3TB, 3TB, 5TB, Java v1.8.0_231, SageTVx64 v9.2.1.826, Samsung UN60EH6003F, Dish ViP222K, ViewHD 1x2 HDMI Splitter. |
#5
|
||||
|
||||
Is this the only time you are processing 3 comskip recordings at a time? I've never seen a bit of software be able to take down a win7 system like that - it is almost certainly a hardware issue - either a power supply, MB regulator, or a cpu/north bridge heat issue.
__________________
Buy Fuzzy a beer! (Fuzzy likes beer) unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers. Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA. Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S Other Clients: Mi Box in Master Bedroom, HD-200 in kids room |
#6
|
|||
|
|||
Quote:
Quote:
I don't have any popped or bulging caps on my MB. In my experience popped or bulging caps cause more random unpredictable issues. My issue occurs at a specific range of time every night consistently. @Fuzzy This was my initial thought as well. But short of running a full diagnostic of every piece of hardware I have not been able to pin point the issue. Also usually there are BSOD when hardware crashes and there are no dump files. A couple days ago I decided to change my list of restricted times (from everything restricted except 11pm-5am) to everything restricted except 7am-4pm) At 11:15 pm comskip is not running. I check the commercial detector queque and there are recordings in the queue. The the next morning @6am my server was still running and all recordings in the queque had already been processed. This has continued for at least three days. This is good because my recordings are getting processed and my server isn't crashing but I don't know when the recordings are actually being processed. I want to make sure its not during my daily backup. Can someone check my logs? THANX! Last edited by nettech_gt; 04-03-2013 at 09:37 AM. |
#7
|
|||
|
|||
Sure sounds like CPU overheating. Maybe repaste the CPU/heatsinnk. Also having the sides of can often slow the movement of air in many cases causing them to run hotter.
Heavy disk activity could tip a marginal power supply. Other symptoms include not always firing up the disk during a cold boot. Grant |
#8
|
||||
|
||||
Quote:
Things like a bad memory chip, or bad peripheral, will most often result in a BSOD. It actually takes a still functioning processor to generate a BSOD, and sump memory to disk. However, a problem in the power supply, or mainboard voltage regulator, will usually result in a reeset of the CPU itself midstream, which sometimes will cause the monitoring system on the motherboard to shut down the power supply, or at best, force a reboot. Neither action will generate a BSOD, or any log entries.
__________________
Buy Fuzzy a beer! (Fuzzy likes beer) unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers. Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA. Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S Other Clients: Mi Box in Master Bedroom, HD-200 in kids room |
#9
|
|||
|
|||
Quote:
Quote:
I definitely think if could be a hardware issue.This certainly fits the best. In fact my first thought was it was the power supply. However when I moved the restricted times for commercial detector so my recordings would not process during the time I was consistently having the sever crash.(11pm-11:50pm) The issue "seems" to have gone away. The server is not crashing and my recordings are being processed. However as far I can tell comskip is not obeying the new restriction times. So if the issue is the power supply, motherboard or CPU is getting overloaded/overheated doesn't it make sense that the same amount of load/heat but at a different time would produce the same results? Yet this is not what is happening... I will run a diagnostic on all the hardware. Just so I verify or rule it out. In the mean can some please check my logs (a couple posts up) and see if they can tell when my recordings got processed? THANX! |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
SageTV Server crashing on Ubuntu | 3tones | SageTV Linux | 3 | 04-18-2009 11:02 AM |
SageTV Server keeps crashing | grauchy | SageTV Software | 2 | 02-21-2008 09:35 AM |
SageTV 4.1 is crashing Win2003 server | SethV | SageTV Software | 7 | 02-03-2006 11:16 PM |
MVP Server crashing | Ralnee | SageTV Software | 2 | 11-11-2003 08:39 AM |