Eric at Lucii.org on 15 Mar 2011 10:47:08 -0700 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
[PLUG] MySQL server cyclic restarts |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm developing a web app on a Linode VM running a LAMP stack. When I look at the syslog I see this bizarre behavior repeated about every 100 seconds day and night: Mar 15 17:28:50 li282 init: mysql main process (4210) terminated with status 1 Mar 15 17:28:50 li282 init: mysql main process ended, respawning Mar 15 17:28:50 li282 /etc/mysql/debian-start[4304]: Upgrading MySQL tables if necessary. Mar 15 17:28:50 li282 /etc/mysql/debian-start[4307]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Mar 15 17:28:50 li282 /etc/mysql/debian-start[4307]: Looking for 'mysql' as: /usr/bin/mysql Mar 15 17:28:50 li282 /etc/mysql/debian-start[4307]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Mar 15 17:28:50 li282 /etc/mysql/debian-start[4307]: This installation of MySQL is already upgraded to 5.1.41, use --force if you still need to run mysql_upgrade Mar 15 17:28:50 li282 /etc/mysql/debian-start[4318]: Checking for insecure root accounts. Mar 15 17:28:50 li282 /etc/mysql/debian-start[4322]: Triggering myisam-recover for all MyISAM tables Mar 15 17:30:30 li282 init: mysql main process (4298) terminated with status 1 Mar 15 17:30:30 li282 init: mysql main process ended, respawning Mar 15 17:30:30 li282 /etc/mysql/debian-start[4371]: Upgrading MySQL tables if necessary. Mar 15 17:30:30 li282 /etc/mysql/debian-start[4374]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Mar 15 17:30:30 li282 /etc/mysql/debian-start[4374]: Looking for 'mysql' as: /usr/bin/mysql Mar 15 17:30:30 li282 /etc/mysql/debian-start[4374]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Mar 15 17:30:30 li282 /etc/mysql/debian-start[4374]: This installation of MySQL is already upgraded to 5.1.41, use --force if you still need to run mysql_upgrade Mar 15 17:30:30 li282 /etc/mysql/debian-start[4381]: Checking for insecure root accounts. Mar 15 17:30:30 li282 /etc/mysql/debian-start[4389]: Triggering myisam-recover for all MyISAM tables The MySQL log and error log are empty (clearly not enough 'setting' on that!) I tried google but did not find anything that relates to this. Before I go cranking up logging levels and start breaking things... does this look familiar to anyone? Any hints of places to start? I think of starting at /etc/inittab but, surprise surprise, Ubuntu does not have an inittab. Sigh. Thanks, Eric PS apologies for html email but wide log files come across much better for me without the 80 char line wrap and I hope they do for you too. - -- # Eric Lucas # # "Oh, I have slipped the surly bond of earth # And danced the skies on laughter-silvered wings... # -- John Gillespie Magee Jr -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1/ph0ACgkQ2sGpvXQrZ/4CQwCfUT1uSjMCyoYGXZWVBjKazHox 0bgAoJlFa9xQ4JDNDxhwOkpn3an3fykh =8Ofh -----END PGP SIGNATURE----- ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug