Bug#609897: [debian-mysql] Bug#609897: mysql-server-core-5.1: Mysqld failed message on boot (still there)
Am Donnerstag, den 13.01.2011, 18:30 +0100 schrieb r.ductor: Apparently the bug I reported in #589513 which was classed fixed by 5.1.49-2 is still there in 5.1.49-3: i.e. at boot I get a failed message, but after a ps gives a running mysqld. Which version of mysql-server-5.1 do you have installed? Please make sure that the mysql-server-5.1 package is also updated to 5.1.49-2 or newer. Could you please also send me the mysqld related informations during it's startup from /var/log/daemon.log? Norbert -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609897: [debian-mysql] Bug#609897: mysql-server-core-5.1: Mysqld failed message on boot (still there)
Hi Riccardo, please keep the @bugs.debian.org address in CC, thanks. Am Freitag, den 14.01.2011, 12:41 +0100 schrieb r.duc...@gmail.com: as shown below, I do not have the mysql-server-5.1 package at all. The init script checks for mysqld_safe since 5.1.49-2, which is part of the mysql-server-5.1 package. Could you please check if /etc/init.d/mysql checks for mysqld_safe in line 20 on your system? Of course my problem might not be a bug of the core package, but a dirty configuration inherited by bad automatic updates, as suggested in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589513#13 Did you modify the init-script in the past? The init scripts are treated as configuration files, so they will not get overwritten automatically when upgrading the package and the init script was manually edited in the past. Does a file called /etc/init.d/mysql.dpkg-dist exist on your system? Norbert -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609897: [debian-mysql] Bug#609897: mysql-server-core-5.1: Mysqld failed message on boot (still there)
Dear Norbert as shown below, I do not have the mysql-server-5.1 package at all. The point is that I do not explicitly use mysql and all mysql stuff that I have, namely mysql-server-core-5.1, come from automatic installations (as far as I remember). In this sense having a failed message at boot should not happen, I'm I wrong? It turned out from my previous bug report that there was a problem in a init script http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589513#16 Of course my problem might not be a bug of the core package, but a dirty configuration inherited by bad automatic updates, as suggested in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589513#13 in this case any suggestion to clean up my state is welcome. I was planning to aptitude full--upgrade but maybe I will wait your answer. Thanks for your time, all my best Riccardo # cat /var/log/daemon.log|egrep -i mysql Jan 14 10:03:28 galileo /etc/init.d/mysql[1925]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in Jan 14 10:03:28 galileo /etc/init.d/mysql[1925]: /etc/init.d/mysql: line 75: /usr/bin/mysqladmin: No such file or directory Jan 14 10:03:28 galileo /etc/init.d/mysql[1925]: # # aptitude search mysql|egrep '^i' i A libmysqlclient16- MySQL database client library i A libqt4-sql-mysql- Qt 4 MySQL database driver i A mysql-common- MySQL database common files, e.g. /etc/mys i A mysql-server-core-5.1 - MySQL database server binaries # aptitude search mysql-server p mysql-server- MySQL database server (metapackage depending on the latest version) c mysql-server-5.0- MySQL database server binaries c mysql-server-5.1- MySQL database server binaries and system database setup v mysql-server-core - v mysql-server-core-5.0 - i A mysql-server-core-5.1 - MySQL database server binaries v virtual-mysql-server- On Friday 14 January 2011 11:41:15 you wrote: Am Donnerstag, den 13.01.2011, 18:30 +0100 schrieb r.ductor: Apparently the bug I reported in #589513 which was classed fixed by 5.1.49-2 is still there in 5.1.49-3: i.e. at boot I get a failed message, but after a ps gives a running mysqld. Which version of mysql-server-5.1 do you have installed? Please make sure that the mysql-server-5.1 package is also updated to 5.1.49-2 or newer. Could you please also send me the mysqld related informations during it's startup from /var/log/daemon.log? Norbert -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609897: [debian-mysql] Bug#609897: mysql-server-core-5.1: Mysqld failed message on boot (still there)
Dear Norbert
Could you please check if /etc/init.d/mysql checks for mysqld_safe in
line 20 on your system?
No, it tests -x /usr/sbin/mysqld
(but the #13 mentions mysqld_safe)
So, if I understand well,
either my /usr/sbin/mysqld does not correspond to = 5.1.49-2 (for which reason
has not been updated?)
or /usr/sbin/mysqld v5.1.49-2 is still buggy...
I attach my version of /usr/sbin/mysqld
Did you modify the init-script in the past? The init scripts are treated
as configuration files, so they will not get overwritten automatically
when upgrading the package and the init script was manually edited in
the past.
No, I do not think so (I do not use mysql at all).
Does a file called /etc/init.d/mysql.dpkg-dist exist on your system?
No
Riccardo
--- INFO --
galileo:~# head -n 25 /etc/init.d/mysql|cat -n
1 #!/bin/bash
2 #
3 ### BEGIN INIT INFO
4 # Provides: mysql
5 # Required-Start:$remote_fs $syslog
6 # Required-Stop: $remote_fs $syslog
7 # Should-Start: $network $named $time
8 # Should-Stop: $network $named $time
9 # Default-Start: 2 3 4 5
10 # Default-Stop: 0 1 6
11 # Short-Description: Start and stop the mysql database server daemon
12 # Description: Controls the main MySQL database server daemon
mysqld
13 #and its wrapper script mysqld_safe.
14 ### END INIT INFO
15 #
16 set -e
17 set -u
18 ${DEBIAN_SCRIPT_DEBUG:+ set -v -x}
19
20 test -x /usr/sbin/mysqld || exit 0
21
22 . /lib/lsb/init-functions
23
24 SELF=$(cd $(dirname $0); pwd -P)/$(basename $0)
25 CONF=/etc/mysql/my.cnf
galileo:~# ls /etc/init.d/mysql.dpkg-dist
ls: cannot access /etc/init.d/mysql.dpkg-dist: No such file or directory
galileo:~#
etc_init.d_mysql_2011-01-14
Description: application/shellscript
Bug#609897: [debian-mysql] Bug#609897: mysql-server-core-5.1: Mysqld failed message on boot (still there)
Am Freitag, den 14.01.2011, 16:44 +0100 schrieb r.duc...@gmail.com: Dear Norbert Could you please check if /etc/init.d/mysql checks for mysqld_safe in line 20 on your system? No, it tests -x /usr/sbin/mysqld (but the #13 mentions mysqld_safe) It definitely tests for /usr/bin/mysqld_safe since 5.1.49-2, I don't know why you're still having an outdated init script on your system. http://svn.debian.org/wsvn/pkg-mysql/mysql-dfsg-5.1/branches/unstable/debian/mysql-server-5.1.mysql.init Norbert -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609897: [debian-mysql] Bug#609897: mysql-server-core-5.1: Mysqld failed message on boot (still there)
On Friday 14 January 2011 17:55:03 you wrote: I don't know why you're still having an outdated init script on your system. Neither me :) I vaguely remember that during an upgrade I was asked to choose a password (for the database, I guess). If I gave it (do not remember) could this (non-locally) prevent the upgrade of the init.d/mysql ? No warnings about locally modified files in my last /var/log/apt/term, see below. (Aptitude should not have reported a conflict?) With the /etc/init.d/mysql file I sent you could check that it corresponds to 5.1.49-1(and formally prove I've not touched the file). Which package should trigger in its set-up the update of the /etc/init.d/mysql ? Maybe there is an error in the pre-installation scripts. Or ?? a packaging error in the deb file ?? Shall I reset my Mysql or do you need more info/time? (How to reset?) By the way, the original boot failure was detected also in two other debian machines I have (x86). I've not updated them, maybe it would be interesting to see what happens if I update the other two. Do you want me report on that? Riccardo --- INFO --- galileo:~# cat var_log_apt_term_2010-12-21.log |grep -i -C2 mysql Preparing to replace libqt4-help 4:4.6.3-1+b1 (using .../libqt4-help_4%3a4.6.3-4_amd64.deb) ... Unpacking replacement libqt4-help ... Preparing to replace mysql-common 5.1.49-1 (using .../mysql-common_5.1.49-3_all.deb) ... Unpacking replacement mysql-common ... Preparing to replace libmysqlclient16 5.1.49-1 (using .../libmysqlclient16_5.1.49-3_amd64.deb) ... Unpacking replacement libmysqlclient16 ... Preparing to replace libqt4-sql-mysql 4:4.6.3-1+b1 (using .../libqt4-sql-mysql_4%3a4.6.3-4_amd64.deb) ... Unpacking replacement libqt4-sql-mysql ... Preparing to replace libsqlite3-0 3.7.2-1 (using .../libsqlite3-0_3.7.3-1_amd64.deb) ... Unpacking replacement libsqlite3-0 ... -- Preparing to replace mobile-broadband-provider-info 20100910-1 (using .../mobile-broadband-provider-info_20101106-1_all.deb) ... Unpacking replacement mobile-broadband-provider-info ... Preparing to replace mysql-server-core-5.1 5.1.49-1 (using .../mysql-server-core-5.1_5.1.49-3_amd64.deb) ... Unpacking replacement mysql-server-core-5.1 ... Preparing to replace wpasupplicant 0.6.10-2 (using .../wpasupplicant_0.6.10-2.1_amd64.deb) ... Unpacking replacement wpasupplicant ... -- Setting up libqt4-scripttools (4:4.6.3-4) ... Setting up libqt4-help (4:4.6.3-4) ... Setting up mysql-common (5.1.49-3) ... Setting up libmysqlclient16 (5.1.49-3) ... Setting up libqt4-sql-mysql (4:4.6.3-4) ... Setting up libsqlite3-0 (3.7.3-1) ... Setting up libqt4-sql-sqlite (4:4.6.3-4) ... -- Installing new version of config file /etc/menu-methods/lang.h ... Setting up mobile-broadband-provider-info (20101106-1) ... Setting up mysql-server-core-5.1 (5.1.49-3) ... Setting up wpasupplicant (0.6.10-2.1) ... Setting up network-manager (0.8.1-5) ... galileo:~# -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
