@Robie,
This has occurred since the package has landed, after a reboot the
following occurs:
» 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 Tue 2015-03-24 18:23:10 SAST; 7min ago
Main PID: 16722 (code=exited, status=0/SUCCESS); : 16723
(mysql-systemd-s)
CGroup: /system.slice/mysql.service
└─control
├─16723 /bin/bash /usr/share/mysql/mysql-systemd-start post
└─20513 sleep 1
Mar 24 18:23:10 host systemd[1]: mysql.service holdoff time over, scheduling
restart.
Mar 24 18:23:10 host systemd[1]: Starting MySQL Community Server...
Mar 24 18:23:10 host mysqld_safe[16722]: 150324 18:23:10 mysqld_safe Can't log
to error log and syslog at the same time. Remove all --log-error configuration
options for --syslog to take effect.
Mar 24 18:23:10 host mysqld_safe[16722]: 150324 18:23:10 mysqld_safe Logging to
'/var/log/mysql/error.log'.
Mar 24 18:23:10 host mysqld_safe[16722]: mkdir: cannot create directory
‘/var/run/mysqld’: Permission denied
Mar 24 18:23:10 host mysqld_safe[16722]: chown: cannot access
‘/var/run/mysqld’: No such file or directory
Mar 24 18:23:10 host mysqld_safe[16722]: chmod: cannot access
‘/var/run/mysqld’: No such file or directory
Mar 24 18:23:10 host mysqld_safe[16722]: 150324 18:23:10 mysqld_safe Starting
mysqld daemon with databases from /var/lib/mysql
Running the workaround in comment #6 seems start the service correctly,
however it will have to be re-applied after a reboot as pointed out in
comment #7.
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset:
enabled)
Active: active (running) since Tue 2015-03-24 18:33:48 SAST; 2min 38s ago
Process: 22041 ExecStartPost=/usr/share/mysql/mysql-systemd-start post
(code=exited, status=0/SUCCESS)
Process: 22038 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
(code=exited, status=0/SUCCESS)
Main PID: 22040 (mysqld_safe)
CGroup: /system.slice/mysql.service
├─22040 /bin/sh /usr/bin/mysqld_safe
└─22401 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql
--plugin-dir=/usr/lib/mysql/plugin --log-error=/var/log/mysql/error.log
--pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock
--port=3306
Mar 24 18:33:47 host systemd[1]: Starting MySQL Community Server...
Mar 24 18:33:47 host mysqld_safe[22040]: 150324 18:33:47 mysqld_safe Can't log
to error log and syslog at the same time. Remove all --log-error configuration
options for --syslog to take effect.
Mar 24 18:33:47 host mysqld_safe[22040]: 150324 18:33:47 mysqld_safe Logging to
'/var/log/mysql/error.log'.
Mar 24 18:33:47 host mysqld_safe[22040]: 150324 18:33:47 mysqld_safe Starting
mysqld daemon with databases from /var/lib/mysql
Mar 24 18:33:48 host systemd[1]: Started MySQL Community Server.
Users unfamiliar with problem, might try do a remove and install, but my
oh my is that another story. If this should be filed as a seperate bug,
let me know I'll be glad to do so.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421303
Title:
mysql does not import apparmor profile correctly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1421303/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
