Internet Mail Gateway service stopping far too often

[robm]

Should I be worried about the following types of entries in the log? Most of the time the service is stopped. The problems seem to only occur with outbound messages -- 99%.

robm


SERIOUS ERROR Internet Mail (Outgoing ) 01.17.07 04:23:50
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 31763
Procedure trace follows:
-> msl_envelopeRcptNext
<- msl_envelopeRcptNext
-> msl_envelopeRcptNext
<- msl_envelopeRcptNext
-> msl_outputMime
-> msl:outputMime
-> im_ItemRef2FName
<- im_ItemRef2FName
-> msl_fileEncodeNmap_
-> im_CrNewTempItem
-> im_GetNewTempItemNum
<- im_GetNewTempItemNum
<- im_CrNewTempItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- msl_fileEncodeNmap_


SERIOUS ERROR Internet Mail (Outgoing ) 01.17.07 04:23:50
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x40049366]
/opt/scalix/lib/libom_er.so[0x40049665]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x400497ef]
[0xffffe420]
/opt/scalix/lib/libom_msl.so[0x4009b4e1]
/opt/scalix/lib/libom_msl.so[0x4009bc45]
/opt/scalix/lib/libom_msl.so[0x4009dff8]
/opt/scalix/lib/libom_msl.so[0x4009d74d]
/opt/scalix/lib/libom_msl.so[0x4009e438]
/opt/scalix/lib/libom_msl.so(msl_outputMime+0x74)[0x4009e5d4]
unix.out[0x804b646]
unix.out[0x804afe8]
/lib/tls/libc.so.6(__libc_start_main+0xe0)[0x4023a250]
unix.out[0x804a2e1]


SERIOUS ERROR Internet Mail (Outgoing ) 01.17.07 08:34:36
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 5926
Procedure trace follows:
-> msl_envelopeRcptNext
<- msl_envelopeRcptNext
-> msl_envelopeRcptNext
<- msl_envelopeRcptNext
-> msl_outputMime
-> msl:outputMime
-> im_ItemRef2FName
<- im_ItemRef2FName
-> msl_fileEncodeNmap_
-> im_CrNewTempItem
-> im_GetNewTempItemNum
<- im_GetNewTempItemNum
<- im_CrNewTempItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- msl_fileEncodeNmap_


SERIOUS ERROR Internet Mail (Outgoing ) 01.17.07 08:34:36
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x40049366]
/opt/scalix/lib/libom_er.so[0x40049665]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x400497ef]
[0xffffe420]
/opt/scalix/lib/libom_msl.so[0x4009b4e1]
/opt/scalix/lib/libom_msl.so[0x4009bc45]
/opt/scalix/lib/libom_msl.so[0x4009dff8]
/opt/scalix/lib/libom_msl.so[0x4009d74d]
/opt/scalix/lib/libom_msl.so[0x4009e438]
/opt/scalix/lib/libom_msl.so(msl_outputMime+0x74)[0x4009e5d4]
unix.out[0x804b646]
unix.out[0x804afe8]
/lib/tls/libc.so.6(__libc_start_main+0xe0)[0x4023a250]
unix.out[0x804a2e1]

[ScalixSupport]

Hi!

If you do an omstat -q error, it's likely you'll see a message there. If there's a corrupted
message in a queue that causes one of the services to abort, it will get moved to the error
queue after two more aborted attempts.

See if this post helps:
viewtopic.php?t=5146

Thanks,
Subir

[kanderson]

You can also check the poison queue. That's where mine ended up.

omstat -q poison.