l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2003 Mar 23 12:17

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Squirrel Mail Authentication Problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Squirrel Mail Authentication Problems

On Sun, Mar 23, 2003 at 01:14:23AM -0800, Ryan wrote:
> In /var/log/messages I see this line:
> Mar 22 06:54:33 the45 authdaemon: authdaemon: s_connect() failed: No
> such file or directory
> So it looks like the authdaemon isn't working correctly.


  I agree, that error message looks like authdaemon having problems.  The 
error message isn't particularly useful... the next thing I would do is
figure out what file s_connect is trying to open by:
strace -o /tmp/trace -s 1024 `pgrep authdaemon`

  Then try to do a imap log in, make sure that a new error appears in the
/var/log/messages, then stop the strace.  Open up the /tmp/trace and search
for "s_connect.*failed", then start scanning up from there maybe 100 to
2000 lines, to see what files the process was working with... you should 
see file names for any system calls.
  Investigate why any files it's using are missing...

  A second thing I would do is a google search in web and groups for

s_connect "No such file or directory"

to see if anyone else has reported this.

  Last thing would be grepping the source for s_connect to see what it
does, and why it would print a failed error message.

> What imapd do you use? I am using courier only because that is what SM
> recommends.

  I don't actually use IMAP, but looking over the package lists both of
these would be the first I would try:
  uw-imapd or courier-imap

> Do you know how to access the courier log?

Another thing you can do to track down what log files are in use by these
processes is:
for l in `pgrep authdaemon`; do echo $l; ls -l /proc/$l/fd/*; done

change "authdaemon" to the name of the courier process you want to check.
the things on the right of the '->' will be the files that the process
has open... it should be obvious which are log files.

      Mike Simons

  If you get some problems with 'pgrep' not being installed on your
system... just replace that part of the command with a list of process
ids you want to check.
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.