Mysql can't be started (start job failed to start error)

Type df -h to check the free of your disk.

If your disk is full, the mysql cannot start

Type df -h to check the free of your disk.

If your disk is full, the mysql cannot start

Type df -h to check the free of your disk.

If your disk is full, the mysql cannot start

hi, for me it’s doesn’t work.

see:

my mysql can’t restart .

i saw my /var/log/mysql/error.log and there is this error: 2017-12-03T09:39:52.142121Z 459 [Warning] IP address ‘168.1.128.53’ has been resolved to the host name ‘35.80.01a8.ip4.static.sl-reverse.com’, which resembles IPv4-address itself. 2017-12-03T10:59:19.141618Z 460 [Warning] IP address ‘27.223.28.120’ could not be resolved: Name or service not known 2017-12-03T10:59:19.305963Z 460 [Note] Access denied for user ‘mysql’@‘27.223.28.120’ (using password: NO) 2017-12-03T10:59:19.797301Z 461 [Note] Access denied for user ‘mysql’@‘27.223.28.120’ (using password: YES) 2017-12-03T10:59:28.499946Z 462 [Note] Access denied for user ‘mysql’@‘27.223.28.120’ (using password: YES) 2017-12-03T10:59:30.009678Z 463 [Note] Access denied for user ‘mysql’@‘27.223.28.120’ (using password: YES) 2017-12-03T10:59:30.503099Z 464 [Note] Access denied for user ‘mysql’@‘27.223.28.120’ (using password: YES) 2017-12-03T17:20:15.641002Z 467 [Warning] Host name ‘207-226-143-218.static.pccwglobal.net’ could not be resolved: Name or service not known 2017-12-03T17:20:16.949527Z 468 [ERROR] InnoDB: Table mysql.innodb_table_stats not found.

i don’t know what is the problem !

help me

that’s helpful :)

have you tried turning it off then on again.

I had the same issue.

I checked the log with

less /var/log/mysql/error.log

At the bottom of the log I found this

161212  6:30:06  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: trying to add tablespace 278 of name './gseworldfilm/wp_wfHoover.ibd'
InnoDB: to the tablespace memory cache, but tablespace
InnoDB: 278 of name './budget_bumps/wp_wfBadLeechers.ibd' already exists in the tablespace
InnoDB: memory cache!

I moved the “/var/lib/mysql/budget_bumps/wp_wfBadLeechers.ibd” file to “/var/lib/mysql/budget_bumps”

mv /var/lib/mysql/budget_bumps/wp_wfBadLeechers.ibd /var/lib/mysql/ 

I ran a check and repair to the db

 mysqlcheck -c -uroot  --all-databases
 mysqlcheck -o -uroot  --all-databases
 mysqlcheck -r  -uroot  --all-databases

Then I ran the mysql

service mysql start 

Everything is running fine noe

I suddenly started having issues with mysql failing and not starting, and was seeing log entries like: $ dmesg | grep mysql [ 6.208963] type=1400 audit(1477060722.802:22): apparmor=“STATUS” operation=“profile_load” profile=“unconfined” name=“/usr/sbin/mysqld” pid=1183 comm=“apparmor_parser” [ 6.709699] type=1400 audit(1477060723.302:25): apparmor=“STATUS” operation=“profile_replace” profile=“unconfined” name=“/usr/sbin/mysqld” pid=1299 comm=“apparmor_parser” [ 6.817714] init: mysql main process (1320) terminated with status 1 [ 6.817729] init: mysql main process ended, respawning [ 7.803123] init: mysql post-start process (1321) terminated with status 1 [ 7.869587] init: mysql main process (1371) terminated with status 1 [ 7.869603] init: mysql main process ended, respawning [ 8.856238] init: mysql post-start process (1373) terminated with status 1 [ 8.906902] init: mysql main process (1510) terminated with status 1 [ 8.906917] init: mysql respawning too fast, stopped

I started looking for reasons why apparmor might have gotten involved (found this: http://askubuntu.com/questions/127264/cant-start-mysql-mysql-respawning-too-fast-stopped)

When I started trying to run apt-get commands, THOSE were failing, complaining about tmp files.

Which reminded me that on my web server I’d had previous issues because I was mounting /tmp as a tmpfs and it was (for unknown reasons) getting remounted as read-only, which caused this whole cascade of issues.

SO, if you mount /tmp with tmpfs and other flags for security purposes, it just might be causing other issues as well.