Ivan, can you also add the following to your apparmor profile, and
restart it:
network inet stream,
** Changed in: mysql-dfsg-5.0 (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
--
AppArmor profile included doesn't allow mysql to bind to socket
https://bugs.launchpad.net/bu
I have the same problem on Ubuntu 8.10, added the extra option to mysql
apparmor profile, but still the problem persists if I deactivate
apparmor mysql gets to starts, otherwise it fails
The only message that appears during the restart of mysql is the
following:
Mar 19 14:22:55 zeus kernel: [150
Rather than removing apparmor, try adding to mysql's apparmor profile in
/etc/apparmor.d/usr.sbin.mysqld:
/var/run/samba/winbindd_privileged/pipe rw,
Then do:
$ sudo /etc/init.d/apparmor force-reload
$ sudo /etc/init.d/mysql stop
$ sudo /etc/init.d/mysql start
Please report back if this fixes
confirmed on 9.04 alpha 4 (with updates till today)
also mention that I'm running on a 2.6.27-11 kernel, since my Intel
graphics card is not well supported.
mysqld would run well after removing apparmor
--
AppArmor profile included doesn't allow mysql to bind to socket
https://bugs.launchpad.ne
I can confirm this bug occuring with mysql-server-5.0 and apparmor on
Ubuntu 8.04.2. When apparmor was installed, running '/etc/init.d/mysql
start' would give errors. After uninstalling apparmor, mysqld started
successfully.
--
AppArmor profile included doesn't allow mysql to bind to socket
htt
It's a little messy and includes entries after i disabled AppArmor for
MySQL.
If you want i can purge MySQL and reinstall and give you a clean
kern.log...
Dec 10 13:15:20 avebi01 kernel: [ 40.551814] type=1503
audit(1228914920.026:3): operation="socket_create" family="inet"
sock_type="stream"
