TV-Server wake on LAN timeout value is not respected (1 Viewer)

megahorst

Super User
  • Team MediaPortal
  • Super User
  • July 8, 2006
    879
    259
    Home Country
    Germany Germany
    MediaPortal Version: 1.4.0

    Description
    While doing some testing to help @Sebastiii with his patch for mantis 4477 I have mentioned that the WOL-timeout value is not respected be the MePo client..
    The timeout feature is described here:
    http://wiki.team-mediaportal.com/1_...n/MediaPortal_Configuration/22_TV/1_TV_Client
    I have configured a timeout of 10 seconds.
    The logs show:
    In case of a MePo Start:
    Code:
    2013-06-20 21:35:49,685] [Log  ] [MPMain  ] [INFO ] - Main: MediaPortal v1.4.0.0 is starting up on Windows 7 ( Service Pack 1 ) [6.1.7601.65536]
    [2013-06-20 21:35:49,700] [Log  ] [MPMain  ] [INFO ] - Build: 1.4.0.0
    ...
    [2013-06-20 21:35:58,250] [Log  ] [MPMain  ] [DEBUG] - TVHome: WOL - Valid auto MAC address: 78:ac:c0:af:a4:a1
    [2013-06-20 21:35:58,250] [Log  ] [MPMain  ] [DEBUG] - TVHome: WOL - Store MAC address: 78:AC:C0:AF:A4:A1
    [2013-06-20 21:35:58,250] [Log  ] [MPMain  ] [DEBUG] - TVHome: WOL - Use stored MAC address: 78:AC:C0:AF:A4:A1
    [2013-06-20 21:35:58,266] [Log  ] [MPMain  ] [INFO ] - TVHome: WOL - Start the TV server
    ca. 8,5 sec.
    In case of MePo resuming from S3:
    Code:
    [2013-06-20 21:39:36,030] [Log  ] [MPMain  ] [DEBUG] - Main: WM_DEVICECHANGE (Event: DBT_DEVICEARRIVAL)
    ...
    [2013-06-20 21:39:36,982] [Log  ] [MPMain  ] [DEBUG] - TVHome: WOL - Use stored MAC address: 78:AC:C0:AF:A4:A1
    [2013-06-20 21:39:36,982] [Log  ] [MPMain  ] [INFO ] - TVHome: WOL - Start the TV server
    < 1 second.
    The resume case is the critical one. In many cases MePo tries to send the WOL before the networkinterface is up and running.

    This could be the reason for the problem that some users have described who are wanting the "restart on resume feature" back.

    Steps to Reproduce:
    1. Check the timeout value in the client configuration
    2. Start the client
    3. compare the timestamps in the mediaportal logfile

    4. send the client to standby
    5. resume it
    6. compare the timestamps in the mediaportal logfile again

    EDIT by Sebastiii : Area51 Thread : https://forum.team-mediaportal.com/...ice_detection_from_tvserver_in_tvhome.120159/:)
     

    Attachments

    • server_not_started.7z
      5 KB
    Last edited by a moderator:

    Django.edwards

    Portal Pro
    October 22, 2009
    457
    54
    Eupen
    Home Country
    Belgium Belgium
    Hi megahorst, I think that this timeout is the time between the Client sends the WOL and then waits for 10 sec. before he tries to connect to the Server. So this would be the amount of time the Server Needs to wakeup.
    I think that the Option "delay Startup for" in the General Settings is what you are looking for. http://wiki.team-mediaportal.com/1_...guration/11_General/5_Startup_Resume_Settings

    Here you can pause the Startup for say 10 sec on resume to be shure that the Network Interface is up, and then the wol will be send.

    I hope you understand what I mean.

    But for me, the Option "restart on resue" was very usefull. Because sometimes after waking up mepo was slow or you some other glitches. With the restart you could always be shure that you had a clean started up mepo. So I don't understand, why this Option was removed. I can't see any reason for this.
     
    Last edited:

    megahorst

    Super User
  • Team MediaPortal
  • Super User
  • July 8, 2006
    879
    259
    Home Country
    Germany Germany
    I hope you understand what I mean.
    Yes ;-)


    I think that this timeout is the time between the Client sends the WOL and then waits for 10 sec.
    Perhaps you are right. But the log shows that the client does also not wait 10 serconds to mention that the server has not started, what it should do if you are right.
    Code:
    [2013-06-20 19:29:59,345] [Log	] [MPMain  ] [INFO ] - TVHome: WOL - Start the TV server
    [2013-06-20 19:29:59,345] [Log	] [MPMain  ] [DEBUG] - WOLMgr: Increasing timeout for RemoteControl
    [2013-06-20 19:29:59,345] [Log	] [MPMain  ] [DEBUG] - WOLMgr: Ping TV-Horst
    [2013-06-20 19:29:59,376] [Error  ] [MPMain  ] [ERROR] - WOLMgr: Ping failed - Während einer Pinganforderung ist eine Ausnahme aufgetreten.
    [2013-06-20 19:29:59,377] [Log	] [MPMain  ] [DEBUG] - WOLMgr: Ping TV-Horst
    [2013-06-20 19:29:59,454] [Error  ] [MPMain  ] [ERROR] - WOLMgr: Ping failed - Während einer Pinganforderung ist eine Ausnahme aufgetreten.
    [2013-06-20 19:29:59,455] [Log	] [MPMain  ] [DEBUG] - WOLMgr: System TV-Horst still not reachable, waiting...
    [2013-06-20 19:30:00,464] [Log	] [MPMain  ] [DEBUG] - WOLMgr: Ping TV-Horst
    [2013-06-20 19:30:00,474] [Error  ] [MPMain  ] [ERROR] - WOLMgr: Ping failed - Während einer Pinganforderung ist eine Ausnahme aufgetreten.
    [2013-06-20 19:30:00,474] [Log	] [MPMain  ] [DEBUG] - WOLMgr: System TV-Horst still not reachable, waiting...
    [2013-06-20 19:30:01,476] [Log	] [MPMain  ] [DEBUG] - WOLMgr: Ping TV-Horst
    [2013-06-20 19:30:01,786] [Error  ] [MPMain  ] [ERROR] - WOLMgr: Ping failed - Während einer Pinganforderung ist eine Ausnahme aufgetreten.
    [2013-06-20 19:30:01,786] [Log	] [MPMain  ] [DEBUG] - WOLMgr: System TV-Horst still not reachable, waiting...
    [2013-06-20 19:30:02,792] [Log	] [MPMain  ] [DEBUG] - WOLMgr: Ping TV-Horst
    [2013-06-20 19:30:03,102] [Error  ] [MPMain  ] [ERROR] - WOLMgr: Ping failed - Während einer Pinganforderung ist eine Ausnahme aufgetreten.
    [2013-06-20 19:30:03,102] [Log	] [MPMain  ] [DEBUG] - WOLMgr: System TV-Horst still not reachable, waiting...
    [2013-06-20 19:30:04,104] [Log	] [MPMain  ] [DEBUG] - WOLMgr: Ping TV-Horst
    [2013-06-20 19:30:06,660] [Error  ] [MPMain  ] [ERROR] - WOLMgr: Ping failed - Während einer Pinganforderung ist eine Ausnahme aufgetreten.
    [2013-06-20 19:30:06,660] [Log	] [MPMain  ] [DEBUG] - WOLMgr: System TV-Horst still not reachable, waiting...
    [2013-06-20 19:30:07,660] [Error  ] [MPMain  ] [ERROR] - TVHome: WOL - Failed to start the TV server
    [2013-06-20 19:30:07,660] [Log	] [MPMain  ] [DEBUG] - TVHome: HeartBeat Transmitter started.
    [2013-06-20 19:30:07,660] [Log	] [MPMain  ] [INFO ] - TvNotify: start
     

    megahorst

    Super User
  • Team MediaPortal
  • Super User
  • July 8, 2006
    879
    259
    Home Country
    Germany Germany
    Nobody else?

    Can anybody explain how all these timers should work together?
    Should they run one after another or in parallel or ...?
    I will do some more tests, but I first I need to know, what behaviour is the designed one ...

    Thx
     

    Sebastiii

    Development Group
  • Team MediaPortal
  • November 12, 2007
    16,583
    10,403
    France
    Home Country
    France France
    Hi,

    Didn't take the time to look, will try asap :)
     

    Sebastiii

    Development Group
  • Team MediaPortal
  • November 12, 2007
    16,583
    10,403
    France
    Home Country
    France France
    There is a bin for testing :
    I have the feeling that i'm spamming lol
     
    Last edited:

    megahorst

    Super User
  • Team MediaPortal
  • Super User
  • July 8, 2006
    879
    259
    Home Country
    Germany Germany
    Sebastiii provided 2 versions of a fix to me.
    One of the versions is also located in this thread. For me it works better as before. But you can also give it a try ...
     

    richardc1983

    Portal Pro
    October 10, 2012
    251
    24
    Leeds
    Home Country
    United Kingdom United Kingdom
    Does it avoid the freeze up on resume and black screens. Usually takes 3/4 mins before mp responds or shows anything.
     

    Users who are viewing this thread

    Top Bottom