Page 1 of 1

Server Slows down

Posted: Tue Feb 13, 2007 2:35 pm
by sanjayacharya
Hello,

I have a scalix 11 Community server on Redhat AS 4. this server has about 500Users and the configuration is PIV 2GB with 400GB mirrored Drive.

Ever since this systems is made live I have noticed that every week the system startes to slow down , some times local delivery service stops, opening SAC becomes extremly slow. Even SSH to server is very slow. I eventually restart the server . After the restart everything works fine for about a week then again the server starts to slow down.

Any insights.

Sanjay

Posted: Sat Feb 17, 2007 1:18 pm
by florian
Can you give us any idea what generates the load? I.e. to know what top process shows up in the top output or so. Also, for local delivery, if you say it stops, what does omstat -s show for it's status? If it is in Aborted state, are there any indications why that's the case in omshowlog?

Florian.

Posted: Sat Feb 17, 2007 3:00 pm
by sanjayacharya
Hello florian,

Here is the Event log from SAC for local delivery.

ERROR Local Delivery(Local Delivery) 02.16.07 01:09:35
[OM 24520] The PDL contains no members, hence expansion will not occur.
Last Msg Id: 0000000205023607d7(a)(091)10.51.1.66(093)


ERROR Local Delivery(Local Delivery) 02.16.07 01:14:33
[OM 24520] The PDL contains no members, hence expansion will not occur.
Last Msg Id: 0000000205000207d7(a)(091)10.51.1.66(093)


SERIOUS ERROR Local Delivery(Local Delivery) 02.16.07 10:16:35
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 492
Procedure trace follows:
<- im_ItemRef2FName
-> msl_itemEncodeNmap_
-> im_OpenItem
-> sfl_OpenItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- sfl_OpenItem
<- im_OpenItem
-> sfl_CloseItem
<- sfl_CloseItem
-> im_CrNewTempItem
-> im_GetNewTempItemNum
<- im_GetNewTempItemNum
<- im_CrNewTempItem
-> im_ItemRef2FName
<- im_ItemRef2FName
Last Msg Id: 494B21DF5F4681429D821D52138C6A64011CE8D5(a)lms-dc1.lms-pdc.com
Last Msg DirectRef: 0003a9a6a0e339c3


SERIOUS ERROR Local Delivery(Local Delivery) 02.16.07 10:16:35
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0xfcdee6]
/opt/scalix/lib/libom_er.so[0xfce1e6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0xfce38f]
/lib/tls/libpthread.so.0[0x4497c8]
/opt/scalix/lib/libom_inet.so(inet_bin2base64f+0x4f)[0xfab8cf]
/opt/scalix/lib/libom_msl.so(msl_itemEncodeNmap_+0x289)[0xdfa1d9]
/opt/scalix/lib/libom_msl.so[0xdff99a]
/opt/scalix/lib/libom_msl.so[0xe000a7]
/opt/scalix/lib/libom_msl.so[0xe0146f]
/opt/scalix/lib/libom_msl.so[0xe0230c]
/opt/scalix/lib/libom_msl.so[0xe01c9e]
/opt/scalix/lib/libom_msl.so[0xe0294c]
/opt/scalix/lib/libom_msl.so(msl_outputMime+0x6d)[0xe02a3d]
/opt/scalix/lib/libom_msl.so(msl_readContainerOpenedParent+0x3cb)[0xe0e25b]
local.delivery[0x804efdd]
local.delivery[0x8059ac7]
local.delivery[0x80534a6]
local.delivery[0x805cfa9]
local.delivery[0x805eca1]
local.delivery[0x805f949]
/lib/tls/libc.so.6(__libc_start_main+0xd3)[0x2e9e23]
local.delivery[0x804dce1]
Last Msg Id: 494B21DF5F4681429D821D52138C6A64011CE8D5(a)lms-dc1.lms-pdc.com
Last Msg DirectRef: 0003a9a6a0e339c3

Posted: Sat Feb 17, 2007 3:54 pm
by florian
this looks like message store corrupion. Unfortunately, it does not point to a particular user. So you're probably best off to run the

Code: Select all

omscan -Aafv


command to check and potentially repair consistency of your message store at the next possible occasion. You can do this while the system is being used, just be aware that there will be additional load and it might have performance implications for your users.

Cheers,
Florian.

local del;ivery abort

Posted: Sun Feb 18, 2007 1:01 pm
by mikethebike
You could also look in the Service router audit log and search for that message-id, that may help identify the recipient(s). Then run an omscan against those user(s) as Florian suggests.

Mick

Posted: Wed Mar 21, 2007 12:33 pm
by sanjayacharya
I continue to have the server slow down issue and local service failing.

I get this error in my local Delivery

SERIOUS ERROR Local Delivery(Local Delivery) 03.20.07 15:50:14
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 22639
Procedure trace follows:
<- im_ItemRef2FName
-> msl_itemEncodeNmap_
-> im_OpenItem
-> sfl_OpenItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- sfl_OpenItem
<- im_OpenItem
-> sfl_CloseItem
<- sfl_CloseItem
-> im_CrNewTempItem
-> im_GetNewTempItemNum
<- im_GetNewTempItemNum
<- im_CrNewTempItem
-> im_ItemRef2FName
<- im_ItemRef2FName
Last Msg Id: 20070320234445.0026C60C3A4(a)eq2.spamarrest.com
Last Msg DirectRef: 0006cf5583f48292


SERIOUS ERROR Local Delivery(Local Delivery) 03.20.07 15:50:14
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0xfc9ee6]
/opt/scalix/lib/libom_er.so[0xfca1e6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0xfca38f]
/lib/tls/libpthread.so.0[0x4497c8]
/opt/scalix/lib/libom_msl.so(msl_itemEncodeNmap_+0x25e)[0x5601ae]
/opt/scalix/lib/libom_msl.so[0x56599a]
/opt/scalix/lib/libom_msl.so[0x5660a7]
/opt/scalix/lib/libom_msl.so[0x56746f]
/opt/scalix/lib/libom_msl.so[0x56830c]
/opt/scalix/lib/libom_msl.so[0x567c9e]
/opt/scalix/lib/libom_msl.so[0x56894c]
/opt/scalix/lib/libom_msl.so(msl_outputMime+0x6d)[0x568a3d]
/opt/scalix/lib/libom_msl.so(msl_readContainerOpenedParent+0x3cb)[0x57425b]
local.delivery[0x804efdd]
local.delivery[0x8059ac7]
local.delivery[0x80534a6]
local.delivery[0x805cfa9]
local.delivery[0x805eca1]
local.delivery[0x805f949]
/lib/tls/libc.so.6(__libc_start_main+0xd3)[0xd0de23]
local.delivery[0x804dce1]
Last Msg Id: 20070320234445.0026C60C3A4(a)eq2.spamarrest.com
Last Msg DirectRef: 0006cf5583f48292


ERROR Local Delivery(Local Delivery) 03.20.07 23:31:13
[OM 24520] The PDL contains no members, hence expansion will not occur.
Last Msg Id: 20070321-11260065-318-1(a)euclid-infotech1

Re: Server Slows down

Posted: Mon Jun 28, 2010 5:34 pm
by m15t1k0
Hello, I'm having the same issue, has anyone been able to figure out what seems to be the problem? I tried the Omscan but it lasted a couple of days OK then slowliness again. Thnx.