[Bug 1184871] Re: piston is incompatible with Django 1.5
*** This bug is a duplicate of bug 1184219 *** https://bugs.launchpad.net/bugs/1184219 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-django-piston (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-django-piston in Ubuntu. https://bugs.launchpad.net/bugs/1184871 Title: piston is incompatible with Django 1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-django-piston/+bug/1184871/+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 1251939] Re: Chroot fails with "Cannot chroot when not started as root" error
The attachment "patch against 2.4.6-2" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with "Cannot chroot when not started as root" error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+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 997217] Re: salsauthd maxes cpu
I'm sorry to say, that there is no simple test case. The problem cannot be reproduced with simple instructions. You need to run saslauthd -a rimap for a few days in front of nginx-extras+dovecot IMAP and do a lot of imap logins to trigger the bug. But the bug is already fixed by the newer patch version of 0034-fix_dovecot_authentication.patch in 2.1.25.dfsg1-17. Some more system information: Precise nginx: mail01:~# dpkg -l "nginx*" |grep ^ii ii nginx-common 1.1.19-1ubuntu0.4 small, but very powerful and efficient web server (common files) ii nginx-extras 1.1.19-1ubuntu0.4 nginx web server with full set of core modules and extras Self-compiled known-to-be-working stable dovecot release 2.1.16: mail01:~# doveconf -n |head -2 # 2.1.16: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-56-generic x86_64 Ubuntu 12.04.3 LTS Saslauthd ist running with following parameters, where 10.10.10.10 is the remote dovecot imap server: /usr/sbin/saslauthd -a rimap -O 10.10.10.10 -r -c -t 60 -m /var/run/saslauthd -n 5 In the meanwhile I took 0034-fix_dovecot_authentication.patch from the saucy package https://launchpad.net/ubuntu/saucy/amd64/sasl2-bin/2.1.25.dfsg1-17, updated the patch 0034-fix_dovecot_authentication.patch in the precise package and installed it on our servers. I'll run for a few days (or weeks) now, and see if the CPU problem goes away. If you want to test an official package update for precise, we can do so on one of the machines. Regards Daniel -- 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/997217 Title: salsauthd maxes cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/997217/+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 997217] Re: salsauthd maxes cpu
Daniel, Please could you elaborate on the test case? Neither me nor the stable update verification team will be able to reproduce or test the presence of the bug or a fix for it based on the description you've given. These need to be step-by-step instructions that anybody can follow, including somebody not familiar with the specifics of the package. Will you be OK to test the proposed fix once it is built and ready, so that the update will be able to land for general use? Thanks! -- 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/997217 Title: salsauthd maxes cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/997217/+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 1251939] Re: Chroot fails with "Cannot chroot when not started as root" error
If you fix that, you also need to regenerate debian/patches/itk-rerun- configure.patch after the upstream patch has been applied . I have done that in the attached patch. I would recommend that you do that for saucy. This will also be fixed in 2.4.6-4, which will be uploaded to Debian soon. Therefore for trusty, there is probably no need for further action. ** Patch added: "patch against 2.4.6-2" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1251939/+attachment/3911233/+files/unixd-fix.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with "Cannot chroot when not started as root" error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+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 997217] Re: salsauthd maxes cpu
Hi Robie, Justification against https://wiki.ubuntu.com/StableReleaseUpdates#When: * severe regression bug: Package sasl2-bin is unusable after Upgrade from Lucid LTS to Precise LTS since saslauthd eats up 100% CPU on production mailservers when using rimap and needs regular restarts. saslauthd in Lucid LTS did work just fine with rimap. Complete steps 1 through 4 in https://wiki.ubuntu.com/StableReleaseUpdates#Procedure Step 1) Check that the bug is fixed in the current development release, and that its bug task is "Fix Released". --> Yes, launchpad bug #997217 has status "Fix released". Check. Step 2) Ensure that the bug report for this issue is public. --> Yes, launchpad bug #997217 is public. Step 3) Update the bug report description and make sure it contains the following information: [Impact] * High Load on production mailservers since Upgrade of Long Term Support Release from Lucid 10.04 LTS to Precise 12.04 LTS [Test Case] * Sporadically running into high load (infinite loop in saslauthd) when running saslauthd via Remote (rimap) against nginx mailproxy from "nginx-extras" package on mailservers with high imap traffic [Regression] * The bug itself is a regression in comparison to Lucid 10.04. Step 4) Ask someone in the Ubuntu bug control team to nominate the bug for the appropriate Ubuntu release(s)/series (e. g. the current LTS and latest stable release). --> Nominated for Precise by Adolfo Jayme Barrientos Is anything missing? Regards Daniel ** Tags added: precise -- 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/997217 Title: salsauthd maxes cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/997217/+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 1252022] Re: package mysql-client-core-5.5 5.5.32-0ubuntu7 [modified: usr/bin/mysql usr/bin/mysqlcheck usr/share/man/man1/mysql.1.gz usr/share/man/man1/mysqlcheck.1.gz] failed to install/upgrade:
apt-get -o Dpkg::Options::="--force-overwrite" upgrade fixed it ** Changed in: mysql-5.5 (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1252022 Title: package mysql-client-core-5.5 5.5.32-0ubuntu7 [modified: usr/bin/mysql usr/bin/mysqlcheck usr/share/man/man1/mysql.1.gz usr/share/man/man1/mysqlcheck.1.gz] failed to install/upgrade: спроба перезаписати «/usr/bin/mysqlcheck», який вже є у пакунку percona- server-client-5.6 1:5.6.14-rel62.0-483.raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1252022/+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 1251939] Re: Chroot fails with "Cannot chroot when not started as root" error
Thank you for reviewing this bug report and assigning the severity. While I agree with you on the assigned severity of "Medium", I'd like to point out that though ChrootDir is not a default option, it relates to the security of apache server. I am not sure how many users simply use the server w/ default options, but I would guess many will do server hardening starting with chrooting. Would really appreciate if this fix is included soon. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with "Cannot chroot when not started as root" error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+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 1251939] Re: Chroot fails with "Cannot chroot when not started as root" error
Thank you for taking the time to report this bug and helping to make Ubuntu better. Looks like we need to cherry-pick this upstream fix if we do not merge it in first. ** Changed in: apache2 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with "Cannot chroot when not started as root" error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+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 1251939] Re: Chroot fails with "Cannot chroot when not started as root" error
Since ChrootDir is not a default option, I think Medium priority is appropriate given the criteria listed at https://wiki.ubuntu.com/Bugs/Importance. That's not to say we shouldn't fix it, and an SRU to Saucy isn't out of the question, either. ** Changed in: apache2 (Ubuntu) Importance: Undecided => Critical ** Changed in: apache2 (Ubuntu) Importance: Critical => Medium ** Bug watch added: Apache Software Foundation Bugzilla #55787 http://issues.apache.org/bugzilla/show_bug.cgi?id=55787 ** Also affects: apache2 via http://issues.apache.org/bugzilla/show_bug.cgi?id=55787 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1251939 Title: Chroot fails with "Cannot chroot when not started as root" error To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1251939/+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 997217] Re: salsauthd maxes cpu
If you need a fix for an existing stable release, please comment with a justification against https://wiki.ubuntu.com/StableReleaseUpdates#When and complete steps 1 through 4 in https://wiki.ubuntu.com/StableReleaseUpdates#Procedure -- 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/997217 Title: salsauthd maxes cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/997217/+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 1252016] Re: package libldap-2.4-2 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:am
** Tags removed: need-duplicate-check -- 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/1252016 Title: package libldap-2.4-2 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1252016/+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 1252016] [NEW] package libldap-2.4-2 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:
Public bug reported: Release 13.04 Ubuntu in virtualbox as guest ProblemType: Package DistroRelease: Ubuntu 13.04 Package: libldap-2.4-2 (not installed) ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Sun Nov 17 09:10:48 2013 DuplicateSignature: package:libldap-2.4-2:(not installed):trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:amd64 ErrorMessage: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:amd64 InstallationDate: Installed on 2013-10-21 (26 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: openldap Title: package libldap-2.4-2 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict raring -- 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/1252016 Title: package libldap-2.4-2 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1252016/+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 1251941] Re: Sync python-django 1.6-1 (main) from Debian unstable (main)
This bug was fixed in the package python-django - 1.6-1 Sponsored for Jackson Doak (noskcaj) --- python-django (1.6-1) unstable; urgency=low * New upstream version. Closes: #557474, #724637. * python-django now also suggests the installation of ipython, bpython, python-django-doc, and libgdal1. Closes: #636511, #686333, #704203 * Set package maintainer to Debian Python Modules Team. * Bump standards version to 3.9.5, no changes needed. -- Luke Faraone Thu, 07 Nov 2013 15:33:49 -0500 ** Changed in: python-django (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-django in Ubuntu. https://bugs.launchpad.net/bugs/1251941 Title: Sync python-django 1.6-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1251941/+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
