mysql has to autostart later

[midnightflash]

Binary package hint: mysql-server

The original startups for mysql in /etc/rc2.d/ are:
S17mysql-ndb-mgm
S18mysql-ndb
S19mysql

This is to early to come up for mysql. It just jails to start.
Changing them to:
S26mysql-ndb-mgm
S27mysql-ndb
S28mysql

Is working correctly though.

(btw. it seems my system is a bit fast while reading because if raid-5 with 4 hdds)

[Mathias Gug (mathiaz)]

On Fri, Dec 12, 2008 at 01:34:23PM -0000, midnightflash wrote:
> The original startups for mysql in /etc/rc2.d/ are:
> S17mysql-ndb-mgm
> S18mysql-ndb
> S19mysql
>
> This is to early to come up for mysql.

Why?

> It just jails to start.

How does it fail? Could you post some log files?

> Changing them to:
> S26mysql-ndb-mgm
> S27mysql-ndb
> S28mysql
>

  status incomplete

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

[midnightflash (midnightflash)]

Which logfiles do you mean?

# dmesg | grep mysql
[ 20.963888] type=1505 audit(1229199679.263:6): operation="profile_load" name="/usr/sbin/mysqld" name2="default" pid=4765

# ls -alh /var/log/mysql*
-rw-r----- 1 mysql adm 0 2008-12-04 06:30 /var/log/mysql.err
-rw-r----- 1 mysql adm 0 2008-12-13 10:43 /var/log/mysql.log
-rw-r----- 1 mysql adm 20 2008-12-12 08:19 /var/log/mysql.log.1.gz
-rw-r----- 1 mysql adm 20 2008-12-11 07:53 /var/log/mysql.log.2.gz
-rw-r----- 1 mysql adm 20 2008-12-10 08:01 /var/log/mysql.log.3.gz
-rw-r----- 1 mysql adm 20 2008-12-09 11:28 /var/log/mysql.log.4.gz
-rw-r----- 1 mysql adm 20 2008-12-08 09:44 /var/log/mysql.log.5.gz
-rw-r----- 1 mysql adm 20 2008-12-07 13:10 /var/log/mysql.log.6.gz
-rw-r----- 1 mysql adm 20 2008-12-06 07:35 /var/log/mysql.log.7.gz

This is all worth nothing. Zero to twenty byte...

--------------

# tail -n 1000 /var/log/messages | grep mysql
Dec 13 09:42:30 wallace kernel: [ 21.633705] type=1505 audit(1229157747.320:6): operation="profile_load" name="/usr/sbin/mysqld" name2="default" pid=4770
Dec 13 21:21:22 wallace kernel: [ 20.963888] type=1505 audit(1229199679.263:6): operation="profile_load" name="/usr/sbin/mysqld" name2="default" pid=4765

The first one was comming up (this morning with my altered startup sequence) an the second is not coming up (5 Minutes ago with the original startups).

It fails just as saying [fail] while the bootup-prompts. That's all (I see).

Would like to help some more... just tell me how please.

Greetings

[Mathias Gug (mathiaz)]

On Sat, Dec 13, 2008 at 08:38:41PM -0000, midnightflash wrote:
> Which logfiles do you mean?

Could you have a look into /var/log/daemon.log?

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

[midnightflash (midnightflash)]

For comparison the successful startup with the higher S-numbers:
 Dec 13 09:42:38 wallace mysqld_safe[6588]: started
Dec 13 09:42:38 wallace mysqld[6591]: 081213 9:42:38 InnoDB: Started; log sequence number 0 43655
Dec 13 09:42:39 wallace mysqld[6591]: 081213 9:42:39 [Note] /usr/sbin/mysqld: ready for connections.
Dec 13 09:42:39 wallace mysqld[6591]: Version: '5.0.67-0ubuntu6' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Dec 13 09:42:39 wallace /etc/mysql/debian-start[6630]: Upgrading MySQL tables if necessary.
Dec 13 09:42:39 wallace /etc/mysql/debian-start[6635]: Looking for 'mysql' in: /usr/bin/mysql
Dec 13 09:42:39 wallace /etc/mysql/debian-start[6635]: Looking for 'mysqlcheck' in: /usr/bin/mysqlcheck
Dec 13 09:42:39 wallace /etc/mysql/debian-start[6635]: This installation of MySQL is already upgraded to 5.0.67, use --force if you still need to run mysql_upgrade
Dec 13 09:42:39 wallace /etc/mysql/debian-start[6667]: Checking for insecure root accounts.
Dec 13 09:42:39 wallace /etc/mysql/debian-start[6671]: Triggering myisam-recover for all MyISAM tables

