Error message flood when enabling events in Ubuntu

Bug #599790 reported by Sander Johansen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mysql-dfsg-5.1 (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

When enabling events with "SET GLOBAL event_scheduler = ON; " I get a flood of error messages when I stop mysql.

Here is what's happening:
/etc/init.d/mysql restart
 * Stopping MySQL database server mysqld
ERROR 1053 (08S01) at line 1: Server shutdown in progress
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
.........
.....
...
To stop it, I have to do "killall -9 xargs" from another shell.

This is happening on Ubuntu 9.10 with mysql 5.1.37-1ubuntu5.4

I managed to enable event scheduler in my.cnf with setting event_scheduler = 1 . Then the bug permanently will occour every time I stop mysql.

I've heard that the mysql init script is diffrent from the ubuntu/debian version. That might be the reason of this bug.

ProblemType: Bug
Architecture: amd64
Date: Tue Jun 29 13:02:34 2010
DistroRelease: Ubuntu 9.10
Logs.var.log.kern.log:

MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: ['Provisioning', 'debian-5.1.flag', 'mysql_upgrade_info', 'DB30000693', 'ib_logfile0', 'DB13453812', 'lost@002bfound', 'mysql', 'DB13453817', 'ibdata1', 'ib_logfile1', 'test']
Package: mysql-server-5.1 5.1.37-1ubuntu5.4
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-server
SourcePackage: mysql-dfsg-5.1
Uname: Linux 2.6.31-19-server x86_64
mtime.conffile..etc.apparmor.d.usr.sbin.mysqld: 2010-06-28T16:36:44.028478

Revision history for this message
Sander Johansen (sanderm) wrote :
Revision history for this message
Thierry Carrez (ttx) wrote :

Any chance you could confirm if this error is still present in 10.04 LTS ?

Changed in mysql-dfsg-5.1 (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Sander Johansen (sanderm) wrote :

This bug is not present in 10.04 LTS.

But I found another bug after I upgraded.

All spaces was stored as \040 in ~/.mysql_history on 9.10. But in 10.04 they use normal spaces.

Means all my previous history have lots of \040 inside it, so I get an error when executing those commands.

Revision history for this message
Chuck Short (zulcss) wrote :

Can you open another bug about this then? Im closing the original bug.

chuck

Changed in mysql-dfsg-5.1 (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.