[no Bug] TV Server constantly crashing since RC5 (1 Viewer)

[x4mer]

I was late upgrading to RC5, and didn't do it till a couple of days before RC6 was released. RC5 TV Server kept crashing, and before I could report it, RC6 was out. I've updated my server/clients to RC6, but the problem remains.

I loaded up the client on the server (single-seat) earlier today, & just left it till I saw the client complaining that the connection to the TV server had been lost. No TV was playing, MP was just sitting on the home screen. There were recordings happening on the TV Service though.

Debug mode logs attached.

 

[elliottmc]

I was late upgrading to RC5, and didn't do it till a couple of days before RC6 was released. RC5 TV Server kept crashing, and before I could report it, RC6 was out. I've updated my server/clients to RC6, but the problem remains.

I loaded up the client on the server (single-seat) earlier today, & just left it till I saw the client complaining that the connection to the TV server had been lost. No TV was playing, MP was just sitting on the home screen. There were recordings happening on the TV Service though.

Debug mode logs attached.

Could you try with only one card (try both types) enabled and see if one of your cards is causing the problem? It could be buggy drivers.

Mark

 

[x4mer]

I've been running the same drivers for months now, and the problem just started with RC5. I'll check whether there's an update for any of them, and possibly try disabling.


I'm just home for the evening to find that the service has crashed again. The logs I posted earlier have hundreds of errors complaing that the recording has already happened. Why does it keep loggin the same thing over and over. If it's a repeat, shouldn't it just log it once & not try to record it? It seem like it continues to try to start the recording for the whole duration of the show. These are advanced recordings set for "every time on this channel".

 

[jameson_uk]

Something looks a little off with your tuners (possibly not related but can you confirm) logs show

2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 BDA ATSC/QAM Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 BDA ATSC/QAM Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 BDA ATSC/QAM Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 BDA ATSC/QAM Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 Analog TV Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 Analog TV Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 Analog TV Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 Analog TV Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: preloading card :Hauppauge WinTV PVR PCI II TvTuner

so his has picked up 4 ATSC and 4 analog tuners (later on shows these as hybrid tuners) plus the PVR PC II

The logs also have config files for four analogue tuners on 7164 card and four analogue tuners on PVR PC II??


As you say logs are then spammed with

2010-07-11 20:54:17.571200 [scheduler thread(9)]: Scheduler: Check recordings for schedule The Next Food Network Star...
2010-07-11 20:54:17.572200 [scheduler thread(9)]: diskmanagement: recording The Next Food Network Star ended. type:Once max episodes:2147483647
2010-07-11 20:54:17.591200 [scheduler thread(9)]: Scheduler: Schedule 7/11/2010 8:00:00 PM-The Next Food Network Star (Grammy Award Celebration) has already been recorded (7/8/2010 8:57:10 PM) - aborting...

which I think is unrelated to your crash (on the recording tab in TVconfig do you have the "Check episode...prevent duplicate..." flag ticked? Also I take it that you have enough disk space? On that note I see that timesfift folder is in a UNC path when it is local \\GOLIATH\Video\Timeshift, this might cause an issue and I would suggest you convert this to a local path .

Another thing, do you use the disk quota option?


finally fails with

2010-07-12 00:12:28.529000 [TvClient-TvHome: HeartBeat transmitter thread(6)]: RemoteControl - timed out after 3002 msec
2010-07-12 00:12:30.536000 [TvClient-TvHome: HeartBeat transmitter thread(6)]: TCP connect took : 999
2010-07-12 00:12:30.596000 [TvClient-TvHome: HeartBeat transmitter thread(6)]: RemoteControl - Disconnected st :    at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at TvControl.RemoteControl.InvokeEvents()
   at TvControl.RemoteControl.RefreshRemotingConnectionStatus()
   at TvControl.RemoteControl.get_Instance()
   at TvControl.TvServer.<IsAnyCardRecording>b__4()
   at TvControl.WaitFor`1.Run(Func`1 function)
   at TvControl.TvServer.IsAnyCardRecording()
   at TvPlugin.TVHome.HeartBeatTransmitter()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

which is the issue but looks like this is client loosing contact with server and it does restart again

 

[elliottmc]

Something looks a little off with your tuners (possibly not related but can you confirm) logs show

2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 BDA ATSC/QAM Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 BDA ATSC/QAM Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 BDA ATSC/QAM Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 BDA ATSC/QAM Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 Analog TV Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 Analog TV Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 Analog TV Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: NOT preloading card :Hauppauge WinTV-7164 Analog TV Tuner
2010-07-11 19:55:48.325200 [TVService(5)]: Controller: preloading card :Hauppauge WinTV PVR PCI II TvTuner

so his has picked up 4 ATSC and 4 analog tuners (later on shows these as hybrid tuners) plus the PVR PC II

The logs also have config files for four analogue tuners on 7164 card and four analogue tuners on PVR PC II??

So x4mer, how many tuner cards do you have? If you do not have five cards (4 hybrid ATSC/analog and one PVR) then I think that your database is corrupt, and something has gone horribly wrong.

I'd say this is a good time to do a complete uninstall (including the TV database) and reinstall RC6 from scratch. Don't try to export anything from your database and then reimport!

Thanks.

Mark

 

[x4mer]

I have 2 HVR-2250 cards & one PVR-500, so 4 hybrid ATSC/NTSC (antenna - HDTV) & 2 NTSC only (cable - SD).

I tried testing channel preview in TVSetup, while the Hauppauge signal monitor was running. Channels which definitely had signal, were showing as no activity on the monitor. A reboot of the server did not correct the problem. I had to do a full power down to cut power to the tuners, then the signal monitor worked fine on next boot. Since then, the TV server hasn't crashed. I guess one of the 2250 cards was hung in a locked up state, while the other was working as some recordings did get done.

I've used the UNC paths for timeshifting/recording for a very long time, in order for comskip to work on multiseat. I realise you can now enter it in the client config in debug mode, but I just keep it the old way, with the client getting fed absolute UNC paths by the TV server DB.

I did have the prevent duplicate, with the 'by episode name' option enabled. I've found I've missed too many recordings, erroneously identified as repeats, and when I had this new problem I did away with the repeats detection. I believe the problem lies in the guide data from Schedules Direct being inconsistant in providing episode data.

Appears there was no bug here. Thanks for the responses guys.