The entry with the faulty init start for mysql:

Dec 13 21:21:37 wallace /etc/init.d/mysql[5869]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Dec 13 21:21:37 wallace /etc/init.d/mysql[5869]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Dec 13 21:21:37 wallace /etc/init.d/mysql[5869]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Dec 13 21:21:37 wallace /etc/init.d/mysql[5869]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Dec 13 21:21:37 wallace /etc/init.d/mysql[5869]:

Seems to me as if the networking is not ready at that "early" time.

[Mathias Gug (mathiaz)]

Networking should already be up by then. Could you post your mysql configuration files as well as your networking configuration?

[midnightflash (midnightflash)]

/etc/my.cnf

[midnightflash (midnightflash)]

The above is /etc/mysql/my.conf
Now: /etc/mysql/mysqlaccess.conf

[midnightflash (midnightflash)]

Those two above are totally wrong... from a totally other system running on the same box... sorry!
Need more coffee by the way... ;-)

Now the real ones...

[midnightflash (midnightflash)]

etc/mysql/debian-start

[midnightflash (midnightflash)]

/etc/mysql/debian.cnf is the generic "do not touch" one.
and
/etc/mysql/conf.d/old_passwords.cnf :
# created by debconf
[mysqld]
old_passwords = false

In
/etc/network/interfaces
all is commented out -> DHCP -> Networkmanager
And the other files/folders are generic too. Nothing special at all.

[Mathias Gug (mathiaz)]

On Tue, Mar 31, 2009 at 10:16:51AM -0000, midnightflash wrote:
> In
> /etc/network/interfaces
> all is commented out -> DHCP -> Networkmanager

Are you running NetworkManager in session or system mode? In session mode NetworkManager will only bring networking once a user is logged into the
system which happens after mysql tries to start during boot.

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

[midnightflash (midnightflash)]

In sysv-rc-conf: (just giving the marked ones)

service 1 2 3 4 5 0 6 S

mysql* 2 3 4 5
NetworkMan 2 3 4 5
networking 0 6 S

So it seems to me as if it is in system mode.
I'm quite sure to set up this 8.10-64bit-system via debbootstrap from a 8.04-64-live-CD... as the 8.10-64-live-CD wasn't working properly on that machine.

[Mathias Gug (mathiaz)]

According to http://launchpadlibrarian.net/24564973/my.cnf, mysqld is configured to only bind to the loopback interface, which rules out any issue with NetworkManager. Could you provide the output of the following command:

# ls -l /etc/rc*/*

[midnightflash (midnightflash)]

it's my pleasure:

