Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#4276 closed defect (fixed)

MythWelcome Does Not Retry Connecting To MythBackend

Reported by: anonymous Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: mythtv Version: unknown
Severity: medium Keywords: mythwelcome
Cc: Ticket locked: no


If you load MythWelcome? before the Backend has completely finished loading it causes MythWelcome? to display a "Could Not Connect To The Master Backend Service - Is It Running" message.

This is confusing as the user has already loaded the backend it just has not finished starting up so mythwelcome can detect it. After MythWelcome? has displayed the "could not connect error message" it then displays "Retrieving Scheduled Recordings, Retrieving Recording Status" on the screen giving the impression it is attempting to retrieve the values but it never does.

Reproduce by loading Mythwelcome without the Mythbackend running. Alternatively run mythbackend on a slower machine (e.g. mine take 15 sec to start) and before it has fully started run mythwelcome.

Suggest if mythwelcome can not connect to backend immediately attempt to reconnect to the backend a few times at regular intervals for 30 seconds or so and only display a permanent could not connect to backend after this time.

This will also fix the rather imprecise hack of having to use the sleep 15 command if you want to boot and start with mythwelcome.

Using 0.20.2+fixes via Mythbuntu

Change History (3)

comment:1 Changed 13 years ago by bullestock@…

This problem only occurs if the setting WOLbackendReconnectWaitTime is zero.

So the solution is simple: Set WOLbackendReconnectWaitTime ("Delay between wake attempts") to a nonzero value, and optionally set WOLbackendConnectRetry ("Number of times the frontend will try to wake up the master backend") to the number of retries you need.

comment:2 Changed 13 years ago by paulh

Resolution: fixed
Status: newclosed

(In [15354]) Make MythWelcome? a little quicker to re-connect to the master BE if it looses the connection or if the BE is not available when it starts up.

I think it would always eventually reconnect it was just the UI was sometimes taking a while to be updated to reflect that.

Fixes #4276.

comment:3 Changed 13 years ago by anonymous

Thanks this seems to have sorted the problem for me.

Note: See TracTickets for help on using tickets.