Error after password change

[Marcus.Becker]

Hi all!

Without any known change one of our SCALIX servers (11.4.6.5113, CE, ~8600 mailboxes ) acts weird:

when I expire a password, then if the user, using SWA, types in the old and new passwords he gets the message that
the user could not be found or the password is wrong.

Funny facts: the password is set correctly and this happens only in, hmm, let's say 95% of all cases.
The imap-logging (lvl 8 ):

22194 10:39:06.930 S: A1 NO AUTHENTICATE [X-SCALIX-EXPIRED] password expired, please change it
22194 10:39:06.931 S: * BYE IMAP Server not available
22194 10:39:06.931 IMAP4 Satellite Server exiting.
22217 10:39:15.918 S: A1 NO AUTHENTICATE [X-SCALIX-EXPIRED] password expired, please change it
22217 10:39:15.918 S: * BYE IMAP Server not available
22217 10:39:15.918 IMAP4 Satellite Server exiting.
22219 10:39:16.465 S: A1 NO LOGIN [X-SCALIX-EXPIRED] password expired, please change it
22219 10:39:16.465 C: A2 X-SCALIX-PASSWORD "expiredpw" "newpw"
22219 10:39:17.403 S: A2 OK X-SCALIX-PASSWORD completed, now connected to server.de
22219 10:39:17.403 C: A3 LOGOUT
22219 10:39:17.404 S: * BYE IMAP Server logging out
22219 10:39:17.404 S: A3 OK LOGOUT completed
22219 10:39:17.404 IMAP4 Satellite Server exiting.
22226 10:39:17.402 CS: S2 OK X-SCALIX-PASSWORD completed, now connected to server.de
22226 10:39:17.403 CC: S3 LOGOUT
22226 10:39:17.404 CS: S3 OK LOGOUT completed
22226 10:39:28.000 IMAP4 CORE Server exiting.

And: I checked the log.0 and found lots of the following entries ( the seemed to correspond the the above mentioned incidents)

imapCheckAndCreateCore: ^@Could not bind to socket ^@/var/opt/scalix/fs/s/temp/imap-core.51498^@ Error was: ^@Address already in use

Been hunting now for some days but I think I need your help...

Marcus

[ls-al]

check for special characters in the password. there are some known bugs.

[Marcus.Becker]

Unfortunately the error occured (in my case) even when using passwords without special characters...

[ls-al]

Regarding the mentioned imapCheckAndCreateCore error you could verify if it corresponds to the mailbox in question by running

Code: Select all

omshowu -O 51498

I would also check if other stale in.imap41d processes for this mailbox exist. Get the "system login" for the mailbox from omshowu. This is the UID for the user processes.

[Marcus.Becker]

I was able to reproduce the error with my own account and also took care that no old imapds were running.

Is this possibly some sort of timeout problem as the machine has a lot of mailboxes (~8500)? The load on the 8 core machine was not too high though. And, as I said, the password was changed correctly!

[ls-al]

Looks like Bug 14067 (closed as a duplicate for 10595 which is still Scalix internal). Probably not touched as its hard to reproduce.
Not sure how to deal with this at this point.

[Marcus.Becker]

Thank you anyway.