[Bug 719388] Re: semop failed for cookie 0xd4d09ef: incorrect semaphore state during luksOpen
I got this when executing: zeratul@antioch:~$ sudo cryptsetup luksOpen /dev/md0 raid Enter passphrase for /dev/md0: semid 5111810: semop failed for cookie 0xd4dca3f: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223201855 (0xd4dca3f) to initialize waiting for incoming notifications. System is Kubuntu 11.04, 2.6.38-10-generic-pae, i686. Didn't occur in previous releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/719388 Title: semop failed for cookie 0xd4d09ef: incorrect semaphore state during luksOpen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/719388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667986] Re: Disk image type defaults to raw since 0.7.5-5ubuntu27.5
As this information is not that easy to come by, here is a sample code for domain xml file. You have to specify driver tag with attribute type set to the image type. (Or alternatively, as described in security notice, adjust the 'allow_disk_format_probing' option in /etc/libvirt/qemu.conf) Example: disk type='file' device='disk' driver type='qcow2'/ source file='myDisk.qcow2'/ ... /disk -- Disk image type defaults to raw since 0.7.5-5ubuntu27.5 https://bugs.launchpad.net/bugs/667986 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 667986] Re: Disk image type defaults to raw since 0.7.5-5ubuntu27.5
As this information is not that easy to come by, here is a sample code for domain xml file. You have to specify driver tag with attribute type set to the image type. (Or alternatively, as described in security notice, adjust the 'allow_disk_format_probing' option in /etc/libvirt/qemu.conf) Example: disk type='file' device='disk' driver type='qcow2'/ source file='myDisk.qcow2'/ ... /disk -- Disk image type defaults to raw since 0.7.5-5ubuntu27.5 https://bugs.launchpad.net/bugs/667986 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 448656] Re: CPU information is inaccessible for MySQL
That is upgrade related issue as well, usually they both come hand in hand (adding apparmor permission and commenting skip-bdb). I was referring to this in my earlier post. Glad you got it working now. -- CPU information is inaccessible for MySQL https://bugs.launchpad.net/bugs/448656 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 448656] Re: CPU information is inaccessible for MySQL
That is upgrade related issue as well, usually they both come hand in hand (adding apparmor permission and commenting skip-bdb). I was referring to this in my earlier post. Glad you got it working now. -- CPU information is inaccessible for MySQL https://bugs.launchpad.net/bugs/448656 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 448656] Re: CPU information is inaccessible for MySQL
Suggestion: Add line /sys/devices/system/* r, to your /etc/apparmor.d/usr.sbin.mysqld Then check your syslog/mysql-log again if there is something else e.g. i personnaly had problem with package in kubuntu. After adding rule I saw error in log complaining about bdb something. I opened /etc/mysql/my.cnf and commented the line with bdb option and it runs now. HTH, Regards, Marek -- CPU information is inaccessible for MySQL https://bugs.launchpad.net/bugs/448656 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 448656] Re: CPU information is inaccessible for MySQL
Disabling AppArmor may not be desirable solution, but as you see there could be error in apparmor's mysql configuration and then in configuration of mysql itself. When you disable apparmor for debugging you are one step ahead because mysql now actually produces some logs why it can't start (eg in my case some option that just needed to be commented. I doubt that mysqld would run with proper mysql conf and misconfigured apparmor). -- CPU information is inaccessible for MySQL https://bugs.launchpad.net/bugs/448656 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 448656] Re: CPU information is inaccessible for MySQL
Suggestion: Add line /sys/devices/system/* r, to your /etc/apparmor.d/usr.sbin.mysqld Then check your syslog/mysql-log again if there is something else e.g. i personnaly had problem with package in kubuntu. After adding rule I saw error in log complaining about bdb something. I opened /etc/mysql/my.cnf and commented the line with bdb option and it runs now. HTH, Regards, Marek -- CPU information is inaccessible for MySQL https://bugs.launchpad.net/bugs/448656 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 448656] Re: CPU information is inaccessible for MySQL
Disabling AppArmor may not be desirable solution, but as you see there could be error in apparmor's mysql configuration and then in configuration of mysql itself. When you disable apparmor for debugging you are one step ahead because mysql now actually produces some logs why it can't start (eg in my case some option that just needed to be commented. I doubt that mysqld would run with proper mysql conf and misconfigured apparmor). -- CPU information is inaccessible for MySQL https://bugs.launchpad.net/bugs/448656 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
