protocol failure communicating withUAL server during omtidyu

[heupink]

Hi all,

I am getting the following error while running omtidyu -u "heupink" -MB

Code: Select all

Group 5 error calling ual_recvreply
Error reason 32
System error calling ual_sendcommand
Error reason 9
omtidyu : [OM.BP 2007] Protocol failure communicating with UAL server


"omscan -Avfx -U heupink" gives no errors. I have followed all additional mailbox troubleshooting techniques that I know. (which is not that many, but meaning: clearing out imap cache for that user.

Outlook seems to work fine. In fatal, I see the following errors, after the omtidyu operation:

Code: Select all


SERIOUS ERROR           Local Client I(U/I Access    ) Thu Jul 12 15:01:01 2007
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 24405
Procedure trace follows:
  <- msl_getObjectFile
  -> msl_readMimeMessage_
  -> im_OpenItem
  -> sfl_OpenItem
  -> im_ItemRef2FName
  <- im_ItemRef2FName
  <- sfl_OpenItem
  <- im_OpenItem
  -> sfl_CloseItem
  <- sfl_CloseItem
  -> msl_readMessageHeaders
  <- msl_readMessageHeaders
  -> msl_readContentHeaders
  <- msl_readContentHeaders
  -> msl_readContentHeaders
  <- msl_readContentHeaders
User Name: mourik jan c. heupink / intech007, intech
Pid of logging process: 24405
  Last Msg Subject: [Fwd: Fwd: 3D-Echografie]
  Last Msg Sender: heupink/mourik jan/c//intech007/intech//////////////////%heupink, mouri
  Last Msg Id: 468B7D79.7030108(a)merit.unu.edu
  Last Msg DirectRef: 000174dd1577025e
  Last Folder: Scalix Recovered Items
  Last Ct RecNo: 1057


SERIOUS ERROR           Local Client I(U/I Access    ) Thu Jul 12 15:01:01 2007
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x40024366]
/opt/scalix/lib/libom_er.so[0x40024665]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x400247ef]
[0xffffe420]
/opt/scalix/lib/libom_msl.so[0x4052697f]
/opt/scalix/lib/libom_msl.so[0x4052679d]
/opt/scalix/lib/libom_msl.so(msl_readMimeMessage_+0x248)[0x4052655b]
/opt/scalix/lib/libom_msl.so(msl_readContainerOpenedParent+0x208)[0x40520d15]
/opt/scalix/lib/libom_ual.so(ual_GetMslData+0x1ba)[0x400cae82]
/opt/scalix/lib/libom_ual.so[0x400e80db]
/opt/scalix/lib/libom_ual.so(ual_PrepList+0xa76)[0x400e9683]
/opt/scalix/lib/libom_ual.so(ual_PrepareList+0x4c8)[0x400ea83b]
/opt/scalix/lib/libom_ual.so(ual_RecvReply+0x356)[0x4006b46c]
/opt/scalix/lib/libom_ual.so(ual_ProcessCommands+0xcf)[0x400ddd4b]
/opt/scalix/bin/ual.local[0x8049818]
/lib/tls/libc.so.6(__libc_start_main+0xd0)[0x4016d210]
/opt/scalix/bin/ual.local[0x8048d91]
User Name: mourik jan c. heupink / intech007, intech
Pid of logging process: 24405
  Last Msg Subject: [Fwd: Fwd: 3D-Echografie]
  Last Msg Sender: heupink/mourik jan/c//intech007/intech//////////////////%heupink, mouri
  Last Msg Id: 468B7D79.7030108(a)merit.unu.edu
  Last Msg DirectRef: 000174dd1577025e
  Last Folder: Scalix Recovered Items
  Last Ct RecNo: 1057


ERROR                   Browser       (Item_Browser  ) Thu Jul 12 15:01:01 2007
[OM.BP 2001] Group 5 error calling ual_recvreply
Error reason 32
Pid of logging process: 24404


ERROR                   Browser       (Item_Browser  ) Thu Jul 12 15:01:01 2007
[OM.BP 2004] System error calling ual_sendcommand
Error reason 9
Pid of logging process: 24404


SERIOUS ERROR           Browser       (Item_Browser  ) Thu Jul 12 15:01:01 2007
[OM.BP 2007] Protocol failure communicating with UAL server


Pid of logging process: 24404

The message with subject "[Fwd: Fwd: 3D-Echografie] " has already (succesfully, as far as I can tell) been deleted from this mailbox, INCLUDING the the scalix recovered items folder! (yet: in the error, it is still there)

Any ideas where to go now?

[heupink]

nobody even *read* my post..?

[jaime.pinto]

I see many posts here referring om_something utilities.

The fact is that the majority of users on this forum don't have a clue about what any of those scripts do, and like me seldom use any of them. There are just too many of them, and it can be overwhelming.

The scalix guys in general are the only ones who suggest using one or the other, and also the best prepared to respond to issues related to them. They have been quiet.

From my part I absolutely make a point to never use any om script if I can avoid, and I'd prefer if they could all be reconciled and combined into the sac GUI in no more then some 15 buttons. Personally, if you want to get on my good side please don't ask questions about om scripts, and when I have an issue, please don't ask me to use a om tool.

If you (and so many others) don't get an answer to your questions promptly is because it didn't come across anybody that know the answer yet. Just be patient.

[Richard Hall]

Hi heupink,

It does seem as though the omtidyu program is failing because it's having a problem generating the MIME structure for one particular message in the Recovery Folder.

One quick way to list all the messages in the RF is to use omtidyu in report mode:
omtidyu -B -u <user> -Tr -a 0 -R

If you want to clear everything out of the RF then run:
omtidyu -B -u <user> -Tr -a 0 -d -k

Cheers - Richard

[heupink]

Hi Richard,

thanks for the response!

After my initial post here, I deleted the message from the recovery folder, by making the folder visible, and then removing the message. Much to my surprise, omtidy STILL failed.

Then, today I read your reply, and decided to first give "omtidyu -u "heupink" -MB" another try. (you never know...)

And it finished succesfully! No idea why. The machine hasn't been rebooted or so, in fact: I haven't touched the server since my first post.

So, thanks for the reply, but the problem has automagically disappeared! :-)

Kind regards,
Mourik Jan