Local Delivery Dies

[kluss0]

I have a strang issue... Whenever someone sends an e-mail to any of my PDL's, Local Delivery dies, and I need to kill and restart it several times until the message is moved into the poison queue and life goes on. Some people recieve the e-mail, but others don't, and local delivery dies with:

SERIOUS ERROR Local Delivery(Local Delivery) 07.16.06 13:06:29
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 7553
Procedure trace follows:
<- /build/10.0.1.3/src/lib/ombase/sfl/sfl_Blcked.c
<- /build/10.0.1.3/src/lib/ombase/sfl/sfl_Blcked.c
<- /build/10.0.1.3/src/lib/ombase/sfl/sfl_Blcked.c
<- /build/10.0.1.3/src/lib/ombase/sfl/sfl_Blcked.c
-> im_OpenItem
-> sfl_OpenItem
-> im_ItemRef2FName
<- im_ItemRef2FName
-> sfl_OpenSfl
-> im_OpenItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- im_OpenItem
<- sfl_OpenSfl
<- sfl_OpenItem
<- im_OpenItem
Last Msg Id: 6768.10451153069586
Last Msg DirectRef: 000c9c5765550242


SERIOUS ERROR Local Delivery(Local Delivery) 07.16.06 13:06:29
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x3e1f06]
/opt/scalix/lib/libom_er.so[0x3e21d6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x3e237f]
/lib/tls/libpthread.so.0[0x1ca8b8]
/opt/scalix/lib/libom_ct.so(ct_GetDIData+0x137)[0x75b314]
/opt/scalix/lib/libom_ct.so(PendOpenCtner+0x3b0)[0x7751ab]
/opt/scalix/lib/libom_ct.so(PendDelete+0x1d1)[0x774a19]
/opt/scalix/lib/libom_ct.so(CloseCtner+0x2ea)[0x7607b5]
/opt/scalix/lib/libom_ct.so(ct_CloseCtner+0x5d)[0x751249]
local.delivery[0x804eb36]
local.delivery[0x805a92f]
local.delivery[0x8052ffd]
local.delivery[0x805db61]
local.delivery[0x805f9a6]
local.delivery[0x8060648]
/lib/tls/libc.so.6(__libc_start_main+0xe3)[0x1002e33]
local.delivery[0x804d841]
Last Msg Id: 6768.10451153069586
Last Msg DirectRef: 000c9c5765550242

I am running v10.0.1. This just started Friday night. I have a hack in place right now that re-starts local delivery every minute, but I can't keep that up forever. Has anyone else seen this?

Thanks,
Kenny

[ScalixSupport]

Hi,

Try running

Code: Select all

omscan -f -a > /tmp/omscan.out

And see if that helps in any way.

Cheers,
Yuri

[mikethebike]

Are those the only entries from the fatal log?
It may be worth checking to see if one of the recipients either has a bad Inbox (or even the Inbox file missing....the user*/g*/*1 file)

[kluss0]

Try running
Code:
omscan -f -a > /tmp/omscan.out



And see if that helps in any way.

That went tremendiously badly....... It uncovered many, *MANY* missing children. However, now I have people whose mail stores are corrupt, there are folders missing from peoples mail, etc. I, myself, am missing all mail from before Friday....

[ScalixSupport]

Hi,

That was a passive scan that does not remove anything from your message store. You could try doing an active scan but you need to shut down the server to do so. To do an active scan you need to shut down scalix server first then run the following command while the server is shut down.

Code: Select all

omscan -a -A -f

Please run 'man omscan' to read about the purpose of omscan.

Cheers,
Yuri

[kluss0]

Hi Yuri,

That was a passive scan that does not remove anything from your message store.

The -a is passive, but the -f is not. From the man page (which I have read many times):

-f Check/Scan the area selected and fix inconsistencies found (e.g. delete references, files, and Directories, and move orphan files and incomplete messages).

Which means that in all likelyhood, it deleted any inconsistencies. That accounts for all of the missing e-mail...

[ScalixSupport]

Hi,

Can you provide your fatal log, your omscan command output (from the passive mode you ran earlier). Also check you /var/log/messages, and the output of the dmesg command.

That should give us something to work with.

Cheers,
Yuri

[kluss0]

I called in earlier and turned this into a support issue because of the depth of the issue.

Thanks,
Kenny