[confirm] tvservice dying very often (1 Viewer)

[porky996t]

Just to confirm that I am still having random crashes with the TV service.

Sometimes MP will just freeze or others it won't timeshift. As much as I have tried to replicate it, I can't. I just have to reboot and start again. The TV Server still records etc when MP freezes up.

Next time it happens I'll post the logs up.

 

[DiePlage]

TVService on WLAN

Since RC1 TVService is crashing frequently. From TVService configuration I can tell that the server is labeled with it's IP rather than hostname (which is how it used to be in prior versions IIRC). I also notice my WLAN-NIC loosing connection / reconnecting every once in a while. To find out whether both events are related, I would like to make the TVService listen on 127.0.0.1 rather than on the WLAN NIC's IP-address.
I'm running a single-seat environment so this should work.

Can anyone tell me how to configure on which interface TVService listens?

Cheers, DiePlage

 

[morpheus_xx]

AW: Re: tvservice dying very often

I added the fix mentioned above to svn: 0002776: Code locking in cardtuner can cause hangs - MediaPortal Bugtracker --> This is only the removal of "lock(this)" call in cardtuner.cs.

Any news on this ??
Happened again this morning....

***UPDATE***

Did some testing with this in order to replicate.. could not do so.

See, it occured to me that the problem mostly happens first thing in the morning when waking up the server from suspend mode.
Anyway, in an attempt to find out, i put my server into suspend manually and then woke it up manually.
However, i can sit there and do this for hours on end ( suspend -> wakeup -> suspend -> wakeup... etc ) and the TVService never crashes.

Problems lies elsewhere....

Hope this info helps...

Cheers

--> this time your system hangs in another place, when the graph is about to start. I currently have no other idea than to try other drivers

 

[DiePlage]

Re: TVService on WLAN

Since RC1 TVService is crashing frequently. From TVService configuration I can tell that the server is labeled with it's IP rather than hostname (which is how it used to be in prior versions IIRC). I also notice my WLAN-NIC loosing connection / reconnecting every once in a while. To find out whether both events are related, I would like to make the TVService listen on 127.0.0.1 rather than on the WLAN NIC's IP-address.
I'm running a single-seat environment so this should work.

Can anyone tell me how to configure on which interface TVService listens?

Cheers, DiePlage

I am sure I did change this once before. I had to manually edit some configuration file... I would really like to know whether at least some of my problems are related to WLAN

 

[Kaoh]

I tried this version to see if it fixes my: https://forum.team-mediaportal.com/mediaportal-1-1-0-rc-1-496/recording-failing-some-channels-80248/ problem and it does change the behaviour in such a manor that the second recording is not tried anymore. Using a the client to tune to a second channel now gives me a unknown error on the client.
In the other thread I added logs that show many excpetion while attempting to tune the second tuner,

 

[Nickske00]

I'm currently having this issue. I'm already on svn 25446

The tv service just stops randomly, sometimes when I'm watching live tv, or like today, when I'm not home and there was a recording scheduled. I've got logs from today. Tomorrow I'll clean up everything with your log tool and let mediaportal run when I'm at work and I'll upload new logs when I get home.

EDIT: I found the cause of my problem. I'm using mediaportal with satellite, now there is one channel I found that just crashes the tvservice... I now disabled epg grabbing for this channel (was enabled with dvb epg), and today the tv service didn't die

 

[crawdaddy]

Re: AW: tvservice dying very often

