Page 1 of 1
Backend connection retry system on boot
Posted: Wed Jan 07, 2009 11:10 am
I notice that when Minimyth doesn't find the backend server during the boot process, it hangs in there and it doesn't periodically retry the connection, so there's no any other solution than rebooting the frontend client when the backend server is ready. Is there any other way for the frontend to keep retrying the connection to the backend server during the boot?
EDIT: Since this topic is about booting, can someone please move this to the Booting section of the forum?
Posted: Wed Jan 07, 2009 5:53 pm
Some additional information would be helpful in troubleshooting.
When does this happen?
Why is the backend not ready?
If you are using WOL to wake the backend, then have you configured the MM_MASTER_WOL* parameters?
Posted: Thu Jan 08, 2009 5:02 pm
During my tests, sometimes I forget to start the backend server and the frontend stops in the MythTV backend connection step. Then I start the backend server but I need to reboot the frontend since it seems that it doesn't apply any retry system in order to check if the backend is already available.
I don't know if WOL can solve this problem...
Posted: Fri Jan 09, 2009 3:42 am
I doubt that the WOL settings will solve the problem. MiniMyth assumes that the MythTV master backend is running (at least after WOL). As MiniMyth accesses the MythTV master backend database during its boot process, changing this assumption would be difficult.
Posted: Fri Jan 09, 2009 10:20 am
I wonder if a periodic connection retry system wouldn't be possible to implement...
Posted: Wed Mar 04, 2009 11:20 pm
Pablo wrote:I doubt that the WOL settings will solve the problem. MiniMyth
assumes that the MythTV master backend is running (at least
after WOL). As MiniMyth accesses the MythTV master backend
database during its boot process, changing this assumption
would be difficult.
I haven't looked at the code yet, but one would think that
putting the "connect" operation in a loop with a 5-10 second
delay wouldn't be too tough.
How does one handle the case when after a power failure (and
resumption)the frontend boots up before the backend? I guess
since one doesn't use a frontend unattended, it doesn't really
matter -- you can wait until the backend is up and hit the
"reset" button on the frontend.
I'm curious: do people usually power off their MiniMyth
frontends while not in use, or do people usually leave them on?