Menu
I recently discovered the following error in a log
Oct 14 10:21:43 squire-labs kernel: [4186256.684193] init: mysql main process (16331) terminated with status 1
Oct 14 10:21:43 squire-labs kernel: [4186256.684215] init: mysql main process ended, respawning
Oct 14 10:21:44 squire-labs kernel: [4186257.394474] type=1400 audit(1381738904.046:23): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=28201 comm="apparmor_parser"
Oct 14 10:21:47 squire-labs /etc/mysql/debian-start[28254]: Upgrading MySQL tables if necessary.
Oct 14 10:21:47 squire-labs /etc/mysql/debian-start[28257]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Oct 14 10:21:47 squire-labs /etc/mysql/debian-start[28257]: Looking for 'mysql' as: /usr/bin/mysql
Oct 14 10:21:47 squire-labs /etc/mysql/debian-start[28257]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Oct 14 10:21:47 squire-labs /etc/mysql/debian-start[28257]: This installation of MySQL is already upgraded to 5.5.29, use --force if you still need to run mysql_upgrade
Oct 14 10:21:47 squire-labs /etc/mysql/debian-start[28269]: Checking for insecure root accounts.
Oct 14 10:21:47 squire-labs /etc/mysql/debian-start[28274]: Triggering myisam-recover for all MyISAM tables
This happens often (at least 4 times a minute). I'm really not sure what might be causing this issue. Mysql is running on a production server, with enough disk space and memory. Up until yesterday we've never had any problems.
Any help will be much appreciated.
973
In Ubuntu 18.04, sudo systemctl disable mysql will prevent mysql-server from autostarting on boot.
It turned out that one of my tables in one of the dbs was corrupted. This article proved to be very useful.
In the end, I simply made a mysqldump of the database and restored the dump to a new database. That solved the problem.
157
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
