| 2009-02-08 05:27:39 |
Will Uther |
bug |
|
|
added bug |
| 2009-03-30 21:36:06 |
Mathias Gug |
mysql-dfsg-5.0: status |
New |
Incomplete |
|
| 2009-03-30 21:36:06 |
Mathias Gug |
mysql-dfsg-5.0: statusexplanation |
|
Thank you for taking the time to report this bug and helping to make Ubuntu better. When you're running into the issue, does mysqld_safe takes up 100% of the cpu? |
|
| 2009-04-09 15:40:24 |
MarcRandolph |
mysql-dfsg-5.0 (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2009-04-14 11:42:48 |
MarcRandolph |
bug task added |
|
mythbuntu |
|
| 2009-04-14 11:49:23 |
MarcRandolph |
mythbuntu: importance |
Undecided |
Critical |
|
| 2009-04-14 11:49:23 |
MarcRandolph |
mythbuntu: status |
New |
Confirmed |
|
| 2009-04-14 11:49:23 |
MarcRandolph |
mythbuntu: milestone |
|
jaunty-rc |
|
| 2009-04-21 23:34:14 |
Will Uther |
summary |
mysql thinks it has crashed when it hasn't |
mysqld_safe thinks mysqld has crashed when it hasn't |
|
| 2009-05-04 19:50:40 |
Mario Limonciello |
attachment added |
|
mysql.debdiff http://launchpadlibrarian.net/26324395/mysql.debdiff |
|
| 2009-05-05 18:31:14 |
Mario Limonciello |
bug task added |
|
mysql-dfsg-5.0 (Ubuntu Jaunty) |
|
| 2009-05-05 18:31:14 |
Mario Limonciello |
bug task added |
|
mysql-dfsg-5.0 (Ubuntu Karmic) |
|
| 2009-05-05 18:31:33 |
Mario Limonciello |
mysql-dfsg-5.0 (Ubuntu Jaunty): status |
New |
Confirmed |
|
| 2009-05-05 18:40:56 |
Mario Limonciello |
description |
Binary package hint: mysql-server-5.0
I'm running mythtv on jaunty with mysql-server-5.0 version 5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts, then mysql restarts and mythtv gets confused.
What seems to be happening is that line 387 (or 389?) of /usr/bin/mysqld_safe is falling through when it shouldn't. mysqld_safe is a script that starts mysqld and restarts it if it crashes. Here are some relevant syslog sections:
Feb 8 12:35:07 willvo mysqld_safe[3668]: started
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:08 willvo mysqld[3671]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3710]: Upgrading MySQL tables if necessary.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysql' as: /usr/bin/mysql
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: This installation of MySQL is already upgraded to 5.0.75, use --force if you still need to run mysql_upgrade
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3720]: Checking for insecure root accounts.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3724]: Triggering myisam-recover for all MyISAM tables
Feb 8 12:35:13 willvo mythtv-backend[4560]: Started mythtv-backend
Feb 8 12:35:16 willvo mysqld_safe[5212]: Number of processes running now: 1
Feb 8 12:35:16 willvo mysqld_safe[5223]: mysqld process hanging, pid 3670 - killed
Feb 8 12:35:16 willvo mysqld_safe[5227]: restarted
Feb 8 12:35:16 willvo mysqld[5231]: 090208 12:35:16 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:17 willvo mysqld[5231]: 090208 12:35:17 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:17 willvo mysqld[5231]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Note that mysqld_safe is finds one mysqld process still running after it is supposed to have crashed. mysqld_safe then kills that process and starts another. This only seems to happen once during boot - it doesn't keep restarting mysqld in normal use.
The problem is somewhat intermittent. I made it go away once before by mysqlrepairing my tables, but they seem fine now. Debian bug 418648 looks somewhat similar but slightly different (and the fix they used doesn't work for me).
My current fix is to replace:
$NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --d
atadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-external-locking 2>&1 |
$ERR_LOGGER -t mysqld & wait
with:
$NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --dat
adir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-external-locking 2>&1 | $
ERR_LOGGER -t mysqld
in the mysqld_safe script (the second line has " & wait" removed from the end). This seems to fix the problem. I don't understand the difference in semantics between " & wait" and normal process termination.
Will |
--Impact--
I'm running mythtv on jaunty with mysql-server-5.0 version 5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts, then mysql restarts and mythtv gets confused.
This is caused by some portions of a debian patch that is applied on top of MySQL. It has not been accepted yet at upstream MySQL. The MySQL server is receiving a SIGHUP which the behavior is changed because of the debian patch.
Here are some relevant syslog sections:
Feb 8 12:35:07 willvo mysqld_safe[3668]: started
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:08 willvo mysqld[3671]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3710]: Upgrading MySQL tables if necessary.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysql' as: /usr/bin/mysql
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: This installation of MySQL is already upgraded to 5.0.75, use --force if you still need to run mysql_upgrade
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3720]: Checking for insecure root accounts.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3724]: Triggering myisam-recover for all MyISAM tables
Feb 8 12:35:13 willvo mythtv-backend[4560]: Started mythtv-backend
Feb 8 12:35:16 willvo mysqld_safe[5212]: Number of processes running now: 1
Feb 8 12:35:16 willvo mysqld_safe[5223]: mysqld process hanging, pid 3670 - killed
Feb 8 12:35:16 willvo mysqld_safe[5227]: restarted
Feb 8 12:35:16 willvo mysqld[5231]: 090208 12:35:16 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:17 willvo mysqld[5231]: 090208 12:35:17 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:17 willvo mysqld[5231]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Note that mysqld_safe is finds one mysqld process still running after it is supposed to have crashed. mysqld_safe then kills that process and starts another. This only seems to happen once during boot - it doesn't keep restarting mysqld in normal use.
--Addressing--
This has *not* yet been addressed in the karmic branch, but it has been verified that a PPA resolve the problem. MySQL hasn't changed yet in karmic, so this can easily be brought to karmic if viewed to properly solve the problem.
--Test Case--
To reproduce this, you can boot up off of a fresh install of Mythbuntu 9.04 (which includes MySQL and mythtv-backend preinstalled). Check /var/log/syslog and you will see errors regarding mysql getting restarted because of a hanging process. Depending on the speed of your system, this may or may not cause problems with mythtv-backend because of the race condition inherent in this problem.
--Regression Potential--
This type of patch has implications if users were dependent on the behavior of this debian/ubuntu specific patch to issue a mysql refresh via a SIGHUP. |
|
| 2009-05-05 18:41:20 |
Mario Limonciello |
mythbuntu: status |
Confirmed |
Triaged |
|
| 2009-05-05 18:41:20 |
Mario Limonciello |
mythbuntu: milestone |
jaunty-rc |
|
|
| 2009-05-05 18:43:54 |
Mario Limonciello |
bug |
|
|
added subscriber Ubuntu Release Team |
| 2009-05-05 18:44:43 |
Mario Limonciello |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2009-05-05 21:15:08 |
Martin Pitt |
mysql-dfsg-5.0 (Ubuntu Karmic): assignee |
|
Canonical Server Team (canonical-server) |
|
| 2009-05-05 21:15:37 |
Martin Pitt |
removed subscriber Ubuntu Release Team |
|
|
|
| 2009-05-06 10:41:22 |
Martin Pitt |
mysql-dfsg-5.0 (Ubuntu Jaunty): status |
Confirmed |
Fix Committed |
|
| 2009-05-06 10:41:29 |
Martin Pitt |
tags |
|
verification-needed |
|
| 2009-05-07 19:15:05 |
Mathias Gug |
mysql-dfsg-5.0 (Ubuntu Jaunty): status |
Fix Committed |
Confirmed |
|
| 2009-05-07 19:16:25 |
Mathias Gug |
tags |
verification-needed |
|
|
| 2009-05-07 19:34:53 |
Steve Langasek |
tags |
|
verification-failed |
|
| 2009-05-08 14:13:49 |
Dewey_Oxberger |
bug watch added |
|
http://bugs.mysql.com/bug.php?id=34312 |
|
| 2009-05-11 01:37:38 |
Will Uther |
description |
--Impact--
I'm running mythtv on jaunty with mysql-server-5.0 version 5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts, then mysql restarts and mythtv gets confused.
This is caused by some portions of a debian patch that is applied on top of MySQL. It has not been accepted yet at upstream MySQL. The MySQL server is receiving a SIGHUP which the behavior is changed because of the debian patch.
Here are some relevant syslog sections:
Feb 8 12:35:07 willvo mysqld_safe[3668]: started
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:08 willvo mysqld[3671]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3710]: Upgrading MySQL tables if necessary.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysql' as: /usr/bin/mysql
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: This installation of MySQL is already upgraded to 5.0.75, use --force if you still need to run mysql_upgrade
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3720]: Checking for insecure root accounts.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3724]: Triggering myisam-recover for all MyISAM tables
Feb 8 12:35:13 willvo mythtv-backend[4560]: Started mythtv-backend
Feb 8 12:35:16 willvo mysqld_safe[5212]: Number of processes running now: 1
Feb 8 12:35:16 willvo mysqld_safe[5223]: mysqld process hanging, pid 3670 - killed
Feb 8 12:35:16 willvo mysqld_safe[5227]: restarted
Feb 8 12:35:16 willvo mysqld[5231]: 090208 12:35:16 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:17 willvo mysqld[5231]: 090208 12:35:17 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:17 willvo mysqld[5231]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Note that mysqld_safe is finds one mysqld process still running after it is supposed to have crashed. mysqld_safe then kills that process and starts another. This only seems to happen once during boot - it doesn't keep restarting mysqld in normal use.
--Addressing--
This has *not* yet been addressed in the karmic branch, but it has been verified that a PPA resolve the problem. MySQL hasn't changed yet in karmic, so this can easily be brought to karmic if viewed to properly solve the problem.
--Test Case--
To reproduce this, you can boot up off of a fresh install of Mythbuntu 9.04 (which includes MySQL and mythtv-backend preinstalled). Check /var/log/syslog and you will see errors regarding mysql getting restarted because of a hanging process. Depending on the speed of your system, this may or may not cause problems with mythtv-backend because of the race condition inherent in this problem.
--Regression Potential--
This type of patch has implications if users were dependent on the behavior of this debian/ubuntu specific patch to issue a mysql refresh via a SIGHUP. |
--Impact--
I'm running mythtv on jaunty with mysql-server-5.0 version 5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts, then mysql restarts and mythtv gets confused.
This is caused by some portions of a debian patch that is applied on top of MySQL. It has not been accepted yet at upstream MySQL. The MySQL server is receiving a SIGHUP which the behavior is changed because of the debian patch.
Here are some relevant syslog sections:
Feb 8 12:35:07 willvo mysqld_safe[3668]: started
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:08 willvo mysqld[3671]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3710]: Upgrading MySQL tables if necessary.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysql' as: /usr/bin/mysql
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: This installation of MySQL is already upgraded to 5.0.75, use --force if you still need to run mysql_upgrade
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3720]: Checking for insecure root accounts.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3724]: Triggering myisam-recover for all MyISAM tables
Feb 8 12:35:13 willvo mythtv-backend[4560]: Started mythtv-backend
Feb 8 12:35:16 willvo mysqld_safe[5212]: Number of processes running now: 1
Feb 8 12:35:16 willvo mysqld_safe[5223]: mysqld process hanging, pid 3670 - killed
Feb 8 12:35:16 willvo mysqld_safe[5227]: restarted
Feb 8 12:35:16 willvo mysqld[5231]: 090208 12:35:16 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:17 willvo mysqld[5231]: 090208 12:35:17 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:17 willvo mysqld[5231]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Note that mysqld_safe is finds one mysqld process still running after it is supposed to have crashed. mysqld_safe then kills that process and starts another. This only seems to happen once during boot - it doesn't keep restarting mysqld in normal use.
--Addressing--
This has *not* yet been addressed in the karmic branch, but it has been verified that a PPA resolve the problem. MySQL hasn't changed yet in karmic, so this can easily be brought to karmic if viewed to properly solve the problem.
--Test Case - Myth
To reproduce this, you can boot up off of a fresh install of Mythbuntu 9.04 (which includes MySQL and mythtv-backend preinstalled). Check /var/log/syslog and you will see errors regarding mysql getting restarted because of a hanging process. Depending on the speed of your system, this may or may not cause problems with mythtv-backend because of the race condition inherent in this problem.
-- Test Case - non-Myth
sudo killall -HUP mysqld_safe # should cause mysql to reload its config, but causes it to restart instead.
--Regression Potential--
This type of patch has implications if users were dependent on the behavior of this debian/ubuntu specific patch to issue a mysql refresh via a SIGHUP. |
|
| 2009-05-12 00:00:11 |
Mathias Gug |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=208364 |
|
| 2009-05-12 03:04:21 |
Mathias Gug |
attachment added |
|
mysql-dfsg-5.0_5.1.30really5.0.75-0ubuntu10.2.debdiff http://launchpadlibrarian.net/26619255/mysql-dfsg-5.0_5.1.30really5.0.75-0ubuntu10.2.debdiff |
|
| 2009-05-12 06:54:17 |
MarcRandolph |
attachment added |
|
Determine the process ID of SIGHUP source http://launchpadlibrarian.net/26623864/sig_src.c |
|
| 2009-05-12 14:39:21 |
Mathias Gug |
description |
--Impact--
I'm running mythtv on jaunty with mysql-server-5.0 version 5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts, then mysql restarts and mythtv gets confused.
This is caused by some portions of a debian patch that is applied on top of MySQL. It has not been accepted yet at upstream MySQL. The MySQL server is receiving a SIGHUP which the behavior is changed because of the debian patch.
Here are some relevant syslog sections:
Feb 8 12:35:07 willvo mysqld_safe[3668]: started
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:08 willvo mysqld[3671]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3710]: Upgrading MySQL tables if necessary.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysql' as: /usr/bin/mysql
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: This installation of MySQL is already upgraded to 5.0.75, use --force if you still need to run mysql_upgrade
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3720]: Checking for insecure root accounts.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3724]: Triggering myisam-recover for all MyISAM tables
Feb 8 12:35:13 willvo mythtv-backend[4560]: Started mythtv-backend
Feb 8 12:35:16 willvo mysqld_safe[5212]: Number of processes running now: 1
Feb 8 12:35:16 willvo mysqld_safe[5223]: mysqld process hanging, pid 3670 - killed
Feb 8 12:35:16 willvo mysqld_safe[5227]: restarted
Feb 8 12:35:16 willvo mysqld[5231]: 090208 12:35:16 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:17 willvo mysqld[5231]: 090208 12:35:17 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:17 willvo mysqld[5231]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Note that mysqld_safe is finds one mysqld process still running after it is supposed to have crashed. mysqld_safe then kills that process and starts another. This only seems to happen once during boot - it doesn't keep restarting mysqld in normal use.
--Addressing--
This has *not* yet been addressed in the karmic branch, but it has been verified that a PPA resolve the problem. MySQL hasn't changed yet in karmic, so this can easily be brought to karmic if viewed to properly solve the problem.
--Test Case - Myth
To reproduce this, you can boot up off of a fresh install of Mythbuntu 9.04 (which includes MySQL and mythtv-backend preinstalled). Check /var/log/syslog and you will see errors regarding mysql getting restarted because of a hanging process. Depending on the speed of your system, this may or may not cause problems with mythtv-backend because of the race condition inherent in this problem.
-- Test Case - non-Myth
sudo killall -HUP mysqld_safe # should cause mysql to reload its config, but causes it to restart instead.
--Regression Potential--
This type of patch has implications if users were dependent on the behavior of this debian/ubuntu specific patch to issue a mysql refresh via a SIGHUP. |
--Impact--
I'm running mythtv on jaunty with mysql-server-5.0 version 5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts, then mysql restarts and mythtv gets confused.
This is caused by some portions of a debian patch that is applied on top of MySQL. It has not been accepted yet at upstream MySQL. The MySQL server is receiving a SIGHUP which the behavior is changed because of the debian patch.
Here are some relevant syslog sections:
Feb 8 12:35:07 willvo mysqld_safe[3668]: started
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:08 willvo mysqld[3671]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3710]: Upgrading MySQL tables if necessary.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysql' as: /usr/bin/mysql
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: This installation of MySQL is already upgraded to 5.0.75, use --force if you still need to run mysql_upgrade
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3720]: Checking for insecure root accounts.
Feb 8 12:35:08 willvo /etc/mysql/debian-start[3724]: Triggering myisam-recover for all MyISAM tables
Feb 8 12:35:13 willvo mythtv-backend[4560]: Started mythtv-backend
Feb 8 12:35:16 willvo mysqld_safe[5212]: Number of processes running now: 1
Feb 8 12:35:16 willvo mysqld_safe[5223]: mysqld process hanging, pid 3670 - killed
Feb 8 12:35:16 willvo mysqld_safe[5227]: restarted
Feb 8 12:35:16 willvo mysqld[5231]: 090208 12:35:16 InnoDB: Started; log sequence number 0 43655
Feb 8 12:35:17 willvo mysqld[5231]: 090208 12:35:17 [Note] /usr/sbin/mysqld: ready for connections.
Feb 8 12:35:17 willvo mysqld[5231]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
Note that mysqld_safe is finds one mysqld process still running after it is supposed to have crashed. mysqld_safe then kills that process and starts another. This only seems to happen once during boot - it doesn't keep restarting mysqld in normal use.
--Addressing--
This has *not* yet been addressed in the karmic branch, but it has been verified that a PPA resolve the problem. MySQL hasn't changed yet in karmic, so this can easily be brought to karmic if viewed to properly solve the problem.
The problem comes from the fact that mysqld_safe starts mysqld and then waits for its crash. However installing a trap for SIGHUP makes the wait command return immediately when a SIGHUP is received by mysqld_safe. This mysqld_safe proceed to kill the remaining mysqld process (which hasn't crashed). The proposed fix is to add a wait command to the trap.
-- Test Case
1. Install mysql-server-5.0 and watch the log. Record the PID of mysqld. Issue a status command to see how many flush tables have been done:
$ sudo /usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf status
Uptime: 36 Threads: 1 Questions: 1 Slow queries: 0 Opens: 12 Flush tables: 1 Open tables: 6 Queries per second avg: 0.028
2. From a terminal:
sudo killall -HUP mysqld_safe
3.
a. WIthtout the patch: mysqld_safe reports that a mysqld process is stuck, kills it and restarts it. This can be verified by checking that mysqld has new a PID.
b. With the patch: mysqld is *not* restarted. mysqld has the same PID. Only the refresh command is sent to mysqld. This can be verified by checking that the number of flush tables has been incremented by one.
--Regression Potential--
There isn't any change in behavior. Signals are still handled the way they were before. |
|
| 2009-05-12 14:39:21 |
Mathias Gug |
tags |
verification-failed |
|
|
| 2009-05-12 14:40:15 |
Mathias Gug |
mysql-dfsg-5.0 (Ubuntu Karmic): status |
Confirmed |
In Progress |
|
| 2009-05-12 14:40:15 |
Mathias Gug |
mysql-dfsg-5.0 (Ubuntu Karmic): assignee |
Canonical Server Team (canonical-server) |
Mathias Gug (mathiaz) |
|
| 2009-05-12 14:40:38 |
Mathias Gug |
mysql-dfsg-5.0 (Ubuntu Jaunty): status |
Confirmed |
In Progress |
|
| 2009-05-12 14:40:38 |
Mathias Gug |
mysql-dfsg-5.0 (Ubuntu Jaunty): assignee |
|
Mathias Gug (mathiaz) |
|
| 2009-05-12 16:16:04 |
Mathias Gug |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527623 |
|
| 2009-05-12 16:16:04 |
Mathias Gug |
bug task added |
|
mysql-dfsg-5.0 (Debian) |
|
| 2009-05-12 16:24:10 |
Bug Watch Updater |
mysql-dfsg-5.0 (Debian): status |
Unknown |
New |
|
| 2009-05-14 09:27:24 |
Martin Pitt |
mysql-dfsg-5.0 (Ubuntu Jaunty): status |
In Progress |
Fix Committed |
|
| 2009-05-14 09:27:31 |
Martin Pitt |
tags |
|
verification-needed |
|
| 2009-06-02 08:08:48 |
Martin Pitt |
tags |
verification-needed |
verification-done |
|
| 2009-06-02 08:09:23 |
Launchpad Janitor |
mysql-dfsg-5.0 (Ubuntu Jaunty): status |
Fix Committed |
Fix Released |
|
| 2009-06-02 08:09:30 |
Martin Pitt |
mysql-dfsg-5.0 (Ubuntu Karmic): importance |
Undecided |
High |
|
| 2009-06-09 10:17:00 |
Stephane Chazelas |
mysql-dfsg-5.0 (Ubuntu Jaunty): status |
Fix Released |
Incomplete |
|
| 2009-06-19 21:24:09 |
Mathias Gug |
mysql-dfsg-5.0 (Ubuntu Karmic): status |
In Progress |
Triaged |
|
| 2009-06-19 21:40:10 |
Mathias Gug |
mysql-dfsg-5.0 (Ubuntu Jaunty): importance |
Undecided |
Medium |
|
| 2009-06-26 14:33:41 |
Mathias Gug |
mysql-dfsg-5.0 (Ubuntu Jaunty): status |
Incomplete |
Fix Released |
|
| 2009-07-10 23:56:58 |
Mathias Gug |
mysql-dfsg-5.0 (Ubuntu Karmic): status |
Triaged |
In Progress |
|
| 2009-07-11 00:15:07 |
Launchpad Janitor |
mysql-dfsg-5.0 (Ubuntu Karmic): status |
In Progress |
Fix Released |
|
| 2009-07-11 00:15:07 |
Launchpad Janitor |
bug watch added |
|
http://bugs.mysql.com/bug.php?id=23921 |
|
| 2009-08-09 05:50:38 |
jflash |
mysql-dfsg-5.0 (Ubuntu Jaunty): status |
Fix Released |
Fix Committed |
|
| 2009-08-09 15:09:36 |
Steve Langasek |
mysql-dfsg-5.0 (Ubuntu Jaunty): status |
Fix Committed |
Fix Released |
|
| 2009-08-10 08:11:08 |
Mario Limonciello |
mythbuntu: status |
Triaged |
Fix Released |
|
| 2009-08-11 13:54:07 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic/mysql-dfsg-5.0 |
|
| 2009-08-11 14:02:08 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/jaunty-updates/mysql-dfsg-5.0 |
|
| 2009-10-07 23:11:12 |
Bug Watch Updater |
mysql-dfsg-5.0 (Debian): status |
New |
Confirmed |
|
