mysql-server won't start

Bug #1579489 reported by vimo
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mysql-5.7 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After upgrading to xubuntu 16.04, mysql won't start neither at boot nor manually.
I tried to purge and reinstall mysql-server and mysql-common several times without success.

When I try to start mysql manually with "sudo start mysql" I got the message "Job failed to start".
Reconfiguring with "sudo dpkg-reconfigure mysql" produce no output (so it should be ok) but trying to start mysql again produce the same error message as above.

The problem is temporarily solved with "sudo dpkg-reconfigure mysql-server-5.7" until the next boot when the issue comes again.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mysql-server 5.7.12-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun May 8 11:29:26 2016
Logs.var.log.daemon.log:

MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: False
PackageArchitecture: all
SourcePackage: mysql-5.7
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
vimo (vimot2) wrote :
Revision history for this message
Lars Tangvald (lars-tangvald) wrote :

Hi,

When you get the failure from running «sudo start mysql», could you see if /var/log/mysql/error.log contains any more information than what's uploaded here? I can't see anything that would explain your issue.

Revision history for this message
Robie Basak (racb) wrote :

Marking as Incomplete as there isn't enough here that a developer can use to confirm that there is a bug here. Please change the status back to New if you provide any further information.

Changed in mysql-5.7 (Ubuntu):
status: New → Incomplete
Revision history for this message
vimo (vimot2) wrote :

Here is error.log if it could help

Revision history for this message
Lars Tangvald (lars-tangvald) wrote :

Thanks.

"2016-05-09T07:14:51.079020Z 10 [ERROR] /usr/sbin/mysqld: Table './smatool/DayData' is marked as crashed and should be repaired"

Is the only thing that's different. If this shows up in the log every time it fails, could you check the timestamp of /var/lib/mysql/smatool/DayData.frm when it's working, then reboot and see if the timestamp has changed?

Revision history for this message
Lars Tangvald (lars-tangvald) wrote :

Just to clarify, if this error keeps showing up and the timestamp is changed, it might be that something besides the server is changing the file

Revision history for this message
vimo (vimot2) wrote :

Thank you Lars.
The table .smatool/DayData is part of a databese named smatool tha was updated every boot bya a cron command.
I removed that cron command and the issue still persists.
I tried to change the root password of mysql.
Tried to purge everything related to mysql.
Tried to install mysql-server-5.6.
Nothing of these actions worked.
Now I reinstalled mysql-server-5.7 again and it is all the same as before. No mysql start at boot, no start with 'sudo start mysql' ("Job failed to start"). It starts only with the command 'sudo dpkg-reconfigure mysql-server-5.7'.
After that everything works, included the updating of my smatool db.

Only one change: the file /var/log/mysql/error.log disappear.

Maybe a future update of mysql or a complete reinstall of Xubuntu (but I have no time to do this right now) could solve the problem.

Thanks for the time you dedicated to me.

Revision history for this message
vimo (vimot2) wrote :

Do I have to change the bug status?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]

Changed in mysql-5.7 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.