Public bug reported:
Binary package hint: mysql-server-5.0
I upgraded from Dapper Drake ( amd64) to the Edgy Eft for testing on an
SMP Intel Xeon ( em64t ). During the course of the upgrade the mysql
package could not successfully configure itself. Whenever the
installation scripts tried launching mysqld, it would die immedietly. If
I removed the contents of /var/lib/mysql, the daemon would come up and
initiliaze itself, but it would always fail to start up if
/var/lib/mysql was populated.
The following error was printed to the system logs:
Oct 17 14:31:27 tinman mysqld_safe[30035]: started
Oct 17 14:31:27 tinman mysqld[30038]: mysqld got signal 4;
Oct 17 14:31:27 tinman mysqld[30038]: This could be because you hit a bug. It
is also possible that this binary
Oct 17 14:31:27 tinman mysqld[30038]: or one of the libraries it was linked
against is corrupt, improperly built,
Oct 17 14:31:27 tinman mysqld[30038]: or misconfigured. This error can also be
caused by malfunctioning hardware.
Oct 17 14:31:27 tinman mysqld[30038]: We will try our best to scrape up some
info that will hopefully help diagnose
Oct 17 14:31:27 tinman mysqld[30038]: the problem, but since we have already
crashed, something is definitely wrong
Oct 17 14:31:27 tinman mysqld[30038]: and this may fail.
Oct 17 14:31:27 tinman mysqld[30038]:
Oct 17 14:31:27 tinman mysqld[30038]: key_buffer_size=0
Oct 17 14:31:27 tinman mysqld[30038]: read_buffer_size=131072
Oct 17 14:31:27 tinman mysqld[30038]: max_used_connections=0
Oct 17 14:31:27 tinman mysqld[30038]: max_connections=100
Oct 17 14:31:27 tinman mysqld[30038]: threads_connected=0
Oct 17 14:31:27 tinman mysqld[30038]: It is possible that mysqld could use up to
Oct 17 14:31:27 tinman mysqld[30038]: key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_connections = 217599 K
Oct 17 14:31:27 tinman mysqld[30038]: bytes of memory
Oct 17 14:31:27 tinman mysqld[30038]: Hope that's ok; if not, decrease some
variables in the equation.
Oct 17 14:31:27 tinman mysqld[30038]:
Oct 17 14:31:27 tinman mysqld_safe[30045]: ended
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: 0 processes alive and
'/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: ^G/usr/bin/mysqladmin: connect
to server at 'localhost' failed
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: error: 'Can't connect to local
MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: Check that mysqld is running
and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]:
Oct 17 14:31:41 tinman /etc/init.d/mysql[30322]:
/etc/mysql/debian-log-rotate.conf is obsolete, see
/usr/share/doc/mysql-server-5.0/NEWS.Debian.gz
I've since downgraded the mysql-server-5.0 package to the
-5.0_5.0.22-0ubuntu6.06.2 and it started up properly.
** Affects: mysql-dfsg-5.0 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
mysql-server-5.0 5.0.24a-9 receives signal 4 on startup
https://launchpad.net/bugs/66702
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
