POP3 interface Aborted

[chewynet]

Hi

I'm having terrible trouble with the Pop3 Interface service. It will accept one connection, then Aborts. I'm currently running it with Scalix 11.3U1 and Suse 10.2. I upgraded from Scalix 11.1 and Suse 10.2 where the same thing was happening.

I was port redirecting through stunnel but the same is happening even if I switch this off and use the standard port 110. I have the omconflvl at 17, but can see nothing in the logs telling why it is Aborting all the time.

If I run a

Code: Select all

omshowlog -e | grep -i -A 10 -B 10 pop

I only get messages about starting the pop3 service never about stopping it and
If I run a

Code: Select all

omshowlog -e | grep -i -A 10 -B 10 abort

I only get context about IMAP errors, a service which I have no problem with so I believe it is unrelated. For clarity of this post, I'll include those outputs at the end of the post.

I have tried omreset -o off pop3, followed by omon, but again it Aborts after one successful connection.

I can't see anything untoward in omsetsvc -r pop3 getting

Details for subsystem POP3 interface:
Service Number = 106
Number of components = 1
Logging Level = 7
Audit logging Level = 0
Has an input queue? - NO
Show details from omstat? - YES
Subsystem can be enabled? - YES
Required state - Enabled
Last state change (on/off) = 08:55:22
Last delayed off time =
Startup prog name = ~/bin/pop3.server
Shutdown program name = ~/bin/ompopadm -s -d %d
Status program name =
PID's of subsystem processes: 27045 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Nice Level = 0
Additional Resolve Flag = 0
Subsystem is controlled by 'all' - YES
Minimum temporary processes = 0
Maximum temporary processes = 0
Context dependent information: 0 0 0 0 0 0 0 0
Auxiliary processes = 0
PID's of auxiliary processes: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

And I happened latterly to inadventantly uninstall the service with omsetsvc -i pop3 but managed to reinstall it a per a previous post.

After all that it's still just Aborting.

Any ideas what could be causing this or how I can fix it, please?

Thanks

Patrick
----------------------

Output of omshowlog -e | grep -i -A 10 -B 10 pop.

--
<- aud_LogCurrentTime Administration(omon ) 02.07.08 08:55:22
-> aud_LogStr Administration(omon ) 02.07.08 08:55:22
<- aud_LogStr Administration(omon ) 02.07.08 08:55:22
-> aud_LogStr Administration(omon ) 02.07.08 08:55:22
<- aud_LogStr Administration(omon ) 02.07.08 08:55:22
-> aud_EndTransaction Administration(omon ) 02.07.08 08:55:22
<- aud_EndTransaction Administration(omon ) 02.07.08 08:55:22
<- con_AudLogStart Administration(omon ) 02.07.08 08:55:22

REPORT Administration(omon ) 02.07.08 08:55:22
[OM 10429] Subsystem POP3 interface started by root.

-> cvc_enhCnvString Administration(omon ) 02.07.08 08:55:22
-> cvc_iconvGetCharSetName Administration(omon ) 02.07.08 08:55:22
<- cvc_iconvGetCharSetName Administration(omon ) 02.07.08 08:55:22
-> cvc_iconvGetCharSetName Administration(omon ) 02.07.08 08:55:22
<- cvc_iconvGetCharSetName Administration(omon ) 02.07.08 08:55:22
-> cvc_CnvStringTryIconv Administration(omon ) 02.07.08 08:55:22
-> cvc_iconvGetCharSetName Administration(omon ) 02.07.08 08:55:22
<- cvc_iconvGetCharSetName Administration(omon ) 02.07.08 08:55:22
-> cvc_iconvGetCharSetName Administration(omon ) 02.07.08 08:55:22
--
<- aud_LogCurrentTime Administration(omon ) 02.07.08 10:06:01
-> aud_LogStr Administration(omon ) 02.07.08 10:06:01
<- aud_LogStr Administration(omon ) 02.07.08 10:06:01
-> aud_LogStr Administration(omon ) 02.07.08 10:06:01
<- aud_LogStr Administration(omon ) 02.07.08 10:06:01
-> aud_EndTransaction Administration(omon ) 02.07.08 10:06:01
<- aud_EndTransaction Administration(omon ) 02.07.08 10:06:01
<- con_AudLogStart Administration(omon ) 02.07.08 10:06:01

