myth-backend wants to start in runlevel2 while mysql is not ready yet
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-dfsg-5.0 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
mythtv (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I have the problem that mythtv-backend wants to connect to mysql in runlevel 2 (jaunty standard) although mysql is not yet ready.
This causes myth-backend to start, but not reach the complete DB, while mysql starts perfectly without any errors.
The result in my case is, that mythtv's recording schedule cant be seen by mythtv-backend.
Restarting /etc/init.
I used sysv-rc-conf to remove the entries for mythtv-backend in runlevel2 (don't know what they're for anyway).
Now mysql has the time to start up before myth starts.
This can only be a workaround though i think...
Description: Ubuntu 9.04
Release: 9.04
mythtv-backend:
Installiert: 0.21.0+
Kandidat: 0.21.0+
Versions-Tabelle:
*** 0.21.0+
500 http://
100 /var/lib/
0.
500 http://
Which version of mysql are you running? This is probably a bug in the mysql init script.
Given, S20mysql S20mythtv-backend, the mythbackend script is 2nd (alphanumerically) and should be able to depend on all previous services being up and running. S20mysql should not exit 0 until mysql is actually available.
:-Dustin