Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 2 > Installation/Configuration

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #1  
Old 19th May 2009, 00:50
3DPeruna 3DPeruna is offline
Member
 
Join Date: Jan 2007
Posts: 50
Thanks: 8
Thanked 0 Times in 0 Posts
Default saslauthd issues after upgrade

I just upgraded following: http://www.howtoforge.com/upgrade-ub...er-to-8.04-lts

I thought I followed everything to the "t", but I'm getting an error when I try and start the saslauthd daemon - it fails.

If I do this

Code:
saslauthd -a pam  -n 5  -V -c -m /var/spool/postfix/var/run/saslauthd -r -d
It works and I can send out locally and through clients (Outlook).

Here's the output of the shell:

Code:
sh -x /etc/init.d/saslauthd start
Code:
+ NAME=saslauthd
+ DAEMON=/usr/sbin/saslauthd
+ DESC='SASL Authentication Daemon'
+ DEFAULTS=/etc/default/saslauthd
+ PWDIR=/var/run/saslauthd
+ PIDFILE=/var/spool/postfix/var/run/saslauthd/saslauthd.pid
+ test -f /usr/sbin/saslauthd
+ '[' -e /etc/default/saslauthd ']'
+ . /etc/default/saslauthd
++ START=yes
++ DESC='SASL Authentication Daemon'
++ NAME=saslauthd
++ MECHANISMS=pam
++ MECH_OPTIONS=
++ THREADS=5
++ OPTIONS='-c -m /var/spool/postfix/var/run/saslauthd -r'
+ '[' yes '!=' yes ']'
+ '[' xpam = x ']'
+ PARAMS=' -a pam'
+ START='--start --quiet --pidfile /var/spool/postfix/var/run/saslauthd/saslauthd.pid --startas /usr/sbin/saslauthd --name saslauthd --  -a pam'
+ case "${1}" in
+ echo -n 'Starting SASL Authentication Daemon: '
Starting SASL Authentication Daemon: ++ dpkg-statoverride --list /var/run/saslauthd
+ dir='root sasl 710 /var/run/saslauthd'
+ test -z 'root sasl 710 /var/run/saslauthd'
+ createdir root sasl 710 /var/run/saslauthd
+ '[' -d /var/run/saslauthd ']'
+ chown -c -h root:sasl /var/run/saslauthd
+ chmod -c 710 /var/run/saslauthd
+ start-stop-daemon --start --quiet --pidfile /var/spool/postfix/var/run/saslauthd/saslauthd.pid --startas /usr/sbin/saslauthd --name saslauthd -- -a pam
+ start-stop-daemon --test --start --quiet --pidfile /var/spool/postfix/var/run/saslauthd/saslauthd.pid --startas /usr/sbin/saslauthd --name saslauthd -- -a pam
+ echo '(failed).'
(failed).
+ exit 1
Thoughts?
Reply With Quote
Sponsored Links
  #2  
Old 19th May 2009, 15:26
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,711
Thanks: 1,899
Thanked 2,702 Times in 2,545 Posts
Default

What's in /etc/default/saslauthd?
Any errors in the mail log?
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
  #3  
Old 19th May 2009, 15:52
3DPeruna 3DPeruna is offline
Member
 
Join Date: Jan 2007
Posts: 50
Thanks: 8
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by falko View Post
What's in /etc/default/saslauthd?
Any errors in the mail log?
Code:
# Settings for saslauthd daemon
# Please read /usr/share/doc/sasl2-bin/README.Debian for details.
#

# Should saslauthd run automatically on startup? (default: no)
START=yes

# Description of this saslauthd instance. Recommended.
# (suggestion: SASL Authentication Daemon)
DESC="SASL Authentication Daemon"

# Short name of this saslauthd instance. Strongly recommended.
# (suggestion: saslauthd)
NAME="saslauthd"

# Which authentication mechanisms should saslauthd use? (default: pam)
#
# Available options in this Debian package:
# getpwent  -- use the getpwent() library function
# kerberos5 -- use Kerberos 5
# pam       -- use PAM
# rimap     -- use a remote IMAP server
# shadow    -- use the local shadow password file
# sasldb    -- use the local sasldb database file
# ldap      -- use LDAP (configuration is in /etc/saslauthd.conf)
#
# Only one option may be used at a time. See the saslauthd man page
# for more information.
#
# Example: MECHANISMS="pam"
MECHANISMS="pam"

# Additional options for this mechanism. (default: none)
# See the saslauthd man page for information about mech-specific options.
MECH_OPTIONS=""

# How many saslauthd processes should we run? (default: 5)
# A value of 0 will fork a new process for each connection.
THREADS=5

# Other options (default: -c -m /var/run/saslauthd)
# Note: You MUST specify the -m option or saslauthd won't run!
#
# See /usr/share/doc/sasl2-bin/README.Debian for Debian-specific information.
# See the saslauthd man page for general information about these options.
#
# Example for postfix users: "-c -m /var/spool/postfix/var/run/saslauthd"
#OPTIONS="-c -m /var/run/saslauthd"
OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd -r"
The mail.err log:

Code:
May 18 15:24:20 ohdweb pop3d: authdaemon: s_connect() failed: Connection refused
May 18 15:24:20 ohdweb pop3d: [Hint: perhaps authdaemond is not running?]
May 18 15:24:20 ohdweb pop3d: authentication error: Connection refused
May 19 07:09:40 ohdweb pop3d: Maximum connection limit reached for ::ffff:32.137.159.125
Other than a ton of rejected connections in the mail.warn log, the mail.log has regular postfix mail traffic. I tried starting the daemon and then hitting the log, but nothing showed up.
Reply With Quote
  #4  
