Package: sasl2-bin
Version: 2.1.28+dfsg-10
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
Running saslauthd for postfix authentication, with postfix in a chroot,
using PAM as an authentication methods, causes saslauthd to exit, with
a message
Nov 03 13:00:59 agc saslauthd[808674]: : master exited: 617183
This appears to be a clean exit, rather than a crash, but was preceded
by several hundred messages of
Nov 03 13:00:44 agc saslauthd[617185]: pam_unix(smtp:auth): check pass; user
unknown
Nov 03 13:00:44 agc saslauthd[617185]: pam_unix(smtp:auth): authentication
failure; logname= uid=0 euid=0 tty= ruser= rhost=
Nov 03 13:00:46 agc saslauthd[617185]: DEBUG: auth_pam: pam_authenticate
failed: Authentication failure
Nov 03 13:00:46 agc saslauthd[617185]: : auth failure:
[user=nayan] [service=smtp] [realm=org.uk] [mech=pam] [reason=PAM auth error]
Nov 03 13:00:48 agc saslauthd[617188]: pam_unix(smtp:auth): check pass; user
unknown
Nov 03 13:00:48 agc saslauthd[617188]: pam_unix(smtp:auth): authentication
failure; logname= uid=0 euid=0 tty= ruser= rhost=
Nov 03 13:00:50 agc saslauthd[617188]: DEBUG: auth_pam: pam_authenticate
failed: Authentication failure
Nov 03 13:00:50 agc saslauthd[617188]: : auth failure:
[user=copier] [service=smtp] [realm=ambridge-garden-club.org.uk] [mech=pam]
[reason=PAM auth error]
Nov 03 13:00:52 agc saslauthd[617187]: pam_unix(smtp:auth): check pass; user
unknown
Nov 03 13:00:52 agc saslauthd[617187]: pam_unix(smtp:auth): authentication
failure; logname= uid=0 euid=0 tty= ruser= rhost=
Nov 03 13:00:55 agc saslauthd[617187]: DEBUG: auth_pam: pam_authenticate
failed: Authentication failure
Nov 03 13:00:55 agc saslauthd[617187]: : auth failure:
[user=beans] [service=smtp] [realm=org.uk] [mech=pam] [reason=PAM auth error]
A more imformative exit reason would help investigate the problem, also
the daemon should not exit simply because it has had a number of PAM
authentication failures.
Restarting the daemon restores normal operation, thus is a work-around,
but not ideal.
-- System Information:
Debian Release: 12.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-13-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sasl2-bin depends on:
ii db-util 5.3.2
ii debconf [debconf-2.0] 1.5.82
ii init-system-helpers 1.65.2
ii libc6 2.36-9+deb12u2
ii libcrypt1 1:4.4.33-2
ii libdb5.3 5.3.28+dfsg2-1
ii libkrb5-3 1.20.1-2+deb12u1
ii libldap-2.5-0 2.5.13+dfsg-5
ii libpam0g 1.5.2-6+deb12u1
ii libsasl2-2 2.1.28+dfsg-10
ii libssl3 3.0.11-1~deb12u1
ii lsb-base 11.6
ii perl 5.36.0-7
ii sysvinit-utils [lsb-base] 3.06-4
sasl2-bin recommends no packages.
sasl2-bin suggests no packages.
-- debconf information:
cyrus-sasl2/backup-sasldb2: /var/backups/sasldb2.bak
cyrus-sasl2/upgrade-sasldb2-backup-failed:
cyrus-sasl2/purge-sasldb2: false
cyrus-sasl2/upgrade-sasldb2-failed:
