New client causes other client on same network to freeze (1 Viewer)

[ben1210]

Upgraded a bedroom client machine (Asrock Q1900DC) and installed MP 1.9. Thing is when the new machine boots up MP or even when changing channel it causes another client to freeze. Its not a fatal freeze and is quickly rectified by a back and off and on on the TV that was frozen - but obviously annoying.

I've attached some logs taken just after a freeze.

Advice greatly appreciated?

 

[mm1352000]

Hello

For a start it looks like you're using non-matching versions of MP and TV Server. This may (...or may not) work. The choice to try such a configuration is at your own risk. We don't test such configurations or commit to preserve compatibility or provide support.

Further, it looks like these are the logs from the client that has been upgraded. To chase a problem like this we'd need the logs from the server and especially the client that froze. Also needed would be specific dates and times when freezes occur.

In other words, at this point I'm not able to help due to lack of information. If you provide the missing information then it might be possible to assist... but better would be to stick with a supported configuration. Quite frankly I don't really want to spend a lot of time investigating a cross-version compatibility issue, because the chances of getting it fixed would be zero.

Regards,
mm
PS: This is not meant to be a grumpy/stern post. Just trying to be realistic.

 

[ben1210]

no probs, I just now upgraded the server to 1.9 (very quick install) - lets see if it works

 

[ben1210]

Hi this freezing continues to happen on this particular client. I think the problem is associated with recordings starting. Other clients in the house are not affected.

Attached are the logs taken from both the client (MediaPortalLogs_02_12_14__16_26.zip) and server (log (2).zip) at the time of the crash 2/12/2014 at 16.25. TV was on Tiny Pop channel and the program on was My Little Pony.

Any help greatly appreciated

 

[mm1352000]

I think the problem is associated with recordings starting.

Based on the MediaPortal log I'd agree:
[2014-12-02 16:25:09,591] [Log ] [MPMain ] [INFO ] - send rec notify
[2014-12-02 16:25:09,592] [Log ] [MPMain ] [INFO ] - send rec notify done

TV is stopped shortly afterwards.

Please can you slim down the TV Server logs and repost?
I'm only on a 10GB cap so can't really afford to be downloading 15 MB sets of logs all the time.

 

[ben1210]

I think the problem is associated with recordings starting.

Based on the MediaPortal log I'd agree:
[2014-12-02 16:25:09,591] [Log ] [MPMain ] [INFO ] - send rec notify
[2014-12-02 16:25:09,592] [Log ] [MPMain ] [INFO ] - send rec notify done

TV is stopped shortly afterwards.

Please can you slim down the TV Server logs and repost?
I'm only on a 10GB cap so can't really afford to be downloading 15 MB sets of logs all the time.

Its a screenfreeze then I press back and switch off TV back on and all is fine. 9 out of 10 times recordings starting or finishing does not cause a screenfreeze. But it happens enough to post this thread methinks.

edit, thinking about it this client is the only client that has recording notification pop-ups enabled - could that be the reason?

 

[mm1352000]

Is F: a RAM drive?

 

[ben1210]

Nope. Its a 500gig regular HDD

 

[mm1352000]

Perfect.
So, based on this logging in the TsWriter log:
[2014-12-02 16:25:18,457] [69de980] [1094] - Recorderid 911 Continuity error... 8 ( prev 8 ) - bad signal?
[2014-12-02 16:25:18,457] [69de980] [1094] - Recorderid 90b Continuity error... 7 ( prev e ) - bad signal?
[2014-12-02 16:25:18,457] [69de980] [1094] - Recorderid 912 Continuity error... 1 ( prev c ) - bad signal?
[2014-12-02 16:25:18,473] [69de980] [1094] - Recorderid 90c Continuity error... 1 ( prev b ) - bad signal?
[2014-12-02 16:25:18,535] [69de980] [1094] - Recorder: TIMESHIFT Info : Program clock reference forward jump ( 903545 ).
[2014-12-02 16:25:18,551] [69de980] [1094] - Recorder: RECORD Info : Program clock reference forward jump ( 906047 ).

...I might suspect that starting the recording requires the D: drive to spin up, and during that spin up the F: drive is temporarily unavailable. This unavailability is enough to trigger the "freeze" on the client.

One way of checking if my theory is correct would be to - rather than stopping and restarting TV on the client - wait 10 seconds or so (enough time for the D: drive to spin up), then skip back 5, 10, 15, <whatever> seconds and see if the client freezes at the same point. My prediction would be that there would be no freeze, though there may be a short glitch. The next test would be to configure Windows' power management to prevent the timeshift drive from ever spinning down and see if the glitches go away. Otherwise, move the timeshift folder to the recording drive. That should also avoid the problem.

 

[ben1210]

OK - sounds plausible, I will report back.