Old 19th May 2009, 16:04
3DPeruna 3DPeruna is offline
Member
 
Join Date: Jan 2007
Posts: 50
Thanks: 8
Thanked 0 Times in 0 Posts
Default

One other note... I went back and reconfigured postfix as per the "perfect" setup after I started getting the start failures.
Reply With Quote
  #5  
Old 20th May 2009, 16:47
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,711
Thanks: 1,899
Thanked 2,702 Times in 2,545 Posts
Default

Please try this:
Code:
adduser postfix sasl 
/etc/init.d/postfix restart
/etc/init.d/saslauthd start
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
  #6  
Old 20th May 2009, 17:06
3DPeruna 3DPeruna is offline
Member
 
Join Date: Jan 2007
Posts: 50
Thanks: 8
Thanked 0 Times in 0 Posts
Default

I did that as part of the upgrade (as per the instructions). I did it again, just to be sure and get:

Code:
The user `postfix' is already a member of `sasl'.
Postfix restarts.
Saslauthd doesn't.
Reply With Quote
  #7  
Old 21st May 2009, 18:52
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,711
Thanks: 1,899
Thanked 2,702 Times in 2,545 Posts
Default

Can you run
Code:
/etc/init.d/saslauthd restart
?
What's the output of
Code:
ps aux | grep saslauthd
afterwards?
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
  #8  
Old 21st May 2009, 20:01
3DPeruna 3DPeruna is offline
Member
 
Join Date: Jan 2007
Posts: 50
Thanks: 8
Thanked 0 Times in 0 Posts
Default

Quote:
Code:
/etc/init.d/saslauthd restart?
The output is:

Code:
Stopping SASL Authentication Daemon: (not running).
Starting SASL Authentication Daemon: (failed).
Quote:
What's the output of
Code:
ps aux | grep saslauthd
afterwards?
Code:
root      5441  0.0  0.0   6948   764 ?        Ss   May18   0:00 /usr/sbin/saslauthd -a pam
root      5442  0.0  0.0   6948   480 ?        S    May18   0:00 /usr/sbin/saslauthd -a pam
root      5443  0.0  0.0   6948   456 ?        S    May18   0:00 /usr/sbin/saslauthd -a pam
root      5444  0.0  0.0   6948   456 ?        S    May18   0:00 /usr/sbin/saslauthd -a pam
root      5445  0.0  0.0   6948   456 ?        S    May18   0:00 /usr/sbin/saslauthd -a pam
root     19992  0.0  0.0   3964  1836 pts/0    T    May18   0:00 nano /ete/default/saslauthd
root     22499  0.0  0.1   8088  2888 pts/0    S+   May20   0:00 saslauthd -a pam -n 5 -V -c -m /var/spool/postfix/var/run/saslauthd -r -d
root     22501  0.0  0.0   8088  1448 pts/0    S+   May20   0:00 saslauthd -a pam -n 5 -V -c -m /var/spool/postfix/var/run/saslauthd -r -d
root     22505  0.0  0.0   8088  1468 pts/0    S+   May20   0:00 saslauthd -a pam -n 5 -V -c -m /var/spool/postfix/var/run/saslauthd -r -d
root     22507  0.0  0.0   8088  1260 pts/0    S+   May20   0:00 saslauthd -a pam -n 5 -V -c -m /var/spool/postfix/var/run/saslauthd -r -d
root     22510  0.0  0.0   8088  1260 pts/0    S+   May20   0:00 saslauthd -a pam -n 5 -V -c -m /var/spool/postfix/var/run/saslauthd -r -d
ohdweb   28626  0.0  0.0   3008   784 pts/2    R+   13:00   0:00 grep saslauthd
Reply With Quote
  #9  
Old 22nd May 2009, 16:27
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,711
Thanks: 1,899
Thanked 2,702 Times in 2,545 Posts
Default

Hm, saslauthd seems to be running already.
Can you run
Code:
killall saslauthd
and then start saslauthd?
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
The Following User Says Thank You to falko For This Useful Post:
3DPeruna (22nd May 2009)
  #10  
Old 22nd May 2009, 17:55
3DPeruna 3DPeruna is offline
Member
 
Join Date: Jan 2007
Posts: 50
Thanks: 8
Thanked 0 Times in 0 Posts
 
Default

Code:
saslauthd(5441): Operation not permitted
saslauthd(5442): Operation not permitted
saslauthd(5443): Operation not permitted
saslauthd(5444): Operation not permitted
saslauthd(5445): Operation not permitted
saslauthd: no process killed
SORRY: Forgot to SUDO. Killed the processes and restarted. Looks good!

Last edited by 3DPeruna; 22nd May 2009 at 17:58. Reason: CODE 18 - User error.
Reply With Quote
Reply

Bookmarks

Tags
saslautd, smtp, upgrade

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
issues with ver3 causing me not to upgrade djtremors General 2 25th April 2009 00:46
debian upgrade broken.. apt-get stuck guthrie Installation/Configuration 3 31st March 2009 04:29
saslauthd problem: bind: Address already in use fitti70 Server Operation 4 14th May 2007 21:51
Couple issues with ispconfig 2.2.12 after Fiesty upgrade pyropoptrt Installation/Configuration 15 1st May 2007 20:37
2.2.0 upgrade issues themachine Installation/Configuration 1 27th March 2006 10:47


All times are GMT +2. The time now is 06:50.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.