Mark Lanctot;299726 Wrote: > I've followed the instructions around here and things still aren't > working properly for me using the latest 7.1. I get: > > > Code: -------------------- > > Reloading AppArmor profiles AppArmor parser error in /etc/apparmor.d/usr.bin.mysqld at line 3: syntax error, unexpected TOK_MODE, expecting TOK_OPEN > Profile /etc/apparmor.d/usr.bin.mysqld failed to load > Skipping profile /etc/apparmor.d/usr.bin.mysqld~ > Warning: found /etc/apparmor.d/force-complain/usr.sbin.mysqld, forcing complain mode > : Warning. > AppArmor parser error in /etc/apparmor.d/usr.bin.mysqld at line 3: syntax error, unexpected TOK_MODE, expecting TOK_OPEN > > > Starting SqueezeCenter Audio Server. -------------------- > > > > ...but it doesn't actually start, I get a page not found. A reboot > brings the page up though - not sure if it's restarting AppArmor or > SqueezeCenter that does the trick. > > The error message seems to imply some sort of error in usr.bin.mysqld > although I copied it character-for-character from the directions here > and edited using nano. On first install of a recent 7.1 this file > didn't exist so I had to create it.
I presume you are using ubuntu 8.04 Hardy. I haven't tried 7.1 but stayed with 7.0.1, although I think they are the same in respect of apparmor. It seems you may have a corrupt /etc/apparmor.d/usr.sbin.mysqld. Squeezecenter appends a number of lines to this file to accommodate squeezecenter. I also note that you have Mysqld in complain mode. This is a useful help page: https://help.ubuntu.com/community/AppArmor and should help a greater understanding of apparmor. This will guide on how to manipulate apparmor profiles. The apparmor profiles are in /etc/apparmor.d. So that you can backtrack, I have attached the original /etc/apparmor.d/usr.sbin.mysql (.txt added to validate for this forum) Please feel free to copy it into your /etc/apparmor.d folder. You could safely delete any previous usr.sbin.mysql files. Squeezecenter will add any necessary lines to this file when you next do an update. If SC doesn't start then use Code: -------------------- #sudo service apparmor stop -------------------- wait 5 secs for SC to start then start apparmor Code: -------------------- #sudo service apparmor start -------------------- SC should then run without problem until the next update. As you may see from my previous post, I have disabled the mysql apparmor profile for now. +-------------------------------------------------------------------+ |Filename: usr.sbin.mysqld.txt | |Download: http://forums.slimdevices.com/attachment.php?attachmentid=5040| +-------------------------------------------------------------------+ -- Ramage T5500 1.6GHz, SC 7.0.1-18576 Win Vista, Alien 2.0 P4 2.6GHz, SC 7.0.1-17976 WinXP, Alien 2.0 P2 266MHz, ClarkConnect 4.1, SC 7.0.1-19325, Alien 2.0 AMD64x2 ubuntu 8.04, SC 7.0.1~19352, Alien 2.0 ------------------------------------------------------------------------ Ramage's Profile: http://forums.slimdevices.com/member.php?userid=5343 View this thread: http://forums.slimdevices.com/showthread.php?t=46614 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
