xenial verification
Confirming bug:
ubuntu@xenial-saslauthd:~$ apt-cache policy sasl2-bin
sasl2-bin:
Installed: 2.1.26.dfsg1-14build1
Candidate: 2.1.26.dfsg1-14build1
Version table:
*** 2.1.26.dfsg1-14build1 500
500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Roberto, are you able to test this update? If not, I can do it, but it
would be better if someone not involved with the fix could do it.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/997217
** Description changed:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This condition
can be easily encountered when an authentication is happening and the
imap service is being restarted.
** Description changed:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This condition
can be easily encountered when an authentication is happening and the
imap service is being restarted.
Ok, trusty isn't affected because the loop there has an exit clause:
+ ret = read(s, rbuf+rc, sizeof(rbuf)-rc);
+ if ( ret<0 ) {
+ rc = ret;
+ break;
+ } else {
+ if (ret == 0) {
+ loopc += 1;
I'm unable to trigger this bug when running the test case on trusty,
even though the same code is there. I also tried adjusting the sleep.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Description changed:
[Impact]
The rimap authentication mechanism in saslauthd can hit a condition
where it will start spinning and using all available CPU. This condition
can be easily encountered when an authentication is happening and the
imap service is being restarted.
-
-
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ The rimap authentication mechanism in saslauthd can hit a condition
+ where it will start spinning and using all available CPU. This condition
+ can be easily encountered when an authentication is
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test
** Changed in: cyrus-sasl2 (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: cyrus-sasl2 (Ubuntu Xenial)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: cyrus-sasl2 (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: cyrus-sasl2 (Ubuntu
I reproduced the problem in xenial by timing a "testsaslauthd" call with
a "service dovecot stop" one (dovecot being my test imap server on
localhost).
This is good enough for an SRU test case, thanks all.
--
You received this bug notification because you are a member of Ubuntu
Server, which is
The patch 0034 mentioned in comment #10 is applied in the xenial package
2.1.26.dfsg1-14build1, so what Roberto hit could be a different issue
requiring a different fix.
Might have been this:
cyrus-sasl2 (2.1.26.dfsg1-15) unstable; urgency=medium
* Add fix for auth_rimap infinite loop (hang)
Trusty has 0034-fix_dovecot_authentication.patch, but it lacks the above
fix as well.
** Also affects: cyrus-sasl2 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Tags removed: precise
** Tags added: server-next
** Changed in: cyrus-sasl2 (Ubuntu Trusty)
Status: New =>
Just a short note:
With the 0034-fix_dovecot_authentication.patch from saucy package
https://launchpad.net/ubuntu/saucy/amd64/sasl2-bin/2.1.25.dfsg1-17 all
systems are running fine so far (for 9 days now), without high load of
saslauthd.
--
You received this bug notification because you are a
** Also affects: cyrus-sasl2 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: cyrus-sasl2 (Ubuntu Precise)
Status: New = Triaged
** Changed in: cyrus-sasl2 (Ubuntu Precise)
Importance: Undecided = High
--
You received this bug notification because you are a
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
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
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
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
This bugs represents a severe regression on upgrade from Ubuntu 10.04 LTS to
Ubuntu 12.04 LTS.
The package is rather unusable since it eats up 100% CPU on production
mailservers after upgrade to current LTS.
Would you please include the fix http://bugs.debian.org/cgi-
Fixed in version cyrus-sasl2/2.1.25.dfsg1-7
--
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:
Thanks. Saucy is now on 2.1.25.dfsg1-7, so marking Fix Released.
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
Bug patch for Debian Wheezy are here: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=708552
** Bug watch added: Debian Bug tracker #708552
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708552
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in Ubuntu.
24 matches
Mail list logo
