UAL error on a user account

[RickC]

Hi,

I'm getting errors on a user account (mine) and have never seen these before. Not able to log on, so shelled to run some tools:

# omtidyu -B -u "richard chamberlain" -Twr -a0 -d -k
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

# omtidyu -B -u "Richard D. Chamberlain " -M
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

When I attempt these commands, the following errors are logged:

SERIOUS ERROR Local Client I(U/I Access ) Thu May 17 08:08:35 2012
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 23498
Procedure trace follows:
<- nf_Close
<- nf_EndSession
-> nf_EndSession
-> nf_Open
-> nf_Init
<- nf_Init
-> nf_GetFileName
-> nf_GetFileBaseName
<- nf_GetFileBaseName
-> nf_GetFileDir
<- nf_GetFileDir
<- nf_GetFileName
<- nf_Open
-> nf_Close
<- nf_Close
<- nf_EndSession
User Name: Richard D. Chamberlain / mt/CN=Richard D Chamberlain
Pid of logging process: 23498


SERIOUS ERROR Local Client I(U/I Access ) Thu May 17 08:08:35 2012
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0xf7fecf26]
/opt/scalix/lib/libom_er.so[0xf7fed21d]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0xf7fed3bf]
[0xffffe500]
/opt/scalix/lib/libom_nf.so[0xf7bfb7d8]
[0x30322d3d]
User Name: Richard D. Chamberlain / mt/CN=Richard D Chamberlain
Pid of logging process: 23498


ERROR Browser (Item_Browser ) Thu May 17 08:08:35 2012
[OM.BP 2001] Group 5 error calling ual_recvreply
Error reason 32
Pid of logging process: 23497


ERROR Browser (Item_Browser ) Thu May 17 08:08:35 2012
[OM.BP 2004] System error calling ual_sendcommand
Error reason 9
Pid of logging process: 23497


SERIOUS ERROR Browser (Item_Browser ) Thu May 17 08:08:35 2012
[OM.BP 2007] Protocol failure communicating with UAL server


Pid of logging process: 23497


Any ideas? we are 'stuck' on 11.4.4 because we were asked not to upgrade due to the platform ...

Thanks,

RIck

[RickC]

Problem solved with a simple 'omshut' and 'omrc'. apparently some stale UAL & IMAP processes hanging around too long.

Rick

[florian]

in this case it may be sufficient to omoff/on remote client interface, and/or simply "kill" the respective ual.remote processes - omstat will even help you with the PID.

Florian.

[RickC]

Thanks Florian,

We've had tons of problems late last week, The CPU load was over 200, IMAP seems to have been out of control.

Do you know what processes run IMAP as root? What else could have caused that high load? The queues had over 3k email in them.

Thanks,

Rick

[florian]

imap rarely spins.

the most likely explanation is a high load on the queue processing (did you possibly get hit by a spam attack?), which led to high system load, which led the user agent processes to have a backlog in their transactions, and that's when IMAP - because of the large number of fine-grained transactions that the protocol itself is all about - becomes somewhat a pain in the ass.

probably not easy to follow through such discussion over forum, especially when no more factual data is available. either needs to be looked at as a matter of support case, or else.

cheers,
Florian.

[RickC]

Getting UAL errors again, very odd, I have not seen these in the past and all of a sudden getting them with user accounts. Any idea why I'm getting these at this time?

killing UAL-remote processes for user <user> (uid 61029) ...
removing /var/opt/scalix/c2/s/user01/g0000is/00000v8.ofs ...
recreating mailboxcache for keith long....
Group 5 error calling ual_recvreply
Error reason 32
System error calling ual_sendcommand
Error reason 9
sxmbcprep : [OM.BP 2007] Protocol failure communicating with UAL server

[RickC]

Tried resetting rci - no go.

omreset -o off rci
kill ual.remote processes
omon rci

same error. only effects some accounts, not all. No clue why some are affected and not others. On both my backend Scalix 11.4.4 servers.