Hi morpheus, I have an issue, that is related to the title (that's how I found this thread), but different cause than discussed so far:
When the recording folder/volume has no space left, tvservice crashes too - see attached error.log.
Wouldn't it be better, if tvservice could stop recording and still service live tv ?

I think I am getting very similar TV Server crashes when the hard drive where recordings go runs out of space. I am going to post some logs up here ASAP showing when it happens. I'm also trying to get a bigger hard drive, the one newegg sent me was DOA.

 

[Kaoh]

I did not suffer from tv service crashes anymore with rc2.
Maybe your old disk is faulty, try running a disk scan to see if the disk has write problems.

 

[bounguine]

My TVServer crashes almost every time after resuming from standby.
I hadn't been suffering from it until I upgraded to 1.1.0*.

On resuming nnCron kills MP, stops TVServer, restarts SS2 driver and then starts TVServer and MP again.
When started, MP always shows a message “Connection to TVServer lost”.

In my single seat setup I use MS loopback adaptor with a given static IP 192.168.1.7 (actual PC’s IP is 192.168.1.67).
Both MP and TVServer are configured to use 192.168.1.7.

Here’s a time-line from different logs with used IPs:

[0506cron.log] 07:36:42 4080 Start: C:\Program Files\Team MediaPortal\MediaPortal TV Server\Tvservice\psservice.exe stop TvService
[0506cron.log] 07:36:45 4080 Start: C:\Program Files\Team MediaPortal\MediaPortal TV Server\Tvservice\SS2.bat
[0506cron.log] 07:37:31 4080 Start: C:\Program Files\Team MediaPortal\MediaPortal TV Server\Tvservice\psservice.exe start TvService
[TV.log] 2010-05-06 07:37:32.156250 - TV service: Starting
[TV.log] 2010-05-06 07:37:40.093750 - TV service: Started
[TV_error.log] 2010-05-06 07:39:09.640625 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:39:09.656250 - TVServer Initialization Error
[TV_error.log] 2010-05-06 07:39:11.640625 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:39:11.640625 - TVClient Initialization Error (192.168.1.67:31456)
[TV_error.log] 2010-05-06 07:39:13.640625 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:39:14.671875 - Remote control:master server :192.168.1.7
[MediaPortal.log] 2010-05-06 07:39:14.687500 - TVHome: IsSingleSeat - RemoteControl.HostName = 192.168.1.7 / Dns.GetHostEntry(Environment.MachineName) = 192.168.1.7
[MediaPortal.log] 2010-05-06 07:39:14.765625 - get channels from database
[MediaPortal.log] 2010-05-06 07:39:15.656250 - TVHome: OnRemotingConnected, recovered from a disconnection
[TV_error.log] 2010-05-06 07:39:15.656250 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:39:15.812500 - found:2508 tv channels
[TV_error.log] 2010-05-06 07:39:17.765625 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:39:20.828125 - TVHome: Error (192.168.1.7:31456)
[TV_error.log] 2010-05-06 07:39:42.015625 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:39:44.015625 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:39:46.031250 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:39:48.046875 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:39:50.062500 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:40:19.531250 - Exception ystem.Net.WebException (127.0.0.1:31457)
[TV_error.log] 2010-05-06 07:40:42.062500 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:40:44.171875 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:40:46.187500 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:40:46.484375 - Exception ystem.Net.WebException (127.0.0.1:31457)
[TV_error.log] 2010-05-06 07:40:48.203125 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:40:50.203125 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:41:15.562500 - Exception ystem.Net.WebException (127.0.0.1:31457)
[TV_error.log] 2010-05-06 07:41:42.015625 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:41:44.015625 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:41:44.531250 - Exception ystem.Net.WebException (127.0.0.1:31457)
[TV_error.log] 2010-05-06 07:41:46.031250 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:41:48.046875 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:41:50.062500 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:42:13.500000 - Exception ystem.Net.WebException (127.0.0.1:31457)
[TV_error.log] 2010-05-06 07:42:42.062500 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:42:42.062500 - Exception (192.168.1.7:31456)
[MediaPortal.log] 2010-05-06 07:42:42.468750 - Exception ystem.Net.WebException (127.0.0.1:31457)
[TV_error.log] 2010-05-06 07:42:44.078125 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:42:46.078125 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:42:48.093750 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:42:50.109375 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:43:11.437500 - Exception ystem.Net.WebException (127.0.0.1:31457)
[MediaPortal.log] 2010-05-06 07:43:40.500000 - Exception ystem.Net.WebException (127.0.0.1:31457)
[TV_error.log] 2010-05-06 07:43:42.015625 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:43:44.015625 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:43:45.937500 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[MediaPortal.log] 2010-05-06 07:44:09.468750 - Exception ystem.Net.WebException (127.0.0.1:31457)
[TV_error.log] 2010-05-06 07:43:48.046875 - EpgGrabbing: unable to connect to controller at: 192.168.1.7
[TV_error.log] 2010-05-06 07:43:50.046875 - EpgGrabbing: unable to connect to controller at: 192.168.1.7

In this case I simply restarted my PC to solve the problem.
Next time I had the same problem, I decided to have an experiment:
1. I sent MP to tray.
2. TVService was working in Services window.
3. I clicked on the TVServer console icon and the console opened without any message, like “TVServer is not started. Do you like to open it?”
4. I opened MP GUI without restarting MP and saw no channels in it.

 

[arion_p]

@bounguine:
What subnet mask do you have on your physical adapter and MS loopback adapter?
If it is 255.255.255.0 then your network is misconfigured. You have two adapters on the same logical network that are not physically connected. What essentially happens is packets to 192.168.1.7 may be routed through the physical adapter at 192.168.1.67 and of course never reach the loopback adapter.