Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

It appears that the issue is around the MySQL services starting as I receive the following in my /var/log/syslog when I attempt to restart the mysql service:

Jan 17 08:19:38 blog kernel: [ 1704.003353] type=1400 audit(1389964778.088:23): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=2219 comm="apparmor_parser"
Jan 17 08:19:38 blog kernel: [ 1704.100627] init: mysql main process (2223) terminated with status 1
Jan 17 08:19:38 blog kernel: [ 1704.100649] init: mysql main process ended, respawning
Jan 17 08:19:39 blog kernel: [ 1705.024735] init: mysql post-start process (2224) terminated with status 1
Jan 17 08:19:39 blog kernel: [ 1705.031829] type=1400 audit(1389964779.120:24): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=2262 comm="apparmor_parser"
Jan 17 08:19:39 blog kernel: [ 1705.164003] init: mysql main process (2266) terminated with status 1
Jan 17 08:19:39 blog kernel: [ 1705.164025] init: mysql respawning too fast, stopped

I was browsing the Wordpress site (personal blog) when I received the data base connection error through Apache2. As I was discussing some details outside of the site with a group of folks and I gave the server a reboot while I continued the conversation. I do have automatic security updates enabled. After the reboot, it appears that the MySQL service never restarted.

No changes were made by me to the my.cnf or other configuration files. I do see that it appears the next version of MySQL is being held back, however I do not believe that should be causing this much havoc. Being a VMware VM, I snapshot the system and attempted to push the download through with aptitude to no success.

All the packages on the system except Webmin where installed through the apt-get repositories. No special modification was done to MySQL and a very minimal amount was done to Wordpress (Image upload size change from 2MB to 64MB for example).

I am looking for some suggestions from folks prior to doing a restore type process and attempting to reimport all the necessary details between wordpress and mysql.

Thanks!

share|improve this question

1 Answer 1

It would appear that the ~27MB Wordpress InnoDB became corrupt and stopped the mysql process from loading, even though the logs did not state anything along those lines. After pulling the database files from a backed up version, mysql was able to start.

Off to find out to repair the ibdata/ib_lobfile files. Thanks to those who read.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.