REPORT Administration(omon ) 02.07.08 10:06:01
[OM 10429] Subsystem POP3 interface started by root.

-> cvc_enhCnvString Administration(omon ) 02.07.08 10:06:01
-> cvc_iconvGetCharSetName Administration(omon ) 02.07.08 10:06:01
<- cvc_iconvGetCharSetName Administration(omon ) 02.07.08 10:06:01
-> cvc_iconvGetCharSetName Administration(omon ) 02.07.08 10:06:01
<- cvc_iconvGetCharSetName Administration(omon ) 02.07.08 10:06:01
-> cvc_CnvStringTryIconv Administration(omon ) 02.07.08 10:06:01
-> cvc_iconvGetCharSetName Administration(omon ) 02.07.08 10:06:01
<- cvc_iconvGetCharSetName Administration(omon ) 02.07.08 10:06:01
-> cvc_iconvGetCharSetName Administration(omon ) 02.07.08 10:06:01

Output of omshowlog -e | grep -i -A 10 -B 10 abort.

--


REPORT IMAP Server Da(IMAP Server Pr) 02.06.08 19:12:17
[OM 24070] Debug message for Lab use :
imapSatServer:Connected to server
User Name: Patrick Tuite / management/CN=Patrick Tuite


SERIOUS ERROR IMAP Server Da(IMAP Server Pr) 02.06.08 19:12:17
[OM 10270] Process about to terminate due to error.
Signal (Abort) trapped by process 21020
Procedure trace follows:
<- dr_ACIModContextFlags
-> cdl_IsOu1Hosting
<- cdl_IsOu1Hosting
-> dr_ACICheckReadPerm
<- dr_ACICheckReadPerm
-> dr_ACIModContextFlags
<- dr_ACIModContextFlags
-> mim_parse_address
<- mim_parse_address
--
Last Msg DirectRef: 00010a1891719dfe


SERIOUS ERROR IMAP Server Da(IMAP Server Pr) 02.06.08 19:12:17
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xb3)[0xf7e56d63]
/opt/scalix/lib/libom_er.so[0xf7e57053]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0xf7e571df]
[0xffffe500]
[0x6]
/lib/libc.so.6(abort+0x101)[0xf7a3f801]
/lib/libc.so.6(__assert_fail+0xfb)[0xf7a377bb]
/opt/scalix-libical/lib/libical.so.0[0xf76d7e5b]
/opt/scalix-libical/lib/libical.so.0[0xf76cdc2a]
/opt/scalix-libical/lib/libical.so.0(icaltimezone_get_builtin_timezone+0xfa)[0xf76cd85a]
/opt/scalix/lib/libom_mapi.so[0xf79e4e2a]
/opt/scalix/lib/libom_mapi.so(mapi_MakeIcalBodyParts+0x5e)[0xf79e98fe]
/opt/scalix/lib/libom_mapi.so(mapi_MakeNormalMapiPropEquivBodyParts+0xc5)[0xf79fe0e5]
/opt/scalix/lib/libom_mapi.so(mapi_MakeMapiPropBodyEquivs+0x2d9)[0xf79ff469]
/opt/scalix/lib/libom_mapi.so(mapi_ConvertMapiProps+0x83a)[0xf7a0166a]
/opt/scalix/lib/libom_msl.so[0xf7db72a3]

[chewynet]

Seems to have been the ssl=starttls directive in openldap, though why it should suddenly pose a problem after working for so long and then only affecting the POP3 service, I can't say.