Internet Mail Gateway OUTGOING keeps aborting

Discuss the Scalix web client

Moderators: ScalixSupport, admin

propagandhi
Posts: 81
Joined: Wed Sep 26, 2007 8:18 am

Internet Mail Gateway OUTGOING keeps aborting

Postby propagandhi » Wed Mar 18, 2009 8:34 pm

Recently, as in only two days ago, our scalix server's outgoing relay keeps aborting.

The following logs repeat every time that it happens:

SERIOUS ERROR Internet Mail (Outgoing ) Thu Mar 19 11:09:36 2009
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xb5)[0x88ab25]
/opt/scalix/lib/libom_er.so[0x88ae13]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x88af9f]
[0xa43420]
/opt/scalix/lib/libom_msl.so(msl_getRecipServiceList+0x19f)[0x1395ef]
Pid of logging process: 26382

^[[A
[root@primail ~]# tail -n 100 /var/opt/scalix/pl/s/logs/fatal


SERIOUS ERROR Internet Mail (Outgoing ) Thu Mar 19 09:58:26 2009
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 26608
Procedure trace follows:
-> tf_GetINT32
<- tf_GetINT32
-> tf_GetStrPtr
<- tf_GetStrPtr
-> tf_GetStrPtr
<- tf_GetStrPtr
-> tf_GetStrPtr
<- tf_GetStrPtr
-> tf_GetINT16
<- tf_GetINT16
-> Q_NamesMatch
<- Q_NamesMatch
-> nm_ParseORN
<- nm_ParseORN
-> mim_parse_address
<- mim_parse_address
Pid of logging process: 26608


SERIOUS ERROR Internet Mail (Outgoing ) Thu Mar 19 09:58:26 2009
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xb5)[0x424b25]
/opt/scalix/lib/libom_er.so[0x424e13]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x424f9f]
[0x885420]
/opt/scalix/lib/libom_msl.so(msl_getRecipServiceList+0x19f)[0x6bb5ef]
Pid of logging process: 26608


SERIOUS ERROR Internet Mail (Outgoing ) Thu Mar 19 10:32:24 2009
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 26614
Procedure trace follows:
-> tf_GetINT32
<- tf_GetINT32
-> tf_GetStrPtr
<- tf_GetStrPtr
-> tf_GetStrPtr
<- tf_GetStrPtr
-> tf_GetStrPtr
<- tf_GetStrPtr
-> tf_GetINT16
<- tf_GetINT16
-> Q_NamesMatch
<- Q_NamesMatch
-> nm_ParseORN
<- nm_ParseORN
-> mim_parse_address
<- mim_parse_address
Pid of logging process: 26614


SERIOUS ERROR Internet Mail (Outgoing ) Thu Mar 19 10:32:24 2009
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xb5)[0x424b25]
/opt/scalix/lib/libom_er.so[0x424e13]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x424f9f]
[0x885420]
/opt/scalix/lib/libom_msl.so(msl_getRecipServiceList+0x19f)[0x6bb5ef]
Pid of logging process: 26614


SERIOUS ERROR Internet Mail (Outgoing ) Thu Mar 19 11:09:36 2009
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 26382
Procedure trace follows:
-> tf_GetINT32
<- tf_GetINT32
-> tf_GetStrPtr
<- tf_GetStrPtr
-> tf_GetStrPtr
<- tf_GetStrPtr
-> tf_GetStrPtr
<- tf_GetStrPtr
-> tf_GetINT16
<- tf_GetINT16
-> Q_NamesMatch
<- Q_NamesMatch
-> nm_ParseORN
<- nm_ParseORN
-> mim_parse_address
<- mim_parse_address
Pid of logging process: 26382


SERIOUS ERROR Internet Mail (Outgoing ) Thu Mar 19 11:09:36 2009
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xb5)[0x88ab25]
/opt/scalix/lib/libom_er.so[0x88ae13]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x88af9f]
[0xa43420]
/opt/scalix/lib/libom_msl.so(msl_getRecipServiceList+0x19f)[0x1395ef]
Pid of logging process: 26382

This mail server was running perfectly for months, with no intervention whatsoever, and all of a sudden it has started doing this. On several occasions when it has happened, there will be one or two messages jammed in the UNIX queue. The only way to get them out is to stop the internet mail gateway service and remove them, after they stop being in the processed state.

Things run along merrily for a few hours and the whole process repeats itself.

Please I really need some help on this one.

We are running 11.4.3

babytux
Posts: 40
Joined: Wed Sep 26, 2007 2:30 am
Location: India

Postby babytux » Thu Mar 19, 2009 9:10 am

is there any similarity between messages which get stucked??
Babytux

schmoe90
Scalix
Scalix
Posts: 900
Joined: Mon May 07, 2007 11:51 am

Postby schmoe90 » Thu Mar 19, 2009 1:02 pm

Increase the logging level on the Internet gateway to 9, wait for it to abort, then look at it with omshowlog (not the fatal file, it's a cut down version of the logging).

You can just restart the gateway a few times, and the server will move the message to the POISON queue for you.


Return to “Scalix Web Access”



Who is online

Users browsing this forum: No registered users and 1 guest