Fail start saslauthd

Discussion in 'Server Operation' started by satimis, May 29, 2008.

  1. satimis

    satimis Member

    Hi folks,


    Ubuntu 6.05 drake amd64


    $ sudo /etc/init.d/saslauthd start
    Code:
    Password:
    Starting SASL Authentication Daemon: (failed).
    

    $ tail /var/log/daemon.log
    Code:
    May 30 00:00:01 lampserver squid[4311]:         0 Objects expired. 
    May 30 00:00:01 lampserver squid[4311]:         0 Objects cancelled. 
    May 30 00:00:01 lampserver squid[4311]:         0 Duplicate URLs purged. 
    May 30 00:00:01 lampserver squid[4311]:         0 Swapfile clashes avoided. 
    May 30 00:00:01 lampserver squid[4311]:   Took 0.7 seconds (   0.0 objects/sec). 
    May 30 00:00:01 lampserver squid[4311]: Beginning Validation Procedure 
    May 30 00:00:01 lampserver squid[4311]:   Completed Validation Procedure 
    May 30 00:00:01 lampserver squid[4311]:   Validated 0 Entries 
    May 30 00:00:01 lampserver squid[4311]:   store_swap_size = 0k 
    May 30 00:00:01 lampserver squid[4311]: storeLateRelease: released 0 objects 
    
    Please advise where shall I check and how to fix the problem.


    TIA


    B.R.
    satimis
     
  2. topdog

    topdog Active Member

    That is the wrong log take a look at syslog
     
  3. satimis

    satimis Member

    Hi topdog,


    $ tail /var/log/syslog
    Code:
    May 30 01:17:01 lampserver /USR/SBIN/CRON[5148]: (root) CMD (   run-parts --report /
    etc/cron.hourly)
    May 30 01:29:53 lampserver cyrus/master[5151]: about to exec /usr/sbin/ctl_cyrusdb
    May 30 01:29:53 lampserver cyrus/ctl_cyrusdb[5151]: checkpointing cyrus databases
    May 30 01:29:53 lampserver cyrus/ctl_cyrusdb[5151]: archiving database file: /var/li
    b/cyrus/annotations.db
    May 30 01:29:53 lampserver cyrus/ctl_cyrusdb[5151]: archiving log file: /var/lib/cyr
    us/db/log.0000000001
    May 30 01:29:53 lampserver cyrus/ctl_cyrusdb[5151]: archiving database file: /var/li
    b/cyrus/mailboxes.db
    May 30 01:29:53 lampserver cyrus/ctl_cyrusdb[5151]: archiving log file: /var/lib/cyr
    us/db/log.0000000001
    May 30 01:29:53 lampserver cyrus/ctl_cyrusdb[5151]: done checkpointing cyrus databas
    es
    May 30 01:29:53 lampserver cyrus/master[3869]: process 5151 exited, status 0
    May 30 01:39:01 lampserver /USR/SBIN/CRON[5153]: (root) CMD (  [ -d /var/lib/php5 ] 
    && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -
    r -0 rm)
    
    Thanks


    B.R.
    satimis
     
  4. topdog

    topdog Active Member

    you need to get it at the exact moment you are starting saslauthd, all i see in this log is cyrus and cron
     
  5. satimis

    satimis Member

    Hi topdog,


    I'm completely lost on building this LAMP server (Server-2)


    Please allow me providing you the story of this LAMP server (Server-2) which building has been completed. There is no X running on it. It can send and receive mails by itself. I'm doing headless installation on another LAMP server (Server-1) connected on the same network.


    On booting "pass phrase" has to be provided before this LAMP server (Server-2) can start.

    Code:
    Server lampserver:443 (RSA)
    pass phrase:
    

    I can ssh connect this LAMP server (Server-2) on Server-1 running on Xterm;
    $ ssh -p 2222 192.168.0.52


    But it must be on port 2222 only. Then I can login users' accounts with their password.


    However I can't login SquirrelMail on Server-1 with the same password to users' accounts


    Nor on Evolution client running on Server-1;

    Authentication Type
    check for supported types - FAIL
    Code:
    Evolution Error
    Error which Checking Service
    could not connect POP server 192.168.0.52
    

    At the beginning /etc/init.d/saslauthd can't start (fail). After on /etc/default/saslauthd/ changed;
    PARAMS

    as;
    OPTIONS

    making the line reading as;
    Code:
    OPTIONS="-m /var/spool/postfix/var/run/saslauthd -r"
    
    then /etc/init.d/saslauthd started.


    After continued fiddling around the pending problem suddenly I found /etc/init.d/saslauthd failing to start.


    Now this LAMP server (Server-2) just freshly boots up.


    On Server-1
    ===========

    $ ps aux | grep saslauthd
    Code:
    root      4194  0.0  0.1  29244  1160 ?        Ss   08:49   0:00 /usr/sbin/sasla
    uthd -a pam
    root      4195  0.0  0.0  29244   740 ?        S    08:49   0:00 /usr/sbin/sasla
    uthd -a pam
    root      4196  0.0  0.0  29244   672 ?        S    08:49   0:00 /usr/sbin/sasla
    uthd -a pam
    root      4197  0.0  0.0  29244   672 ?        S    08:49   0:00 /usr/sbin/sasla
    uthd -a pam
    root      4198  0.0  0.0  29244   672 ?        S    08:49   0:00 /usr/sbin/sasla
    uthd -a pam
    satimis   4446  0.0  0.0   3940   904 pts/0    S+   08:56   0:00 grep saslauthd
    
    I suppose it is running ?


    $ tail /var/log/syslog
    Code:
    May 30 09:17:01 lampserver /USR/SBIN/CRON[4458]: (root) CMD (   run-parts --report /etc/cron.hourly)
    May 30 09:19:49 lampserver cyrus/master[4459]: about to exec /usr/sbin/ctl_cyrusdb
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: checkpointing cyrus databases
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: archiving database file: /var/lib/cyrus/annotations.db
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: archiving log file: /var/lib/cyrus/db/log.0000000001
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: archiving database file: /var/lib/cyrus/mailboxes.db
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: archiving log file: /var/lib/cyrus/db/log.0000000001
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: done checkpointing cyrus databases
    May 30 09:19:49 lampserver cyrus/master[3881]: process 4459 exited, status 0
    May 30 09:39:01 lampserver /USR/SBIN/CRON[4463]: (root) CMD (  [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm)
    
    It seems nothing mentioned on saslauthd.


    $ sudo /etc/init.d/saslauthd stop
    Code:
    Password:
    Stopping SASL Authentication Daemon: (not running).
    

    $ sudo /etc/init.d/saslauthd start
    Code:
    Starting SASL Authentication Daemon: (failed).
    

    $ tail /var/log/syslog
    Code:
    May 30 09:17:01 lampserver /USR/SBIN/CRON[4458]: (root) CMD (   run-parts --report /etc/cron.hourly)
    May 30 09:19:49 lampserver cyrus/master[4459]: about to exec /usr/sbin/ctl_cyrusdb
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: checkpointing cyrus databases
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: archiving database file: /var/lib/cyrus/annotations.db
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: archiving log file: /var/lib/cyrus/db/log.0000000001
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: archiving database file: /var/lib/cyrus/mailboxes.db
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: archiving log file: /var/lib/cyrus/db/log.0000000001
    May 30 09:19:49 lampserver cyrus/ctl_cyrusdb[4459]: done checkpointing cyrus databases
    May 30 09:19:49 lampserver cyrus/master[3881]: process 4459 exited, status 0
    May 30 09:39:01 lampserver /USR/SBIN/CRON[4463]: (root) CMD (  [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm)
    

    $ ps aux | grep saslauthd
    Code:
    root      4194  0.0  0.1  29244  1160 ?        Ss   08:49   0:00 /usr/sbin/saslauthd -a pam
    root      4195  0.0  0.0  29244   740 ?        S    08:49   0:00 /usr/sbin/saslauthd -a pam
    root      4196  0.0  0.0  29244   672 ?        S    08:49   0:00 /usr/sbin/saslauthd -a pam
    root      4197  0.0  0.0  29244   672 ?        S    08:49   0:00 /usr/sbin/saslauthd -a pam
    root      4198  0.0  0.0  29244   672 ?        S    08:49   0:00 /usr/sbin/saslauthd -a pam
    satimis   4554  0.0  0.0   3944   908 pts/0    S+   10:01   0:00 grep saslauthd
    

    $ su - root
    Password:
    $ su - satimis
    etc.

    all work without problem.


    B.R.
    satimis
     
  6. satimis

    satimis Member

    Problem SOLVED

    Hi topdog and folks,


    I found my mistake on running;


    $ sudo 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.pid
    + test -f /usr/sbin/saslauthd
    + '[' -e /etc/default/saslauthd ']'
    + . /etc/default/saslauthd
    ++ START=yes
    ++ PARAMS='-m /var/spool/postfix/var/run/saslauthd -r'
    ++ MECHANISMS=pam
    + '[' yes '!=' yes ']'
    + '[' xpam = x ']'
    + PARAMS='-m /var/spool/postfix/var/run/saslauthd -r -a pam'
    + START='--start --quiet --pidfile /var/spool/postfix/var/run//saslauthd.pid --startas /usr/sbin/saslauthd --name saslauthd -- -m /var/spool/postfix/v
    ar/run/saslauthd -r -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.pid --startas /usr/sbin/saslauthd --name saslauthd -- -m /var/spoo
    l/postfix/var/run/saslauthd -r -a pam
    + start-stop-daemon --test --start --quiet --pidfile /var/spool/postfix/var/run//saslauthd.pid --startas /usr/sbin/saslauthd --name saslauthd -- -m /v
    ar/spool/postfix/var/run/saslauthd -r -a pam
    + echo '(failed).'
    (failed).
    + exit 1
    
    There is a problem on;
    Code:
    /var/spool/postfix/var/run//saslauthd.pid --startas 
    
    // before saslauthd.pid


    Then I found a typo on /etc/init.d/saslauthd on following line
    Code:
    PIDFILE="/var/spool/postfix/var/run/${NANE}/saslauthd.pid"
    
    After changing;
    NANE

    to;
    NAME


    $ sudo /etc/init.d/saslauthd restart
    Code:
    Stopping SASL Authentication Daemon: (not running).
    Starting SASL Authentication Daemon: saslauthd.
    
    My problem gone.


    Now I have to concentrate solving the problem on "login SM"


    B.R.
    satimis
     

Share This Page