Why do I have to manually keep starting mysql and mythbackend??

English Applications
1

As the title states.

# /etc/init.d/mysql status
Checking for service MySQL:                                                                                                       unused
 # /etc/init.d/mythbackend status
Checking for service MythTV backend                                                                                               unused

http://img100.imageshack.us/img100/5274/snapshot4.jpg

2

Did you set mysql to start at boot in YaST? Ditto for mythbackend.

3

i thought that was what “System Services runlevel” was

4

Sorry, didn’t see the screenshot first time. I block images.

So you’re saying it keeps dying? You’d have to work out why then.

Or are you saying you have to start it up manually after boot and then it stays up?

5

yep.567890

6

Do this:

/sbin/chkconfig --list mysql

My result:

mysql                     0:off  1:off  2:on   3:on   4:off  5:on   6:off
7 
# /sbin/chkconfig --list mysql
mysql                     0:off  1:off  2:on   3:on   4:off  5:on   6:off
8

Sorry, I’m stumped. Only thing I can think if is it has some issues starting at boot. You’ll have to watch the process for any errors. Or maybe look in /var/log/boot.msg.

9

ken yap wrote:
> Sorry, I’m stumped. Only thing I can think if is it has some issues
> starting at boot. You’ll have to watch the process for any errors. Or
> maybe look in /var/log/boot.msg.

At the top of the rcscript, is a section with init info. See if there
are some required start entries that aren’t present/enabled. May be
that mysql is trying to start too early in the game.

Here at work my box is running Debian, but the relevant section for
mysql is:
#!/bin/bash

BEGIN INIT INFO

Provides: mysql

Required-Start: $remote_fs $syslog mysql-ndb

Required-Stop: $remote_fs $syslog mysql-ndb

Should-Start: $network $named $time

Should-Stop: $network $named $time

Default-Start: 2 3 4 5

Default-Stop: 0 1 6

Short-Description: Start and stop the mysql database server daemon

Description: Controls the main MySQL database server daemon “mysqld”

and its wrapper script “mysqld_safe”.

END INIT INFO

I’d expect something similar in the SUSE scripts.

–
Kevin Miller
Juneau, Alaska
http://www.alaska.net/~atftb
In a recent poll, seven out of ten hard drives preferred Linux.

10

well, mine is

### BEGIN INIT INFO   
# Provides:       mysql
# Required-Start: $network $remote_fs
# Required-Stop: $network $remote_fs
# Default-Start:  2 3 5
# Default-Stop:
# Description:    Start the MySQL database server
### END INIT INFO

Ah, ok. So it has to do with mysql starting before I get the binded LAN address.

So I just make mysql start after the network, or how do I bring the network to the front (because it seems the case for mythtv as well)

11

$network means networking is up, not that you have a eth address. At that point at least lo should be up with a localhost address even if you get a eth address later with network manager or something like that. Mysql works fine on hosts with no eth inteface at all, and connection is to localhost. Do you not have lo up at that point?

Are you just guessing from looking at the header or did you actually monitor the bootup to see what the problem is? You may have to insert some debugging in the start script or turn on some debugging in mysql.

12

From googling. And also that mythtv and mysql are both set to bind to 10.0.0.3, not localhost

13

But did you stop mysql from also binding to a Unix socket and also 127.0.0.1? Normally you don’t need to change the listening address in /etc/my.cnf because it will listen on all interfaces. If you did change it to listen on only 10.0.0.3 then it would fail if the interface is not up. If you had left it alone, it would bind to *:3306 and when 10.0.0.3 comes it it would be available. Looks like you were too clever by half.