On Mon, Jan 23, 2006 at 06:16:10AM -0800, Richard Broersma Jr wrote: > I've stopped then started the courier process over and logged the same error. > > Jan 23 05:44:06 [authdaemond] stopping authdaemond children > Jan 23 05:44:29 [authdaemond] modules="authpgsql authpam authuserdb > authshadow authcustom authpipe", daemons=5 > Jan 23 05:44:29 [authdaemond] Installing libauthpgsql > Jan 23 05:44:29 [authdaemond] Installation complete: authpgsql > Jan 23 05:44:29 [authdaemond] Installing libauthpam > Jan 23 05:44:29 [authdaemond] Installation complete: authpam > Jan 23 05:44:29 [authdaemond] Installing libauthuserdb > Jan 23 05:44:29 [authdaemond] Installation complete: authuserdb > Jan 23 05:44:29 [authdaemond] Installing libauthshadow > Jan 23 05:44:29 [authdaemond] Installation complete: authshadow > Jan 23 05:44:29 [authdaemond] Installing libauthcustom > Jan 23 05:44:29 [authdaemond] Installation complete: authcustom > Jan 23 05:44:29 [authdaemond] Installing libauthpipe > Jan 23 05:44:29 [authdaemond] Installation complete: authpipe > Jan 23 05:50:14 [pop3d] LOGIN FAILED, user=richard, ip=[::ffff:192.168.1.100] > Jan 23 05:50:14 [pop3d] authentication error: Input/output error
Those 'Installing' messages are logged at level 'INFO'. I still don't see any evidence that you are logging anything at level 'DEBUG'. You can test like this: # echo "Testing 123" | logger -p mail.debug Does this appear in your logs anywhere? If not, then you need to read all the documentation of your non-standard syslog daemon until you can find out how to make it record such messages. A quick google for metalog suggests you need facility = "mail" minimum = 7 <=== THIS logdir = "/var/log/mail" in order to get mail.debug recorded, but that's not tested by me. If you *do* see "Testing 123" logged without changing your metalog config, then are you sure you haven't compiled things so that pop3d expects authdaemond's socket to be somewhere different to where authdaemond creates it? To check: firstly run # authtest richard <password> If this still doesn't log any authdaemond messages, then try again using # strace authtest richard <password> and look for where authtest is opening the socket to authdaemond. If it fails, make a note of the path it is trying to open. Check whether this path exists. Regards, Brian. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