lrwxrwxrwx 1 root root 13 2. Dez 15:31 etc/rc0.d/K01gdm -> ../init.d/gdm
lrwxrwxrwx 1 root root 18 3. Dez 17:37 etc/rc0.d/K01timidity -> ../init.d/timidity
lrwxrwxrwx 1 root root 17 2. Dez 15:34 etc/rc0.d/K02usplash -> ../init.d/usplash
lrwxrwxrwx 1 root root 17 2. Dez 23:52 etc/rc0.d/K05preload -> ../init.d/preload
lrwxrwxrwx 1 root root 18 3. Dez 11:59 etc/rc0.d/K08vmware -> /etc/init.d/vmware
lrwxrwxrwx 1 root root 15 3. Dez 11:04 etc/rc0.d/K19samba -> ../init.d/samba
lrwxrwxrwx 1 root root 16 2. Dez 15:30 etc/rc0.d/K20apport -> ../init.d/apport
lrwxrwxrwx 1 root root 22 23. Jan 11:04 etc/rc0.d/K20boinc-client -> ../init.d/boinc-client
lrwxrwxrwx 1 root root 26 2. Dez 19:35 etc/rc0.d/K20clamav-freshclam -> ../init.d/clamav-freshclam
lrwxrwxrwx 1 root root 16 23. Jan 12:43 etc/rc0.d/K20distcc -> ../init.d/distcc
lrwxrwxrwx 1 root root 15 2. Dez 16:34 etc/rc0.d/K20exim4 -> ../init.d/exim4
lrwxrwxrwx 1 root root 20 2. Dez 19:29 etc/rc0.d/K20fancontrol -> ../init.d/fancontrol
lrwxrwxrwx 1 root root 17 2. Dez 19:29 etc/rc0.d/K20hddtemp -> ../init.d/hddtemp
lrwxrwxrwx 1 root root 25 2. Dez 18:43 etc/rc0.d/K20mldonkey-server -> ../init.d/mldonkey-server
lrwxrwxrwx 1 root root 17 3. Dez 10:46 etc/rc0.d/K20privoxy -> ../init.d/privoxy
lrwxrwxrwx 1 root root 17 2. Dez 19:35 etc/rc0.d/K20winbind -> ../init.d/winbind
lrwxrwxrwx 1 root root 14 7. Dez 13:48 etc/rc0.d/K20zvbi -> ../init.d/zvbi
lrwxrwxrwx 1 root root 15 4. Dez 06:30 etc/rc0.d/K21mysql -> ../init.d/mysql
lrwxrwxrwx 1 root root 19 4. Dez 06:30 etc/rc0.d/K22mysql-ndb -> ../init.d/mysql-ndb
lrwxrwxrwx 1 root root 23 4. Dez 06:30 etc/rc0.d/K23mysql-ndb-mgm -> ../init.d/mysql-ndb-mgm
lrwxrwxrwx 1 root root 20 2. Dez 14:42 etc/rc0.d/K25hwclock.sh -> ../init.d/hwclock.sh
lrwxrwxrwx 1 root root 15 2. Dez 16:34 etc/rc0.d/K25mdadm -> ../init.d/mdadm
lrwxrwxrwx 1 root root 20 2. Dez 15:30 etc/rc0.d/K50alsa-utils -> ../init.d/alsa-utils
lrwxrwxrwx 1 root root 26 2. Dez 14:42 etc/rc0.d/K63mountoverflowtmp -> ../init.d/mountoverflowtmp
lrwxrwxrwx 1 root root 19 2. Dez 15:35 etc/rc0.d/K74bluetooth -> ../init.d/bluetooth
lrwxrwxrwx 1 root root 28 2. Dez 18:07 etc/rc0.d/K74dkms_autoinstaller -> ../init.d/dkms_autoinstaller
lrwxrwxrwx 1 root root 17 2. Dez 19:35 etc/rc0.d/K80openvpn -> ../init.d/openvpn
lrwxrwxrwx 1 root root 22 2. Dez 15:35 etc/rc0.d/K86avahi-daemon -> ../init.d/avahi-daemon
lrwxrwxrwx 1 root root 21 2. Dez 15:29 etc/rc0.d/K99laptop-mode -> ../init.d/laptop-mode
-rw-r--r-- 1 root root 353 14. Okt 15:02 etc/rc0.d/README
lrwxrwxrwx 1 root root 22 2. Dez 15:32 etc/rc0.d/S15wpa-ifupdown -> ../init.d/wpa-ifupdown
lrwxrwxrwx 1 root root 18 2. Dez 14:42 etc/rc0.d/S20sendsigs -> ../init.d/sendsigs
lrwxrwxrwx 1 root root 17 2. Dez 14:42 etc/rc0.d/S30urandom -> ../init.d/urandom
lrwxrwxrwx 1 root root 22 2. Dez 14:42 etc/rc0.d/S31umountnfs.sh -> ../init.d/umountnfs.sh
lrwxrwxrwx 1 root root 20 2. Dez 14:43 etc/rc0.d/S35networking -> ../init.d/networking
lrwxrwxrwx 1 root root 18 2. Dez 14:42 etc/rc0.d/S40umountfs -> ../init.d/umountfs
lrwxrwxrwx 1 root root 20 2. Dez 14:42 etc/rc0.d/S60umountroot -> ../init.d/um...

[xteejx (xteejx)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu version (10.04). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

[xteejx (xteejx)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!