Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#11160 closed Bug Report - General (Upstream Bug)

Mythbackend needs to wait for network before starting on fast-booting systems.

Reported by: John <da_audiophile@…> Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.26
Severity: medium Keywords:
Cc: Ticket locked: yes

Description

Since the 0.26 update, mythbackend is much more picky about requiring a network interface to be up before it starts. I believe that main protocol server in mythbackend terminates, taking the backend with it, when it does not have access to the IP addresses it on which it was told to listen. I have an SSD-based backend that boots pretty quickly. The problem is that my network isn't ready when mythbackend starts which causes the backend to detect no network and shutdown.

I can fix this by starting the backend manually several seconds after the box boots via a simple script that is triggered when X comes up. I know that this is not a robust and general solution. Perhaps there is a way to make the backend more robust and tolerant to this somehow? Maybe add a retry loop or the like?

Here is a snipette from my backend log if I do NOT use the script which clearly shows the issue:

...
2012-10-07 15:07:52.606487 C ServerPool: Host is configured to listen on 192.168.0.102, but address is not used on any local network interfaces.
2012-10-07 15:07:52.606648 I Listening on TCP 127.0.0.1:6544
2012-10-07 15:07:52.606712 I Listening on TCP [::1]:6544
2012-10-07 15:07:52.641782 I Added logging to mythlogserver at TCP:35327
2012-10-07 15:07:53.806462 E Bonjour: Error: -65537
2012-10-07 15:07:53.806474 E Bonjour: Failed to register service.
2012-10-07 15:07:53.806485 I Main::Registering HttpStatus Extension
2012-10-07 15:07:53.811393 C Backend exiting, MainServer
...

Change History (3)

comment:1 Changed 6 years ago by Raymond Wagner

Priority: majorminor
Resolution: Upstream Bug
Severity: highmedium
Status: newclosed

If mythbackend is started before your network is available for use, then your init scripts or init system are broken, and the problem lies with your packager. If you do not require remote access that would need the network to be up when mythbackend is started, simply tell MythTV to listen on the localhost addresses only.

comment:2 Changed 6 years ago by dm@…

I have wasted a lot of time on this issue, in my opinion, it would be much better if mythbackend started regardless of the network status.For a stand alone backend / frontend setup, there is no guarantee that it will have a network connection. It could be an option in mythtv setup, ie: a checkbox that says "do not start backend without networking".

comment:3 Changed 6 years ago by stuartm

Ticket locked: set
Note: See TracTickets for help on using tickets.