From: Andreas Winkelmann (mlawinkelmann.de)
Date: Fri Jan 06 2006 - 12:39:06 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Am Thursday 05 January 2006 10:39 schrieb newbie:

> >>>Show "ps aux|grep saslauthd", please.
> >>
> >># ps aux|grep saslauthd
> >>root 29253 0.0 0.4 4436 1268 ? Ss 14:54 0:00
> >>saslauthd -a pam -V -r -n 0
> >
> > Looks good. Ok, stop saslauthd, start it in a shell with an additional
> > "-d". And use another shell with testsaslauthd. Show the Output of
> > "saslauthd -d...".
>
> # saslauthd -a pam -V -r -n 0 -d
> saslauthd[6834] :main : num_procs : 0
> saslauthd[6834] :main : mech_option: NULL
> saslauthd[6834] :main : run_path : /var/run/saslauthd
> saslauthd[6834] :main : auth_mech : pam
> saslauthd[6834] :detach_tty : master pid is: 0
> saslauthd[6834] :ipc_init : listening on socket:
> /var/run/saslauthd/mux
> saslauthd[6834] :do_auth : auth failure: [user=toto]
> [service=smtp] [realm=] [mech=pam] [reason=PAM acct error]
>
> And here is the output of the mysql log :
> 82 Query SELECT password FROM users WHERE userid = 'toto'

Hmm, please try it with a wrong password. Does there come "PAM acct error"? Or
"PAM auth error"?

> So it means that the request is reaching the db server and even that the
> request is correct. (I'm getting my password when I'm using that sql
> request directly in a mysql shell)
>
> The puzzeling thing here is that the output of saslauthd is quit too
> short, It's quite hard to debug without enough information ...

--
        Andreas

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]