mythtv fails to connect to remote DB on inital boot

Is this on a machine with network manager in use? If so, try to setup DHCP via the manual network configuration utility instead of using network manager.

Yes, this machine use to use the NetworkManager.

Then I needed this machine to have a static IP so I set that in the
"/etc/network/interfaces" file. After that it has been working fine.

I apologize for not updating the bug report.

On 10/29/07, Mario Limonciello <email address hidden> wrote:
> Is this on a machine with network manager in use? If so, try to setup
> DHCP via the manual network configuration utility instead of using
> network manager.
>
> ** Changed in: mythtv (Ubuntu)
> Status: New => Incomplete
>
> --
> mythtv fails to connect to remote DB on inital boot
> https://bugs.launchpad.net/bugs/149268
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Not sure how much time wants to be spent on this. Since a master backend with the database on a different machine isn't supported out of the box however it still needs fixing.

There might be a way to fix this.

NetworkManager seems to be able to run commands whenever it fiddles with interfaces. It looks like it's emulating the old ifup/ifdown behavior (see /etc/NetworkManager/dispatcher.d/01ifupdown).

We might be able to restart mythbackend whenever an interface is taken online. However, this can result in the backend being restart in the middle of a recording/transcoding job/commflagging job. (Just wondering: what happens if the master backend goes away when the slave is recording something?).

Another approach would require us to write a small script which would check (when the backend is started via its init script) if a slave backend is meant to connect to an external backend and make sure it's reachable, eg that a route to that network exists or something as simple as a ping. if it's unreachable, make Networkmanager restart the backend once a interface comes up.

Too complicated to be a nice and simple solution, though. :( Any thoughts? Of course, this should be configurable (disabled by default?).

I've got a fix in that may be able to take care of this in mythtv bzr.

mythtv (0.20.2+fixes15096-0ubuntu2) hardy; urgency=low

  [ Mario Limonciello ]
  * mythtv-backend.init:
    - Require networking and remote file systems to be started before
      running. (LP: #149268)
    - Find the home directory of our USER and then create a symbolic
      link in that user's home directory for mysql.txt.
    - Add LSB support.

  [ Paul McEnery ]
  * More resilient init script PID handling (LP: #118538)

 -- Mario Limonciello <email address hidden> Mon, 17 Dec 2007 00:15:52 -0600

My fix for this was as follows;

1. Move the init for mythbackend from 20 to 50.
2. Change the network configuration.

Details;
1. Move the init for mythbackend from 20 to 50.

Type:
sudo update-rc.d -f mythtv-backend remove

Echo:
Removing any system startup links for /etc/init.d/mythtv-backend ...
   /etc/rc0.d/K20mythtv-backend
   /etc/rc1.d/K20mythtv-backend
   /etc/rc2.d/S20mythtv-backend
   /etc/rc3.d/S20mythtv-backend
   /etc/rc4.d/S20mythtv-backend
   /etc/rc5.d/S20mythtv-backend
   /etc/rc6.d/K20mythtv-backend

Type:
sudo update-rc.d mythtv-backend defaults 50

Echo:
Adding system startup for /etc/init.d/mythtv-backend ...
   /etc/rc0.d/K50mythtv-backend -> ../init.d/mythtv-backend
   /etc/rc1.d/K50mythtv-backend -> ../init.d/mythtv-backend
   /etc/rc6.d/K50mythtv-backend -> ../init.d/mythtv-backend
   /etc/rc2.d/S50mythtv-backend -> ../init.d/mythtv-backend
   /etc/rc3.d/S50mythtv-backend -> ../init.d/mythtv-backend
   /etc/rc4.d/S50mythtv-backend -> ../init.d/mythtv-backend
   /etc/rc5.d/S50mythtv-backend -> ../init.d/mythtv-backend

2. Change the network configuration.
On the desktop select;
Applications > System > Network

Type your sudo password if prompted.

Select your wired connection on the "Connections" tab.

Select "Properties"

Uncheck "Enable Roaming Profile"

Change the configuration to DHCP or Static.

Note: If you do use DHCP I highly recommend a static DHCP assignment in your router or you may have problems in the future.

Reboot.....

And for me the problem is fixed.

Fixed in Mythbuntu 8.04 Alpha 1