Yet another MySQL vs. AppArmor barf

I freaking hate AppArmor! Of course only because I don't want to be bothered when an update makes a mess of it - I really don't know how it works but I don't want to need to know either. Some months ago I tried out Logitech Media Server on my box, and it screwed it up big time. Now it seems there has been an update, so it doesn't accept symlinks anymore. It seems logical that it shouldn't, but Ubuntu could have done a better job fixing it - or maybe it's because I had already edited it, that it didn't get updated..? A search lead me to an issue at Launchpad about it, but I've only skimmed through it. Anyways, today when I rebooted MySQL wouldn't run and /var/log/syslog was filled with entries like this:
Mar 30 11:55:31 tanghus kernel: [ 1309.198481] type=1400 audit(1333101331.343:97): apparmor="DENIED" operation="mknod" parent=1 profile="/usr/sbin/mysqld" name="/run/mysqld/mysqld.sock" pid=7192 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=114 ouid=114
Mar 30 11:55:36 tanghus kernel: [ 1314.463559] init: mysql main process (7192) terminated with status 1
Mar 30 11:55:36 tanghus kernel: [ 1314.463606] init: mysql main process ended, respawning
Mar 30 11:56:01 tanghus kernel: [ 1339.105333] init: mysql post-start process (7194) terminated with status 1
Mar 30 11:56:01 tanghus kernel: [ 1339.111425] type=1400 audit(1333101361.335:98): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=7291 comm="apparmor_parser"
To fix it edit /etc/apparmor.d/usr.sbin.mysqld and replace the lines: /var/run/mysqld/mysqld.pid w, /var/run/mysqld/mysqld.sock w, with: /run/mysqld/mysqld.pid w, /run/mysqld/mysqld.sock w, and restart mysql by running sudo service mysql restart - if it doesn't respawn by itself. AppArmor should automagically refresh from the change of it's configuration file, otherwise run sudo service apparmor restart.

flattr this!

Kernel hell

Ever since I finally installed Kubuntu 10.4 Lucid Lynx I have had kernel crashes at least once a day, sometimes up to ten times a day. It's very frustrating and effectively breaks your workflow to put it mildly. I could easily come up with other, more harsh ways to describe the situation ;-)

I have tried a variety of different kernels:

  • 2.6.35-020635rc1-generic
  • 2.6.34-020634-generic
  • 2.6.32-23-generic
  • 2.6.32-22-generic
  • 2.6.32-22-generic
  • 2.6.32-21-generic

Some I can (sometimes) boot and let me work for 0-20 hours, others never reaches the login screen or goes into an infinite reboot loop.

If anyone experience the same or similar the relevant bug report is at https://bugs.launchpad.net/bugs/585734 and it doesn't look promising. So now I have come to the conclusion that I need to install a pre-Lucid kernel and see if I can get it running. It will probably degrade X performance (if it even runs) and crash other applications but I'd rather live with that than having to reboot all the time.

Is it at all a viable solution to install a pre-Lucid kernel and if so how should it be done. What about graphic drivers (aren't they somehow partly kernel modules now?).

flattr this!

Posted in KDE, Personal. Tags: , , . No Comments »