PDA

View Full Version : mysql on startup



rappie
08-19-2005, 12:04 PM
Hi All,

I've created a remastered version of Knoppix 3.9 with apache, php and mysql 4.1 . I'm having a strange problem on startup, Apache starts up OK but when I try to startup mysql it requires four commands (one at boot time) before it will actually start up i.e.

TRY 1

root@0[~]# /etc/init.d/mysql start
Starting MySQL database server: mysqld...failed.
Please take a look at the syslog.
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)'
Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!

TRY 2

root@0[~]# /etc/init.d/mysql start
Starting MySQL database server: mysqld...failed.
Please take a look at the syslog.
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)'
Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!

TRY 3

root@0[~]# /etc/init.d/mysql start
Starting MySQL database server: mysqld.
Checking for crashed MySQL tables in the background.
root@0[~]#

Then mysql starts OK

with mysqld I get

TRY 1

root@1[~]# mysqld
InnoDB: Unable to lock ./ib_logfile0, error: 9
InnoDB: Error in opening ./ib_logfile0
050819 11:40:59 [ERROR] Can't init databases
050819 11:40:59 [ERROR] Aborting

050819 11:41:00 [Note] mysqld: Shutdown complete

TRY 2

root@1[~]# mysqld
InnoDB: Unable to lock ./ib_logfile1, error: 9
InnoDB: Error in opening ./ib_logfile1
050819 11:41:06 [ERROR] Can't init databases
050819 11:41:06 [ERROR] Aborting

050819 11:41:07 [Note] mysqld: Shutdown complete

TRY 3

root@1[~]# mysqld
050819 11:41:11 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
050819 11:41:13 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 43782.
InnoDB: Doing recovery: scanned up to log sequence number 0 43782
InnoDB: Last MySQL binlog file position 0 79, file name /var/log/mysql/mysql-bin.000010
050819 11:41:13 InnoDB: Flushing modified pages from the buffer pool...
050819 11:41:13 InnoDB: Started; log sequence number 0 43782
mysqld: ready for connections.
Version: '4.1.11-Debian_4-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Source distribution

mysql start OK

I managed to overcome the problem on startup by having 4 startup scripts, but this extends the startup time by quite a bit so I would like to find a better fix. Has anyone seen this before or know of a fix.

Thanks

spyhome
08-19-2005, 01:59 PM
I did the mysql start like this:

in /KNOPPIX/knoppix.sh I added

/etc/init.d/mysql stop
chown -R mysql:mysql /var/lib/mysql
chmod ugo+rwx /var/lib/mysql/*
chmod -R ugo+rw /var/lib/mysql
touch /var/log/mysql/mysql.log
chown mysql:adm /var/log/mysql/mysql.log
sleep 5
/etc/init.d/mysql start

cat /cdrom/[MyFolder]/sqldb.sql | /usr/bin/mysql -p[TheRootPasswd]

rappie
08-19-2005, 02:06 PM
Thanks for the reply, is it a permissions problem then. If so, how come it starts up after a few tries?

markpreston
08-20-2005, 11:38 PM
mysqld_safe may be useful for you to start mysql
see
http://dev.mysql.com/doc/mysql/en/mysqld-safe.html

In the past I used

rm -rf /var/lib/mysql
cp -rp /KNOPPIX/var/lib/mysql /var/lib
mysqld_safe &


which worked for Knoppix 3.3, but whether it works for 3.9 I don't know.
The p option to the cp command preserves permissions.
Regards,
Mark