Archiver Crashes

[maxpower]

Hi,

I've just recently installed Scalix Eval version. I have enabled archiving by adding ARCHIVE=TRUE in the general.cfg but every so often archiving just quits. Does anybody know what may be causing this? I have found the following in the fatal.log:

SERIOUS ERROR Archiver (Archiver ) Fri Nov 24 11:18:28 2006
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xb6)[0x11be76]
/opt/scalix/lib/libom_er.so[0x11c162]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x11c31f]
[0x2c4420]
/lib/libc.so.6(abort+0xf8)[0x30c678]
/lib/libc.so.6(__assert_fail+0xfd)[0x304269]
/usr/lib/libical.so.0[0x43867b]
/usr/lib/libical.so.0(icalproperty_new_uid+0x5c)[0x42eb9c]
/opt/scalix/lib/libom_mapi.so(mapi_MakeIcalBodyParts+0x131a)[0x260a6a]
/opt/scalix/lib/libom_mapi.so(mapi_MakeNormalMapiPropEquivBodyParts+0xf8)[0x272f88]
/opt/scalix/lib/libom_mapi.so(mapi_MakeMapiPropBodyEquivs+0x2d5)[0x273895]
/opt/scalix/lib/libom_msl.so[0x21eadf]
/opt/scalix/lib/libom_msl.so[0x222800]
/opt/scalix/lib/libom_msl.so[0x222360]
/opt/scalix/lib/libom_msl.so(msl_readQMessage+0x38d)[0x22309d]
archiver[0x804a12d]
archiver[0x8049e18]
/lib/libc.so.6(__libc_start_main+0xdf)[0x2f7d7f]
archiver[0x8049b11]
Pid of logging process: 19725


SERIOUS ERROR Archiver (Archiver ) Fri Nov 24 11:39:26 2006
[OM 10270] Process about to terminate due to error.
Signal (Abort) trapped by process 20349
Procedure trace follows:
<- mapixml_GetNextMAPIPropAndValue
-> mapixml_GetNextMAPIPropAndValue
<- mapixml_GetNextMAPIPropAndValue
-> mapixml_GetNextMAPIPropAndValue
<- mapixml_GetNextMAPIPropAndValue
-> mapixml_GetNextMAPIPropAndValue
<- mapixml_GetNextMAPIPropAndValue
-> mapixml_GetNextMAPIPropAndValue
<- mapixml_GetNextMAPIPropAndValue
-> mapixml_GetNextMAPIPropAndValue
<- mapixml_GetNextMAPIPropAndValue
-> mapixml_GetNextMAPIPropAndValue
<- mapixml_GetNextMAPIPropAndValue
-> mapixml_GetNextMAPIPropAndValue
<- mapixml_GetNextMAPIPropAndValue
-> mapi_MakeIcalBodyParts
Pid of logging process: 20349


SERIOUS ERROR Archiver (Archiver ) Fri Nov 24 11:39:26 2006
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xb6)[0x73be76]
/opt/scalix/lib/libom_er.so[0x73c162]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x73c31f]
[0x2c4420]
/lib/libc.so.6(abort+0xf8)[0x30c678]
/lib/libc.so.6(__assert_fail+0xfd)[0x304269]
/usr/lib/libical.so.0[0x43867b]
/usr/lib/libical.so.0(icalproperty_new_uid+0x5c)[0x42eb9c]
/opt/scalix/lib/libom_mapi.so(mapi_MakeIcalBodyParts+0x131a)[0x24ca6a]
/opt/scalix/lib/libom_mapi.so(mapi_MakeNormalMapiPropEquivBodyParts+0xf8)[0x25ef88]
/opt/scalix/lib/libom_mapi.so(mapi_MakeMapiPropBodyEquivs+0x2d5)[0x25f895]
/opt/scalix/lib/libom_msl.so[0x15aadf]
/opt/scalix/lib/libom_msl.so[0x15e800]
/opt/scalix/lib/libom_msl.so[0x15e360]
/opt/scalix/lib/libom_msl.so(msl_readQMessage+0x38d)[0x15f09d]
archiver[0x804a12d]
archiver[0x8049e18]
/lib/libc.so.6(__libc_start_main+0xdf)[0x2f7d7f]
archiver[0x8049b11]
Pid of logging process: 20349

[anand_joshi]

HI ,

The error did not let me to know the actual cause of the problem , but as far as archive concern ARCHIVE=TRUE Enables the archiving of all messages that traverse the Scalix Server. Messages are archived to the ~scalix/archive directory.
arch:/path/ will you to enable the archvie the location for archive the messages where ever you want to archive . Make sure to have a proper permission to this directory
becasue The Archiver process operates as the user “scalixâ€

[gren]

Dear maxpower.

I suspect that you have a message on your ARCHIVE queue which is causing the Archiver problems. Could you please use omqdump to dump the first message on the ARCHIVE queue to files and then create a bug at http://bugzilla.scalix.com with the files as attachments? Also, the omshowlog output from your comment would be useful in that bug report.

omqdump's password is 'A##E' where ## is the current day of the month + 10.
Use the "g" command to GET the message from the queue.
Use the "o" command to output the open message to files.

For convenience, you might want to tar up and gzip the files, so you only need to attach one thing to the bug.

It is possible that after several failures, the Archiver may have spotted that the first message was causing it problems and moved it to the POISON queue, so if there are no message on the ARCHIVE queue or the problem seems to have resolved itself, please check for messages on the POISON queue (also worth looking at the ERROR and SMERR queues).

I would really appreciate this information as it will allow us to identify the cause of the problem and hopefully make the archiver more robust.

Thanks and regards,
Gren.

[dkelly]

What version of the server are you using ?

The Archiver uses the same libraries as the outgoing unix gateway and we've seen this problem before on earlier versions of the 10.x server.

We have a new patch that should be available in the next couple of days that is likely to fix this issue but I need to know the version you are currently on.

Cheers

Dave

[maxpower]

Thanks for all the replies. The version is 10.0.1.21. It does seem to be a problem with a certain message as it hasn't happened again. However, now I am unable to archive to a different folder. I modified the general.cfg file to have ARCHIVE=arch:/backups/archive/ where /backups is a different drive on the machine. However when I do this nothing is actually written

[maxpower]

Never mind about the archive folder location. Classic permissions issue