From: Igor Brezac (no email)
Date: Thu Oct 06 2005 - 16:58:43 EDT
On Thu, 6 Oct 2005, Saltmarsh, Evan M wrote:
> Well good news and bad. I've determined that the saslauthd is crashing
> when the call is made, but the truss is cryptic in nature. Here is the
> tail end, don't know if it's helpful or not.
>
> 26866/2: getpid() = 26866
> [1]
> 26866/2: write(6, "8092010301\0 i\0\0\0 \0".., 148) = 148
> 26866/2: read(6, "16030104 B02\0", 7) = 7
> 26866/2: time() =
> 1128629768
> 26866/2: time() =
> 1128629768
> 26866/2: getpid() = 26866
> [1]
> 26866/2: read(6, "\0 F0301\0\01812 d R v Y".., 1088) = 1088
> 26866/2: Incurred fault #6, FLTBOUNDS %pc = 0xFEB9F95C
> 26866/2: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000008
> 26866/2: Received signal #11, SIGSEGV [default]
> 26866/2: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000008
>
What version of saslauthd do you use? Please email 'ldd saslauthd'.
-Igor
> Evan Saltmarsh
> UNIX Systems Administrator
> Information Technology Services
> Vanderbilt University
> Office: (615) 322-2156
> Cell: (615) 491-4115
>
> -----Original Message-----
> From: Andrew Morgan [mailto:]
> Sent: Thursday, October 06, 2005 3:03 PM
> To: Saltmarsh, Evan M
> Cc:
> Subject: Re: IMAP authentication via LDAPS
>
>
> On Thu, 6 Oct 2005, Saltmarsh, Evan M wrote:
>
>> I'm having trouble getting LDAPS to work with cyrus. We've been able
> to
>> get LDAPS to work using stunnel to encrypt the path, but if we change
>> the saslauthd.conf file to point to the LDAPS port, we get the
> following
>> in our syslog, and it appears the connection to the LDAP server is
> never
>> established.
>>
>>
>>
>> Oct 6 10:39:34 tst-srvr imaps[25773]: [ID 702911 auth.notice] door
> call
>> to saslauthd server failed: Interrupted system call
>>
>> Oct 6 10:39:39 tst-srvr imaps[25773]: [ID 702911 auth.notice] door
> call
>> to saslauthd server failed: Bad file number
>>
>>
>>
>> Anybody else have problems / suggestions on how to get LDAPS
>> authentication to work?
>
> Try running strace (linux) or truss (solaris) on the saslauthd master
> process and the cyrus master process. You'll want to have strace/truss
> follow forks. The system calls near these error message will probably
> expose the problem.
>
> Andy
> ----
> Cyrus Home Page: http://asg.web.cmu.edu/cyrus
> Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>
-- Igor ---- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
|
|
|