Page 1 of 1

Server not doing so good

Posted: Wed Apr 25, 2007 11:01 am
by netcomrade
Logs keep showing


[OM 24070] Debug message for Lab use :
imapSatAuthenticate:Could not register with Session Monitor. usr_Signon() returned: SIGNON LIMIT REACHED, errno: Success

SERIOUS ERROR IMAP Server Da(IMAP Server Pr) 04.25.07 10:19:04
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 21192
Procedure trace follows:
<- imapnotif_notificationUpdate
<- checkNotifications
-> checkNotifications
-> imapnotif_notificationUpdate
<- imapnotif_notificationUpdate
<- checkNotifications
-> checkNotifications
-> imapnotif_notificationUpdate
<- imapnotif_notificationUpdate
<- checkNotifications
-> checkNotifications
-> imapnotif_notificationUpdate
<- imapnotif_notificationUpdate
<- checkNotifications
-> checkNotifications
-> imapnotif_notificationUpdate

SERIOUS ERROR IMAP Server Da(IMAP Server Pr) 04.25.07 10:19:04
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x94dee6]
/opt/scalix/lib/libom_er.so[0x94e1e6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x94e38f]
/lib/tls/libpthread.so.0[0x1d0898]
in.imap41d[0x8062095]
in.imap41d[0x8069f52]
in.imap41d[0x805593a]
in.imap41d[0x8056810]
in.imap41d[0x8057884]
in.imap41d[0x8068d1e]
in.imap41d[0x8069a23]
in.imap41d[0x80639d9]
in.imap41d[0x8064f0b]
in.imap41d[0x80658d4]
/lib/tls/libc.so.6(__libc_start_main+0xd3)[0x2bdde3]
in.imap41d[0x804dff1]


[root@mt-adm2 ~]# omstat -s
Service Router Started 01:24:48 0
Local Delivery Started 01:24:48 0
Internet Mail Gateway Started 01:24:48 0
Sendmail Interface Started 01:24:49 0
Local Client Interface Enabled 01:24:49 0
Remote Client Interface Enabled 01:24:49 15
Test Server Started 01:24:49 0
Request Server Started 01:24:49 0
Print Server Started 01:24:49 0
Directory Synchronization Started 01:24:49 0
Bulletin Board Server Started 01:24:49 0
Background Search Service Started 01:24:49 0
Dump Server Started 01:24:49 0
CDA Server Started 01:24:49 0
POP3 interface Started 01:24:49 0
Omscan Server Started 01:24:49 0
Archiver Started 01:24:49 0
You have new mail in /var/spool/mail/root
[root@mt-adm2 ~]# omstat -a
PC Monitor Started NON-STOP 0
Directory Relay Server Started 01:24:47
Notification Server Started 01:24:47 0
Shared memory daemon Started NON-STOP
Notification Monitor Started NON-STOP
Session Monitor Started NON-STOP
Indexer Started NON-STOP
Stats Daemon Started NON-STOP
Container Access Monitor Started NON-STOP
Item Structure Server Stopped 03.30.07
Database Monitor Started 01:24:47
Licence Monitor Daemon Started NON-STOP
LDAP Daemon Started 01:24:47
Queue Manager Started NON-STOP
Item Delete Daemon Started NON-STOP
IMAP Server Daemon Started 01:24:47
SMTP Relay Started 01:24:47
Mime Browser Controller Started 01:24:47
Event Server Started 01:24:47

Posted: Wed Apr 25, 2007 3:46 pm
by Shredder
You will want to edit the general.cfg file kept in /var/opt/scalix/??/s/sys for Scalix 11 or /var/opt/scalix/sys/general.cfg for Scalix 10.

There is a line called IMAP_CONNECTION_LIMIT. Set that to something higher than what you have.

Then restart the IMAP server with omoff -d0 -w imap then omon imap

Shredder

Posted: Thu Apr 26, 2007 12:25 am
by netcomrade
It's already set to 500.. the config file states "note that many IMAP clients have several
# connections for each IMAP session.", however, we have less then 50 users on the system, i'll set to 2K and report back

Posted: Fri Jun 08, 2007 10:10 am
by vlaurenz
netcomrade wrote:It's already set to 500.. the config file states "note that many IMAP clients have several
# connections for each IMAP session.", however, we have less then 50 users on the system, i'll set to 2K and report back


Run: 'ps -ef |grep imap |wc -l'

If that returns a number much less than 500, then the signon limit isn't your issue.

Any resolution to this?

Posted: Wed Aug 29, 2007 3:50 pm
by blentini
I am having the same issue. Imap sessions are around 30

Posted: Thu Aug 30, 2007 4:41 am
by btisdall
I've had serious IMAP issues recently & one theory is that they were triggered by malformed messages hitting several accounts. It would be worth trying a:

Code: Select all

omtidyu -M -B -u username


on an affected account. If this proves successful you can then run:

Code: Select all

omtidyallu -M


on all mailboxes (you might prefer to do this outside office hours).