On Thu, Jan 20, 2005 at 12:12:35PM +0100, Mechtilde Stehmann wrote: > Hi everyone, > It' s enough to despair: > After the update of my MySQl 4.1.7 to mysql 4.1.8a (Debian-Sarge)the > mysql server doesn't start anymore. From where did you get these packages? The latest version in testing is 4.0.23-1 and the latest in experimental is 4.1.7-2. > > Can anyone give tips to fix the problems. > > In the log-files I've found are following entries: > > daemon.log from the day updating the system > > > Jan 8 14:01:49 localhost init: Trying to re-exec init > Jan 8 14:05:31 localhost mysqld[439]: 050108 14:05:30 [Note] > /usr/sbin/mysqld: Normal shutdown > Jan 8 14:05:31 localhost mysqld[439]: > Jan 8 14:05:31 localhost mysqld[439]: 050108 14:05:31 [Note] > /usr/sbin/mysqld: Shutdown complete > Jan 8 14:05:31 localhost mysqld[439]: > Jan 8 14:05:32 localhost /etc/init.d/mysql[3729]: 2 processes alive and > '/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf ping' > resulted in > Jan 8 14:05:32 localhost /etc/init.d/mysql[3729]: > ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed > Jan 8 14:05:32 localhost /etc/init.d/mysql[3729]: error: 'Can't connect > to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)' > Jan 8 14:05:32 localhost /etc/init.d/mysql[3729]: Check that mysqld is > running and that the socket: '/var/run/mysqld/mysqld.sock' exists! If I interpret this correctly, the server tries to start, but it cant connect to the socket afterwards. > Jan 8 14:05:32 localhost /etc/init.d/mysql[3729]: > Jan 8 14:05:32 localhost mysqld_safe[3732]: ended > Jan 8 14:12:48 localhost mysqld_safe[5274]: PLEASE REMEMBER TO SET A > PASSWORD FOR THE MySQL root USER ! > Jan 8 14:12:48 localhost mysqld_safe[5274]: To do so, start the server, > then issue the following commands: > Jan 8 14:12:48 localhost mysqld_safe[5274]: /usr/bin/mysqladmin -u root > password 'new-password' > Jan 8 14:12:48 localhost mysqld_safe[5274]: /usr/bin/mysqladmin -u root > -h marcus password 'new-password' > Jan 8 14:12:48 localhost mysqld_safe[5274]: See the manual for more > instructions. > Jan 8 14:12:48 localhost mysqld_safe[5274]: > Jan 8 14:12:48 localhost mysqld_safe[5274]: NOTE: If you are upgrading > from a MySQL <= 3.22.10 you should run > Jan 8 14:12:48 localhost mysqld_safe[5274]: the > /usr/bin/mysql_fix_privilege_tables. Otherwise you will not be > Jan 8 14:12:48 localhost mysqld_safe[5274]: able to use the new GRANT > command! Did you create the mysql database (the database holding priviliges information) with a version prior to 3.22.10? If so did you run mysql_fix_privileges_tables? Mysql seems to think that your priviliges tables are not correct. It also seems that you did not set a root password for the databese server. > Jan 8 14:12:48 localhost mysqld_safe[5274]: > Jan 8 14:12:48 localhost mysqld_safe[5274]: Please report any problems > with the /usr/bin/mysqlbug script! > Jan 8 14:12:48 localhost mysqld_safe[5274]: > Jan 8 14:12:48 localhost mysqld_safe[5274]: The latest information > about MySQL is available on the web at > Jan 8 14:12:48 localhost mysqld_safe[5274]: http://www.mysql.com > Jan 8 14:12:48 localhost mysqld_safe[5274]: Support MySQL by buying > support/licenses at https://order.mysql.com > Jan 8 14:12:49 localhost mysqld_safe[5323]: ERROR: 1054 Unknown column > 'Show_db_priv' in 'field list' > Jan 8 14:12:49 localhost mysqld_safe[5388]: started > Jan 8 14:12:49 localhost mysqld[5391]: 050108 14:12:49 [ERROR] bdb: > unable to initialize mutex: Function not implemented > Jan 8 14:12:49 localhost mysqld[5391]: 050108 14:12:49 [ERROR] bdb: > process-private: unable to initialize environment lock: Function not > implemented > Jan 8 14:12:49 localhost mysqld[5391]: 050108 14:12:49 [ERROR] Can't > init databases > Jan 8 14:12:49 localhost mysqld[5391]: 050108 14:12:49 [ERROR] Aborting > Jan 8 14:12:49 localhost mysqld[5391]: > Jan 8 14:12:49 localhost mysqld[5391]: 050108 14:12:49 [Note] > /usr/sbin/mysqld: Shutdown complete > Jan 8 14:12:49 localhost mysqld[5391]: > Jan 8 14:12:49 localhost mysqld_safe[5393]: ended Here somehow it cannot initialise the databeses. It does not really say why though. Gaudenz > Jan 8 14:12:56 localhost /etc/init.d/mysql[5435]: 0 processes alive and > '/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf ping' > resulted in > Jan 8 14:12:56 localhost /etc/init.d/mysql[5435]: > ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed > Jan 8 14:12:56 localhost /etc/init.d/mysql[5435]: error: 'Can't connect > to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)' > Jan 8 14:12:56 localhost /etc/init.d/mysql[5435]: Check that mysqld is > running and that the socket: '/var/run/mysqld/mysqld.sock' exists! > Jan 8 14:12:56 localhost /etc/init.d/mysql[5435]: > > > And the last syslog-file: > > Jan 19 20:53:02 localhost /USR/SBIN/CRON[901]: (mail) CMD ( if [ -x > /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then > /usr/lib/exim/exim3 -q ; fi) > Jan 19 20:55:46 localhost mysqld_safe[963]: started > Jan 19 20:55:46 localhost mysqld[966]: 050119 20:55:46 [ERROR] bdb: > unable to initialize mutex: Function not implemented > Jan 19 20:55:46 localhost mysqld[966]: 050119 20:55:46 [ERROR] bdb: > process-private: unable to initialize environment lock: Function not > implemented > Jan 19 20:55:46 localhost mysqld[966]: 050119 20:55:46 InnoDB: Started; > log sequence number 0 43634 > Jan 19 20:55:46 localhost mysqld[966]: 050119 20:55:46 [ERROR] Can't > init databases > Jan 19 20:55:46 localhost mysqld[966]: 050119 20:55:46 [ERROR] Aborting > Jan 19 20:55:46 localhost mysqld[966]: > Jan 19 20:55:46 localhost mysqld[966]: 050119 20:55:46 InnoDB: Starting > shutdown... > Jan 19 20:55:49 localhost mysqld[966]: 050119 20:55:49 InnoDB: Shutdown > completed; log sequence number 0 43634 > Jan 19 20:55:49 localhost mysqld[966]: 050119 20:55:49 [Note] > /usr/sbin/mysqld: Shutdown complete > Jan 19 20:55:49 localhost mysqld[966]: > Jan 19 20:55:49 localhost mysqld_safe[979]: ended > Jan 19 20:55:54 localhost /etc/init.d/mysql[1018]: 0 processes alive and > '/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf ping' > resulted in > Jan 19 20:55:54 localhost /etc/init.d/mysql[1018]: > ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed > Jan 19 20:55:54 localhost /etc/init.d/mysql[1018]: error: 'Can't connect > to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)' > Jan 19 20:55:54 localhost /etc/init.d/mysql[1018]: Check that mysqld is > running and that the socket: '/var/run/mysqld/mysqld.sock' exists! > Jan 19 20:55:54 localhost /etc/init.d/mysql[1018]: > Jan 19 21:07:42 localhost apmd[377]: Suspending now > Jan 19 21:23:01 localhost /USR/SBIN/CRON[1084]: (mail) CMD ( if [ -x > /usr/lib/exim/exim3 -a -f /etc/exim/exim.conf ]; then > /usr/lib/exim/exim3 -q ; fi) > Jan 19 21:24:14 localhost apmd[377]: Suspending now > > What's wrong? > > Mechtilde > > > -- > To UNSUBSCRIBE, email to debian-women-request@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmaster@lists.debian.org >
Attachment:
signature.asc
Description: Digital signature