mythbuntu-bugs team mailing list archive

[Mario Limonciello <superm1@xxxxxxxxxx>]

The problem with waiting on mysql is that this breaks on systems that don't
need mysql installed (slave backends).

On Sat, Jul 24, 2010 at 01:37, a7x <609402@xxxxxxxxxxxxxxxxxx> wrote:

> I should note that I'm running 0.23.0+fixes25396.
>
> --
> mythtv-backend upstart config should wait for mysql
> https://bugs.launchpad.net/bugs/609402
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to Mythbuntu.
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New
>
> Bug description:
> mythtv-backend requires mysql, so it should not start until mysql has
> started and it should stop when mysql is stopping.
>
> Due to bug #608423 mysql fails to start on my machine.  Because of the
> 'respawn' directive in /etc/init/mythtv-backend.conf, my /var/log/syslog was
> quickly filled with the following:
>
> ...
> Jul 23 19:18:01 myth init: mythtv-backend main process (26729) terminated
> with status 254
> Jul 23 19:18:01 myth init: mythtv-backend main process ended, respawning
> Jul 23 19:18:04 myth init: mythtv-backend main process (26735) terminated
> with status 254
> Jul 23 19:18:04 myth init: mythtv-backend main process ended, respawning
> Jul 23 19:18:08 myth init: mythtv-backend main process (26741) terminated
> with status 254
> Jul 23 19:18:08 myth init: mythtv-backend main process ended, respawning
> ...
>
> and my /var/log/mythtv/mythbackend.log was filled with "Can't connect to
> MySQL server on 'myth' (111)" errors.
>
> The attached patch modifies the upstart config file to wait until mysql
> starts before starting mythtv-backend and stop mythtv-backend when mysql is
> stopping.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mythbuntu-bugs
> Post to     : mythbuntu-bugs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mythbuntu-bugs
> More help   : https://help.launchpad.net/ListHelp
>



-- 
Mario Limonciello
superm1@xxxxxxxxx