[Bug 1435709] [NEW] mysql.service fail to start after upgrade to mysql-server.5.6
Luca D'Isanto
lukadisanto at gmail.com
Tue Mar 24 08:05:17 UTC 2015
Public bug reported:
After upgrade to mysql-server-5.6 mysql.service fail to start (after reboot).
Here the systemctl status mysql.service:
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
Active: activating (start-post) since mar 2015-03-24 08:41:00 CET; 25s ago
Process: 951 ExecStart=/usr/bin/mysqld_safe (code=exited, status=0/SUCCESS)
Process: 943 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
Main PID: 951 (code=exited, status=0/SUCCESS); : 952 (mysql-systemd-s)
CGroup: /system.slice/mysql.service
└─control
├─ 952 /bin/bash /usr/share/mysql/mysql-systemd-start post
└─2601 sleep 1
mar 24 08:41:00 luca-k53sd systemd[1]: Starting MySQL Community Server...
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: 150324 08:41:00 mysqld_safe Can't log to error log and syslog at the same time. Remove all --log-err...e effect.
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: 150324 08:41:00 mysqld_safe Logging to '/var/log/mysql/error.log'.
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: mkdir: impossibile creare la directory "/var/run/mysqld": Permesso negato
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: chown: impossibile accedere a "/var/run/mysqld": File o directory non esistente
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: chmod: impossibile accedere a "/var/run/mysqld": File o directory non esistente
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: 150324 08:41:00 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Hint: Some lines were ellipsized, use -l to show in full.
** Affects: mysql-5.6 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mysql mysql-server systemd vivid
** Description changed:
After upgrade to mysql-server-5.6 mysql.service fail to start (after reboot).
Here the systemctl status mysql.service:
-
+
● mysql.service - MySQL Community Server
- Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
- Active: activating (start-post) since mar 2015-03-24 08:41:00 CET; 25s ago
- Process: 951 ExecStart=/usr/bin/mysqld_safe (code=exited, status=0/SUCCESS)
- Process: 943 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
- Main PID: 951 (code=exited, status=0/SUCCESS); : 952 (mysql-systemd-s)
- CGroup: /system.slice/mysql.service
- └─control
- ├─ 952 /bin/bash /usr/share/mysql/mysql-systemd-start post
- └─2601 sleep 1
+ Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
+ Active: activating (start-post) since mar 2015-03-24 08:41:00 CET; 25s ago
+ Process: 951 ExecStart=/usr/bin/mysqld_safe (code=exited, status=0/SUCCESS)
+ Process: 943 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
+ Main PID: 951 (code=exited, status=0/SUCCESS); : 952 (mysql-systemd-s)
+ CGroup: /system.slice/mysql.service
+ └─control
+ ├─ 952 /bin/bash /usr/share/mysql/mysql-systemd-start post
+ └─2601 sleep 1
mar 24 08:41:00 luca-k53sd systemd[1]: Starting MySQL Community Server...
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: 150324 08:41:00 mysqld_safe Can't log to error log and syslog at the same time. Remove all --log-err...e effect.
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: 150324 08:41:00 mysqld_safe Logging to '/var/log/mysql/error.log'.
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: mkdir: impossibile creare la directory "/var/run/mysqld": Permesso negato
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: chown: impossibile accedere a "/var/run/mysqld": File o directory non esistente
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: chmod: impossibile accedere a "/var/run/mysqld": File o directory non esistente
mar 24 08:41:00 luca-k53sd mysqld_safe[951]: 150324 08:41:00 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Hint: Some lines were ellipsized, use -l to show in full.
- ldisanto at luca-k53sd:~$ sudo systemctl reload mysql.service
- Failed to reload mysql.service: Job type reload is not applicable for unit mysql.service.
- ldisanto at luca-k53sd:~$ sudo systemctl start mysql.service
- ^Cldisanto at luca-k53sd:~$ ubuntu-bug
- ldisanto at luca-k53sd:~$ ubuntu-bug mysql-server
- QCoreApplication::postEvent: Unexpected null receiver
-
- ProblemType: Bug
- DistroRelease: Ubuntu 15.04
- Package: mysql-server 5.6.23-1~exp1~ubuntu4
- ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
- Uname: Linux 3.19.0-10-generic x86_64
- ApportVersion: 2.16.2-0ubuntu4
- Architecture: amd64
- CurrentDesktop: KDE
- Date: Tue Mar 24 09:00:40 2015
- InstallationDate: Installed on 2015-03-18 (5 days ago)
- InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150318)
- PackageArchitecture: all
- SourcePackage: mysql-5.6
- UpgradeStatus: No upgrade log present (probably fresh install)
** Tags added: mysql mysql-server systemd
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1435709
Title:
mysql.service fail to start after upgrade to mysql-server.5.6
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1435709/+subscriptions
More information about the Ubuntu-server-bugs
mailing list