[Bug 1103656] Re: Update Precise drbd8-utils to 8.3.13 for the 12.04.2 release
I'm not the reporter but I am a daily user of DRBD on precise. If someone is running the old kernel then they should use the matching older version of drbd8-utils. So if the module in the kernel is 8.3.11 then the tools should be also or if the module is 8.3.13 then the tools should be 8.3.13 also. I'm a total newbie about packaging but is there a way to make it so drbd8-utils version 8.3.11 is required to be upgraded if you go to kernel = 3.5 and drbd is installed? And if you install/downgrade to kernel 3.5 drbd8-utils must be downgraded to 8.3.11 at the same time if installed - through dependencies or something? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1103656 Title: Update Precise drbd8-utils to 8.3.13 for the 12.04.2 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1103656/+subscriptions -- 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 966039] Re: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update()
Any chance of a patch to at least quiet this down? Or some additional info we can provide to try to fix the problem?? These are writing to log every 15 seconds: Dec 25 23:25:27 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:25:42 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:25:57 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:26:12 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:26:27 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:26:42 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:26:57 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Dec 25 23:27:12 Condor snmpd[3908]: c64 32 bit check failed Dec 25 23:27:27 Condor snmpd[3908]: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() Ubuntu 12.04 Precise with all available updates applied running the latest Lucid kernel: linux-image-2.6.32-45-server 2.6.32-45.101 Linux kernel image for version 2.6.32 on x86_64 snmpd5.4.3~dfsg-2.4ubuntu1.1 SNMP (Simple Network Management Protocol) agents ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/966039 Title: netsnmp_assert 1 == new_val-high failed int64.c:419 netsnmp_c64_check32_and_update() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/966039/+subscriptions -- 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 912254] Re: Please upgrade the drbd module to 8.3.13
No log files available - known issue that was patched in 8.3.13 as noted in comment #3 above. Especially important since the new default scheduler of cfq in Precise is known to cause the bug. ** Changed in: drbd8 (Ubuntu) Status: Triaged = Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/912254 Title: Please upgrade the drbd module to 8.3.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/912254/+subscriptions -- 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 1010602] Re: samba logs are not being reported in logwatch
I will give it a whirl... not sure the exact (best) steps but I assume: Submit a bug against Logwatch at SourceForge.net Follow/answer questions there as needed. If it gets patched then would I need to try to get Debian to pickup the patch before Ubuntu would consider an SRU to 12.04? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+subscriptions -- 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 1010625] Re: named logs are not being reported in logwatch
I will look into it this week and respond accordingly -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010625 Title: named logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010625/+subscriptions -- 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 1010602] Re: samba logs are not being reported in logwatch
Just for the record and if anyone wants to check on it. Upstream bug submitted: http://sourceforge.net/tracker/?func=detailaid=3536008group_id=312875atid=1316824# ** Bug watch added: SourceForge.net Tracker #3536008 http://sourceforge.net/support/tracker.php?aid=3536008 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+subscriptions -- 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 1010602] [NEW] samba logs are not being reported in logwatch
Public bug reported: After upgrading from 10.04 to 12.04 samba logs no longer show up in logwatch reports. There was a change to /usr/share/logwatch/default.conf/logfiles/samba.conf between 10.04 and 12.04: LogFile=samba/* was changed to LogFile=samba/*.log In the samba package the default smb.conf file has logging defined as (no change 10.04-12.04): log file = /var/log/samba/log.%m Since files are log.* they are no longer parsed by logwatch because logwatch only looks for *.log 1. Description:Ubuntu 12.04 LTS Release:12.04 2. logwatch: Installed: 7.4.0+svn20111221rev79-1ubuntu1 Candidate: 7.4.0+svn20111221rev79-1ubuntu1 Version table: *** 7.4.0+svn20111221rev79-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status samba: Installed: 2:3.6.3-2ubuntu2.1 Candidate: 2:3.6.3-2ubuntu2.2 Version table: 2:3.6.3-2ubuntu2.2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages *** 2:3.6.3-2ubuntu2.1 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 2:3.6.3-2ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 3. Logwatch reports/emails should contain samba log information. 4. No samba log information shows up in logwatch reports/emails. Possible fix is to distribute the attached samba.conf in /usr/share/logwatch/dist.conf/logfiles/ It contains LogFile=samba/* which would revert logwatch's behavior to what it was in 10.04 for samba logs. This will allow any type of log file naming you wish in your samba config in the /var/log/samba/ folder to be correctly parsed by logwatch. ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New ** Tags: regression -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+subscriptions -- 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 1010602] Re: samba logs are not being reported in logwatch
** Attachment added: Fix to revert back to prior working settings https://bugs.launchpad.net/bugs/1010602/+attachment/3181066/+files/samba.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+subscriptions -- 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 1010602] Re: samba logs are not being reported in logwatch
Here is the source commit that changed the samba.conf. The reason listed was: samba.conf patch to deal with cores dir -mgt I have no idea what that means honestly but maybe it would be of help to know... http://logwatch.svn.sourceforge.net/viewvc/logwatch?view=revisionrevision=5 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010602 Title: samba logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010602/+subscriptions -- 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 1010625] [NEW] named logs are not being reported in logwatch
Public bug reported: After upgrading from 10.04 to 12.04 named logs no longer show up in logwatch reports. Not sure if this should be filed as a bug against rsyslog or logwatch. There was a change to /etc/rsyslog.d/50-default.conf between 10.04 and 12.04 and a bunch of the seperate log files are now commented out and most things are only in /var/log/syslog Since the /usr/share/logwatch/default.conf/services/named.conf lists messages as the log file it never reports any log data. I changed my /etc/rsyslog.d/50-default.conf by uncommenting these lines (match the config in 10.04): daemon. lpr. user. mail.info mail.warn *.=debug *.=info The last one above sends most stuff to the messages file so named logs entries show up in logwatch reports after making the above changes. Part of me believes rsyslog should be considered the problem but on the other hand if rsyslog is correct then logwatch's named.conf needs to be overiden in dist.conf to correct for the rsyslog change. 1. Description: Ubuntu 12.04 LTS Release: 12.04 2. logwatch: Installed: 7.4.0+svn20111221rev79-1ubuntu1 Candidate: 7.4.0+svn20111221rev79-1ubuntu1 Version table: *** 7.4.0+svn20111221rev79-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status bind9: Installed: 1:9.8.1.dfsg.P1-4 Candidate: 1:9.8.1.dfsg.P1-4ubuntu0.1 Version table: 1:9.8.1.dfsg.P1-4ubuntu0.1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages *** 1:9.8.1.dfsg.P1-4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status rsyslog: Installed: 5.8.6-1ubuntu8 Candidate: 5.8.6-1ubuntu8 Version table: *** 5.8.6-1ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 3. Logwatch reports/emails should contain named log information. 4. No named log information shows up in logwatch reports/emails. ** Affects: logwatch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010625 Title: named logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010625/+subscriptions -- 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 1000355] Re: [SRU] drbd fence-peer breaks when using kernel 2.6.32-41
Hans - The patch is awaiting verification testing. I was unable to test the proposed fix since I had mitigated the bug already on my servers by the time it was available. Looks like tmortensen has tested it so I would expect you to see the patch available soon! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: [SRU] drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+subscriptions -- 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 1000355] [NEW] drbd fence-peer breaks when using kernel 2.6.32-41
Public bug reported: Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8 Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685 This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing: To replicate: Have fencing enabled in drbd config: In handlers section: fence-peer /usr/lib/drbd/crm-fence-peer.sh In the disk section: fencing resource-only; Have both drbd nodes uptodate with one primary one secondary Make the fence-peer get executed. I did this by: Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed. Fence handler will report fence-peer exited with 0 (broken) - such as this: May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0) May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0 If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0. This commit in drbd git should fix this behavior: http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43 This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. ** Affects: drbd8 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+subscriptions -- 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 1000355] Re: drbd fence-peer breaks when using kernel 2.6.32-41
Unfortunately unable to collect such log files due to the nature of the bug and changes since to bring systems back to working order. I might have further info I could give - if there are specific questions I will try to answer. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+subscriptions -- 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 1000355] Re: drbd fence-peer breaks when using kernel 2.6.32-41
** Description changed: Ubuntu 10.04 Lucid with 2.6.32-41 kernel and drbd8 Kernel 2.6.32-41 fixed a consistency issue around UMH_WAIT_PROC in this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/963685 This causes the drbd fencing script's exit codes to be incorrectly interpreted which then breaks the drbd fencing: + + This also affects linux source in all distributions after Lucid + with the applicable kernel versions patched in bug 963685 above since + the drbd kernel module is mainlined in those more recent kernel versions + To replicate: Have fencing enabled in drbd config: In handlers section: fence-peer /usr/lib/drbd/crm-fence-peer.sh In the disk section: fencing resource-only; Have both drbd nodes uptodate with one primary one secondary Make the fence-peer get executed. I did this by: Having drbd under pacemaker control. Both pacemaker nodes were online and in-sync. Drbd in primary on node 1. Put node 1 in standby. Fence-peer will get executed. Fence handler will report fence-peer exited with 0 (broken) - such as this: May 15 09:45:17 kernel: [56645.420714] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 May 15 09:45:17 kernel: [56645.420920] block drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 0 (0x0) May 15 09:45:17 kernel: [56645.420925] block drbd0: fence-peer helper broken, returned 0 If you log debug output of fence-peer script (crm-fence-peer.sh) when executed it exits 4 not the kernel reported 0. - This commit in drbd git should fix this behavior: http://git.drbd.org/gitweb.cgi?p=drbd-8.3.git;a=commitdiff;h=e6cbc43 - - This will cause complete failure of a drbd setup using fencing to auto-recover or continue without manual intervention and repair. + This will cause complete failure of a drbd setup using fencing to auto- + recover or continue without manual intervention and repair. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+subscriptions -- 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 1000355] Re: drbd fence-peer breaks when using kernel 2.6.32-41
** Changed in: drbd8 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/1000355 Title: drbd fence-peer breaks when using kernel 2.6.32-41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/1000355/+subscriptions -- 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 990742] Re: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed
I was finally able to get the half upgraded system fixed using the proposed package. After that was running for a bit I went ahead and upgraded another server in my cluster running the same services. I used the proposed libsasl2-2 package and the upgrade completed start to finish without a hiccup. So on 2 servers using the proposed packaged solved the issue without any side affects. Thanks! ** Tags removed: verification-needed ** Tags added: verification-done ** Description changed: I was trying to apt-get install dpkg to work around #944452 and got the following while trying to upgrade slapd: Setting up slapd (2.4.28-1.1ubuntu4) ... Use of uninitialized value $type in ucfirst at /usr/share/perl5/Debconf/AutoSelect.pm line 35. Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.21-0ubuntu5.7... done. Moving old database directories to /var/backups: Loading from /var/backups/slapd-2.4.21-0ubuntu5.7: - directory dc=interlinx,dc=bc,dc=ca... failed. Loading the database from the LDIF dump failed with the following error while running slapadd: 4f9c4903 slap_sasl_init: auxprop add plugin failed slapadd: slap_init failed! dpkg: error processing slapd (--configure): subprocess installed post-installation script returned error exit status 1 This looks to be related to http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=665473 where message #10 (http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=665473#10) in that bug says: This looks like a repeat of bug #628237. However, slapd 2.4.28-1.1/amd64 has a dependency on libsasl2-2 (= 2.1.24), ... Looking at the package info for slapd: Package: slapd Priority: optional Section: net Installed-Size: 4064 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Debian OpenLDAP Maintainers pkg-openldap-de...@lists.alioth.debian.org Architecture: i386 Source: openldap Version: 2.4.28-1.1ubuntu4 Replaces: ldap-utils ( 2.2.23-3), libldap2 Provides: ldap-server, libslapi-2.4-2 Depends: libc6 (= 2.15), libdb5.1, libldap-2.4-2 (= 2.4.28-1.1ubuntu4), libltdl7 (= 2.4.2), libodbc1 (= 2.2.11) | unixodbc (= 2.2.11), libperl5.14 (= 5.14.2), libsasl2-2, libslp1, libwrap0 (= 7.6-4~), coreutils (= 4.5.1-1), psmisc, perl ( 5.8.0) | libmime-base64-perl, adduser, lsb-base (= 3.2-13) We can see that it's not requiring a newer libsasl2-2. At this point I did an apt-get install libsasl2-2 and it installed the new libsasl2-2 and allowed the configuration of slapd to finish. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: slapd 2.4.28-1.1ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat Apr 28 15:56:29 2012 ProcEnviron: LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: openldap - -- SRU Justification -- [Impact] slapd's maintainer scripts make use of utilities like slapcat and slapadd which require a running slapd server, however, the relationship between slapd and libsasl2-2 packages do not take into account a binary incompatability introduced with 2.4.28-1.1. As a result, libsasl2-2 is not upgraded until after slapd, slapd fails to start (with error msg cited in the bugs), and maintainer scripts fail during upgrades with a debconf error like: http://paste.ubuntu.com/965636/ [Development Fix] The issue has been sorted in Debian and in Quantal with the recent merges. A thorough explanation of the fix is available at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628237#163 . The solution is to update cyrus-sasl2 with: - - Breaks: 'slapd 2.4.25-4' on libsasl2-2 - - shlib dependency on 2.1.24 for libsasl2-2 + - Breaks: 'slapd 2.4.25-4' on libsasl2-2 + - shlib dependency on 2.1.24 for libsasl2-2 Both of which have been applied to packaging in Debian and synced into Ubuntu Quantal. A no-change rebuild of openldap against the new sasl dependency is required as well. [Stable Fix] - The two one-liners from above should be back-ported from 2.1.25.dfsg1-4 packaging and applied + The two one-liners from above should be back-ported from 2.1.25.dfsg1-4 packaging and applied to cyrus-sasl2 packaging in Precise. A no-change rebuild of openldap against the newly updated dependency is required as well. [Test Case] - To reproduce, install slapd on a lucid installation, populate a minimal LDAP directory and do-release-upgrade. A script to populate a minimal database can be found at http://paste.ubuntu.com/965633/. + To reproduce, install slapd on a lucid installation, populate a minimal LDAP directory and do-release-upgrade. A script to populate a minimal database can be found at http://paste.ubuntu.com/965633/. [Regression Potential] Minimal. Packaging changes ensure proper ordering of upgrades during dist-upgrade and do not touch original source tree.
[Bug 990742] Re: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed
I have my server in that state now unfortunately so I should be able to test. How would I tested proposed while trying to do-release-upgrade? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/990742 Title: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/990742/+subscriptions -- 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 994837] [NEW] package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
Public bug reported: Upgrading from 10.04 LTS to 12.04 LTS. Upgrade failed after slapd failed to install. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: slapd 2.4.21-0ubuntu5.7 ProcVersionSignature: Ubuntu 2.6.32-40.87-server 2.6.32.57+drm33.23 Uname: Linux 2.6.32-40-server x86_64 Architecture: amd64 Date: Fri May 4 17:06:45 2012 ErrorMessage: ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu-Server 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.2) SourcePackage: openldap Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/994837 Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/994837/+subscriptions -- 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 994837] Re: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/994837 Title: package slapd 2.4.21-0ubuntu5.7 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/994837/+subscriptions -- 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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
I have tested this a couple times a week since the fix was proposed and I have had no ill effects and it has fixed the problem. Hopefully we can get this update out to all! If there is any other info I can provide please let me know. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- 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
Re: [Ubuntu-ha] [Bug 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
Henning You are probably right that this isn't the right place to continue with non-bug questions though Andres or others could answer that more acurately. I would recommend drbd-users mailing list as there are many experts there for config and troubleshooting. Also the pacemaker mailing lists is a good one. *snip* I don't have any idea why your getting the broken pipe... but do you have STONITH/fencing configured?! Normally when you have a comm link break like that then you would want Pacemaker to STONITH the disconnected node. Prior to the STONITH which ever DRBD node is going to survive should fence the resource preventing it from becoming primary until it is UpToDate. I use the fence peer handler in DRBD set to resource only and then have STONITH configure in Pacemaker. This way I can have a break in DRBD that doesn't automatically STONITH the node (but prevents the borked DRBD from coming up as Master and causing split brain) unless the Cluster communications are also dead at which point Pacemaker will shoot the node. I think the lack of fencing/STONITH is causing the split brain because both nodes do their own thing when not communicating which causes the diverging data set. This causes a split brain every time this happens even though there are no writes on the devices yet. You have your split brain handling configured like this still?: after-sb-0pri disconnect; after-sb-1pri consensus; after-sb-2pri disconnect; Your are telling it to disconnect regardless of changes with these split brain lines (I believe it's part of the cause). Have you considered using some more agressive split brain handling if your going with dual primary? They can be controversial topic due to data loss but... In the users guide at the bottom of this page it lists split brain behaviors that are considered OK for dual primary/clustered filesystem setups: http://www.drbd.org/users-guide/s-configure-split-brain-behavior.html after-sb-0pri discard-zero-changes; after-sb-1pri discard-secondary; after-sb-2pri disconnect; You would likely hit sb-1pri if you had fencing. It would go something like this: Break in comms Node 1 is fenced preventing it from becoming master Pacemaker shoots node 1 Node 1 reboots and (if setup to auto start the cluster) pacemaker accepts the node back into the cluster Drbd links up and finds Node 1 is diverged Node 1 is fenced so it is not master right now Considers the after-sb-1pri rule - this assumes that since it's dual primary if you have one primary then the dataset on that primary is always good and there is no need to perserve the secondary data so just overwrite it. Basically executes the commands you did manually and discards the Node 1 data. Once Node 1 is UpToDate DRBD removes the fencing and allows Node 1 to become master I hope all of that wasn't too confusing! Jake -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+subscriptions -- 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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Still working good - no issues. I've changed/rebooted both nodes and it takes snapshots, re-syncs, then removes snapshots (at least 30 times since applying the patch) without a hitch. Thanks again for your help! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- 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 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
I know how it might not look like a Pacemaker problem but I believe it is. Pacemaker is in charge of everything. As I put in the comment before I believe this line disallows Drbd2 to be master on node 2: location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1 Since everything else relies on Drbd2 being promoted to master (o2cb, dlmcontrol, filesystem via order and colocation constraints) none of those service will be started on node 2. Therefore you cannot have ocfs2_controld running on node 2 because Drbd2 is never master which means it could not be contacted. This would generate the errors in your logs... at least that's what I think! Though I'm not sure why dlm_controld.pcmk is running... Hopefully it help! Jake -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+subscriptions -- 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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Ok looks good. No zombie processes. I updated and restarted node 1 - drbd initiated snapsho on startup, synced properly (wouldn't get that far before) and then removed them. After doing that on node 1 I updated and restarted node 2 (causing everything to fail to node 1) and everything moved and resynced after restart properly. Only thing I don't understand/like is the following in the syslog: Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 3 (/) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 4 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 6 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 7 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1761]: File descriptor 7 (/etc) leaked on lvdisplay invocation. Parent PID 1761: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 8 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 9 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash Jul 13 10:50:16 Condor snapshot-resync-target-lvm.sh[1760]: File descriptor 10 (/etc) leaked on lvdisplay invocation. Parent PID 1760: /bin/bash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- 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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Thanks Adam/Andres I've got to remember: Google first, ask second - always not just mostly! I'll report in again in about a week on this. I am doing a lot of reconfig, add resources, testing, and failing of my pacemaker cluster so I will report on how the snapshot patch holds up. It *should* get a good workout! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- 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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Andres - have you had a chance to review my last update? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- 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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Still the same thing - zombie processes for lvm snapshots with 100% cpu. Script still doesn't have the changes in the patch applied - still looks identical as my post #8. root@Vulture:~# apt-cache policy drbd8-source drbd8-source: Installed: 2:8.3.7-1ubuntu2.3 Candidate: 2:8.3.7-1ubuntu2.3 Version table: *** 2:8.3.7-1ubuntu2.3 0 500 http://ppa.launchpad.net/gandelman-a/ppa/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 2:8.3.7-1ubuntu2.2 0 500 http://ppa.launchpad.net/andreserl/ppa/ubuntu/ lucid/main Packages 2:8.3.7-1ubuntu2.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 2:8.3.7-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- 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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Thanks Adam - thought that was weird. Only update available was drbd8-source after adding your ppa. Maybe because I use amd64 builds? I noticed it says need to be built next to those in your ppa. I'll check again in the morning. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- 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 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
You have a location constraint for msDrbd2 that requires it to be master on node 1 only. I would assume it's leftover from your master/slave setup: location locDrbd2Master msDrbd2 rule role=master inf: #uname eq node1 I would remove that and see what happens. Also a few other things: In ordering statements the action performed on the first item is applied to all the others unless explicitly defined. In the statement below if msDrbd2 is not master it will promote it to master and once that finished it will then try to take the same promote action on cloneDlm also. If all items required a start action then you could not define the action at all or only on define it on the first and it would be fine but if you have mixed actions then all must be defined. It should be changed to match the second statement. order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm:start In this ordering statement I think you meant to put before not after... :-) order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm Also to follow-up on Ante's comment - you were following DRBD users guide for Legacy non-Pacmaker setup. I don't know if you found it but here is the direct link to the Pacemaker config in the DRBD users guide: http://www.drbd.org/users-guide/s-ocfs2-pacemaker.html Last - once you have it functioning well you can group the primitives for Dlm and o2cb before you clone them and then eliminate a couple order and colo statements. Then you can combine the colocation and ordering statements for Drbd, the ocfs control group clone and the file system into one of each. I.E. group g_ocfs2control p_controld p_o2cb clone cl_ocfs2control g_ocfs2control \ meta globally-unique=false interleave=true target-role=Started colocation c_fs_srv_on_ocfs2control_on_drbd_srv_master inf: cl_fs_srv cl_ocfs2control ms_drbd_srv:Master order o_drbd_srv_master_before_ocfs2control_before_fs_srv 0: ms_drbd_srv:promote cl_ocfs2control:start cl_fs_srv:start Hope that helps! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+subscriptions -- 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 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
Whoops! I put them backwards too! In this ordering statement I think you meant to put before not after... :-) order ordDlm-before-msDrbdMaster2 0: msDrbd2:promote cloneDlm I meant it should be after not before! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+subscriptions -- 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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Hi Andres, So I gave it a try and now I'm racking my brain because I thought I knew what I was doing but it didn't behave as I expected and I don't know if it's my ignorance or a problem so I'll let you be the judge! Executed the following on both nodes, one after the other finished: Added your PPA. apt-get update; apt-get upgrade Edit /etc/drbd.d/global_common.conf and uncomment before and after-resync-target shutdown -r now Ended up with all kinds of errors and zombie lvm processes and drbd complaining etc. after restart. Looked at the lvm scripts in question - /usr/lib/drbd/snapshot-resync-target-lvm.sh The changes from the patch are not there... if I understand what the patch was supposed to do. First - The meat of the patch was to remove a couple of shift lines from the case statement among other things correct? Second - doing the apt-get upgrade should have replaced the patched script? Node 2: root@Vulture:~# apt-cache policy drbd8-source drbd8-source: Installed: 2:8.3.7-1ubuntu2.2 Candidate: 2:8.3.7-1ubuntu2.2 Version table: *** 2:8.3.7-1ubuntu2.2 0 500 http://ppa.launchpad.net/andreserl/ppa/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 2:8.3.7-1ubuntu2.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 2:8.3.7-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages Node 1: root@Condor:~# apt-cache policy drbd8-source drbd8-source: Installed: 2:8.3.7-1ubuntu2.2 Candidate: 2:8.3.7-1ubuntu2.2 Version table: *** 2:8.3.7-1ubuntu2.2 0 500 http://ppa.launchpad.net/andreserl/ppa/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 2:8.3.7-1ubuntu2.1 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 2:8.3.7-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages root@Vulture:~# cat /usr/lib/drbd/snapshot-resync-target-lvm.sh | grep -A 20 case case $1 in -p|--percent) SNAP_PERC=$2 shift ;; -a|--additional) SNAP_ADDITIONAL=$2 shift 2 ;; -n|--disconnect-on-error) DISCONNECT_ON_ERROR=1 shift ;; -v|--verbose) BE_VERBOSE=1 shift ;; --) shift break ;; Thoughts?? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions -- 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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Andres, This is a real pain for those of us who would like to ensure that we don't lose data due to a failure during re-sync. If we don't take a snapshot prior to a re-sync of the secondary and there was a failure it could be catastrophic. I'm pretty sure Lars put out a patch which is mentioned in the original bug report. I realize getting this into 10.04 can be a long process. Any chance in the mean time you would be willing to put up a patched version in the HA PPA? I could patch it myself however if you put it up at least it would be there for those that don't know how or don't want to modify their packages outside of apt. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid -- 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 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
Excellent! Thank you Andres -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid -- 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 490370] [NEW] Cannot start guest when apparmor is running
Public bug reported:
When I try to start a Windows XP virtual machine (kvm) it fails with the
following error:
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 493, in run_domain
vm.startup()
File /usr/share/virt-manager/virtManager/domain.py, line 558, in startup
self.vm.create()
File /usr/lib/python2.6/dist-packages/libvirt.py, line 293, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error cannot parse QEMU version number in ''
If I stop AppArmor it starts fine.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
Cannot start guest when apparmor is running
https://bugs.launchpad.net/bugs/490370
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 490370] Re: Cannot start guest when apparmor is running
** Attachment added: Guest XML definition file http://launchpadlibrarian.net/36260352/winXPpro.xml -- Cannot start guest when apparmor is running https://bugs.launchpad.net/bugs/490370 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 490370] Re: Cannot start guest when apparmor is running
Host: Linux IT02 2.6.31-14-server #48-Ubuntu SMP Fri Oct 16 15:07:34 UTC 2009 x86_64 GNU/Linux Package versions: libvirt-bin 0.7.0-1ubuntu13.1 libvirt0 0.7.0-1ubuntu13.1 python-libvirt 0.7.0-1ubuntu13.1 python-virtinst 0.400.3-4ubuntu1 qemu-kvm 0.11.0-0ubuntu6.3 ubuntu-virt-server 1.2 virt-manager 0.7.0-3ubuntu1 virt-viewer 0.0.3-6ubuntu7.xul191.1 kvm 1:84+dfsg-0ubuntu16+0.11.0+0ubuntu6.3 qemu-kvm 0.11.0-0ubuntu6.3 -- Cannot start guest when apparmor is running https://bugs.launchpad.net/bugs/490370 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 490370] Re: Cannot start guest when apparmor is running
No files in /var/log/apparmor/ Entry in kern.log: (Repeats everytime I tried to start guest - pid/parent varied but the rest is identical - if more are needed let me know) Nov 30 10:11:12 IT02 kernel: [ 405.887561] type=1503 audit(1259593872.142:29): operation=exec pid=2402 parent=1933 profile=/usr/sbin/libvirtd requested_mask=x:: denied_mask=x:: fsuid=0 ouid=0 name=/etc/libvirt/qemu/kvm -- Cannot start guest when apparmor is running https://bugs.launchpad.net/bugs/490370 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 490370] Re: Cannot start guest when apparmor is running
That is where the XML definitions resides on my system... r...@it02:/home/jsmith# ls /etc/libvirt/ libvirtd.conf qemu qemu.conf storage r...@it02:/home/jsmith# ls /etc/libvirt/qemu autostart KarmicBeta1.xml kvm networks winXPpro.xml r...@it02:/home/jsmith# A bit of history (and maybe my problem isn't apparmor's problem specifically...) The host system is an upgrade from 9.04. When it was 9.04 I uninstalled the distribution installs of kvm, libvirt, and virt manager and compiled and installed them from source to get some of the newer features available. I later removed the compiled versions and re-installed the distribution version. All of this was done before upgrading to 9.10. Maybe this caused some of the issue(s)? -- Cannot start guest when apparmor is running https://bugs.launchpad.net/bugs/490370 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 490370] Re: Cannot start guest when apparmor is running
Whoops that isn't correct - thats not where my XML resides. And I figured out what it is. I was trying to get auto-connect USB recognition to work (back when it was 9.04) and the instructions here (http://david.wragg.org/blog/2009/03 /usb-pass-through-with-libvirt-and-kvm.html) said to make this script up: $ cat /etc/libvirt/qemu/kvm #!/bin/sh exec /usr/bin/kvm `echo $* | sed 's|-usbdevice host:\([^ ]*\)|-usbdevice host:auto:*.*:\1|g'` and (direct quote from afore mentioned website) Save the script as /etc/libvirt/qemu/qemu-kvm, and make it executable. With that in place, you need to tell libvirt to use it instead of the real KVM binary. Do that by editing the VM XML description as described in my previous post. You need to edit the //domain/devices/emulator entry to refer to the wrapper script, e.g. domain type='kvm' namewindowsxp/name … devices emulator/etc/libvirt/qemu/qemu-kvm/emulator … /devices /domain Restart the relevant VMs, and USB pass-through with autoconnect should now work. So now I realize it's not a bug really... now to figure out whether or not I really need the wrapper at all... Sorry to have filed this without finding out it was my customization in the first place! -- Cannot start guest when apparmor is running https://bugs.launchpad.net/bugs/490370 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 490370] Re: Cannot start guest when apparmor is running
Thanks! -- Cannot start guest when apparmor is running https://bugs.launchpad.net/bugs/490370 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 269627] Re: force group breaks share
Found syntactical error: force group = +group-name should be force group = group-name No problem any longer. I hope that no one had spent much time as of yet. ** Changed in: samba (Ubuntu) Status: New = Invalid -- force group breaks share https://bugs.launchpad.net/bugs/269627 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 269627] [NEW] force group breaks share
Public bug reported: Binary package hint: samba When you have 'force group = xxx' you receive Network path not found error in a WinXP client trying to access share that contains the force group directive. Description:Ubuntu 8.04.1 Release:8.04 samba: Installed: 3.0.28a-1ubuntu4.5 Candidate: 3.0.28a-1ubuntu4.5 Version table: *** 3.0.28a-1ubuntu4.5 0 500 http://us.archive.ubuntu.com hardy-updates/main Packages 100 /var/lib/dpkg/status smb.conf [global] using ldap backend [Test] comment = for testing only path = /path/to/test read only = no write list = +test force group = +test directory test is 775 root.test When I comment out force group I can connect from an XP client no problem. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- force group breaks share https://bugs.launchpad.net/bugs/269627 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 269627] Re: force group breaks share
Attachment is the error message received in WinXP. -- force group breaks share https://bugs.launchpad.net/bugs/269627 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 269627] Re: force group breaks share
** Attachment added: err1.jpg http://launchpadlibrarian.net/17568803/err1.jpg -- force group breaks share https://bugs.launchpad.net/bugs/269627 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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
