Bug#791814: sasl2-bin: fails to start saslauthd

[yamasita]

Package: sasl2-bin
Version: 2.1.26.dfsg1-13
Severity: important

Dear Maintainer,

* What led up to the situation?

I was if it was normal installation.
(apt-get install sasal2-bin)
It failed to start.
service saslauthd start
or
/etc/init.d/saslauthd start
or
systemctl start saslauthd.service

* What exactly did you do (or not do) that was effective (or ineffective)?

I was editing the /etc/default/saslauthd.
It was changed to "START=yes".

* What was the outcome of this action?

saslauthd did not start.

* What outcome did you expect instead?

saslauthd is wanted to start.

-- System Information:
Debian Release: 8.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages sasl2-bin depends on:
ii db-util 5.3.0
ii debconf [debconf-2.0] 1.5.56
ii libc6 2.19-18
ii libcomerr2 1.42.12-1.1
ii libdb5.3 5.3.28-9
ii libgssapi-krb5-2 1.12.1+dfsg-19
ii libk5crypto3 1.12.1+dfsg-19
ii libkrb5-3 1.12.1+dfsg-19
ii libldap-2.4-2 2.4.40+dfsg-1
ii libpam0g 1.1.8-3.1
ii libsasl2-2 2.1.26.dfsg1-13
ii libssl1.0.0 1.0.1k-3+deb8u1

sasl2-bin recommends no packages.

sasl2-bin suggests no packages.

-- Configuration Files:
/etc/default/saslauthd changed:
START=yes
DESC="SASL Authentication Daemon"
NAME="saslauthd"
MECHANISMS="pam"
MECH_OPTIONS=""
THREADS=15
OPTIONS="-c -m /var/run/saslauthd"


-- debconf information excluded


--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Roberto C. Sánchez]

package sasl2-bin
tag 791814 + moreinfo unreproducible
thanks

On Thu, Jul 09, 2015 at 01:42:37AM +0900, yamasita wrote:
>
> * What led up to the situation?
>
> I was if it was normal installation.
> (apt-get install sasal2-bin)
> It failed to start.
> service saslauthd start
> or
> /etc/init.d/saslauthd start
> or
> systemctl start saslauthd.service
>
> * What exactly did you do (or not do) that was effective (or ineffective)?
>
> I was editing the /etc/default/saslauthd.
> It was changed to "START=yes".
>
> * What was the outcome of this action?
>
> saslauthd did not start.
>
> * What outcome did you expect instead?
>
> saslauthd is wanted to start.
>

I have attempted to reproduce this in a stretch Docker. After starting
the container, I ran 'apt-get update && apt-get install -y sasl2-bin'.

After that, this is the result:

root@9fb09a55b38d:~# /etc/init.d/saslauthd status
[FAIL] Checking SASL Authentication Daemon: saslauthd (not running) failed!
root@9fb09a55b38d:~# /etc/init.d/saslauthd start
[warn] To enable saslauthd, edit /etc/default/saslauthd and set START=yes ... (warning).
root@9fb09a55b38d:~# sed -i 's/START=no/START=yes/' /etc/default/saslauthd
root@9fb09a55b38d:~# /etc/init.d/saslauthd start
[ ok ] Starting SASL Authentication Daemon: saslauthd.

Here is the same sequence in an unstable Docker:

root@1b23b77be2b2:~# /etc/init.d/saslauthd status
[FAIL] Checking SASL Authentication Daemon: saslauthd (not running) failed!
root@1b23b77be2b2:~# /etc/init.d/saslauthd start
[warn] To enable saslauthd, edit /etc/default/saslauthd and set START=yes ... (warning).
root@1b23b77be2b2:~# sed -i 's/START=no/START=yes/' /etc/default/saslauthd
root@1b23b77be2b2:~# /etc/init.d/saslauthd start
[ ok ] Starting SASL Authentication Daemon: saslauthd.


Can you try again to see if you can reproduce this problem.

Regards,

-Roberto

--
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com

[Privat]

Hi,

I was having issues starting saslauthd due to a misconfiguration in /etc/default/rcS

Where I should have put a line “FSCKFIX=yes” I had erroneously put “set FSCKFIX=yes”

After correcting that, everything started up fine.

HTH,

Karl.

[Nigel Horne]

Package: sasl2-bin
Version: 2.1.27+dfsg2-2
Followup-For: Bug #791814

Dear Maintainer,

Everthing was fine until today an update to sasl2-bin came in, and now I can't send e-mail from my phone using
my SMTP server.

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?

I ran "apt upgrade" which updated sasl2-bin

* What exactly did you do (or not do) that was effective (or
ineffective)?

Tried to send an e-mail

* What was the outcome of this action?

"ps ax | grep sasl" gives no output. Running "systemctl" shows it's not even trying to start the daemon.

My phone now says that I've entered the wrong username/password. I haven't, and anyway I haven't changed it.

* What outcome did you expect instead?

For my e-mails to still be able to be sent.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.14.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

LSM: AppArmor: enabled

Versions of packages sasl2-bin depends on:

ii db-util 5.3.1+nmu1
ii debconf [debconf-2.0] 1.5.79
ii init-system-helpers 1.60
ii libc6 2.32-4
ii libcrypt1 1:4.4.26-1
ii libdb5.3 5.3.28+dfsg1-0.8
ii libkrb5-3 1.18.3-7
ii libldap-2.4-2 2.4.59+dfsg-1
ii libpam0g 1.4.0-10
ii libsasl2-2 2.1.27+dfsg2-2
ii libssl1.1 1.1.1l-1
ii lsb-base 11.1.0
ii perl 5.32.1-6

sasl2-bin recommends no packages.

sasl2-bin suggests no packages.

-- Configuration Files:
/etc/default/saslauthd changed:
START=yes
DESC="SASL Authentication Daemon"
NAME="saslauthd"
MECHANISMS="pam"
MECH_OPTIONS=""

THREADS=5
OPTIONS="-c -m /var/run/saslauthd"


-- debconf information:
cyrus-sasl2/upgrade-sasldb2-backup-failed:
cyrus-sasl2/upgrade-sasldb2-failed:
cyrus-sasl2/backup-sasldb2: /var/backups/sasldb2.bak
cyrus-sasl2/purge-sasldb2: false

[Nigel Horne]

I changed the MECHANISMS from pam to getpwent and now saslauthd starts and
stays running. So that's an improvement. However it still doesn't send email
from my phone which claims "no password provided for $address" which is a lie
and since it's sasl that changed not my phone, I continue to suspect the
sasl2 update broke sendmail.

[Bastian Germann]

I guess you were experiencing #1003355. This is solved with revision 2.1.27+dfsg2-3.