Standard User Account Becomes Locked

[seankoshy]

Hello,

Running community edition 11.1 on OpenSuse 10.1
Running into the problem of random standard user accounts becoming locked. I find out when the user cannot login, then I find out in the SAC that the user has become locked somehow. Any ideas as to how this happens?

Thanks,

Sean

[chris]

I know it's silly, but is it possible that the users are entering the wrong password multiple times?

You can find the bad password count with omsearch -e UL-BADPWD=* -s -t h -d userlist.

That's certainly the first thing I'd check.

Chris

[jaime.pinto]

Every now and then I have this problem with some user: the system simply reports that the password is not correct, which is obviously not true.

My solution has been very nasty, because it affects all other users:
1) omshowu -n "user" -f
2) cd g00003e/ (or whatever)
3) rm -rf 00000v8.ofs imap-cache
4) omscan -Avfx -U "user/mailnode
5) then omshut and omrc (this is the bad part)"
6) I still do another restart or the DB and tomcat

[seankoshy]

Still locking random accounts ... one was locked today - and I checked to see if there was bad password attempts - and there were none for the locked user. Any other ideas? Thanks,

Sean

[seankoshy]

Also ... is there a command I could use to get a list of locked accounts? Thanks,

Sean

[massspec]

Same here. I have two users who are locked out for no apparent reason, and I can't see how to reset them.

I also don't understand the solution above. I am new to administrating Scalix, and could use a hand with those instructions specifcally this part

g00003e/ (or whatever)

And why is omshut and omrc so bad for the other users?

Thanks

[jaime.pinto]

And why is omshut and omrc so bad for the other users?

That will stop the scalix server and start again. The shutdown process can take upwards of a few minutes, and kick out some users that were online, as well as keeping other from loging in.

In earlier releases there appear to have been a ommaint script installed on the crontab of the system, and this would run on a regular basis in a more proactive way, doing preventive housekeeping on user's mailboxes. Since release 11.0.4 I have no longer seen this script run, and the usual reports mailed to me. That's when I started to see this lockup symptoms happening more often.

So, what about the ommaint installation? Why isn't there anymore?

[massspec]

I still don't see how the solution that you describe works.

What does this mean?

"g00003e/ (or whatever)"

Thanks for your reply. This is locking up of accounts is not a good problem...

[jaime.pinto]

When you give the command omshowu -n "user" -f for a particular user, some information will be displayed about the location where the folders for that user are stored. The "g00003e" refers to the way Scalix identifies a user forder.

[mikethebike]

omsearch -d userlist -t h -e s=*/ul-type=primerecip/ul-flags=1 -m s/g/ou1 |omfmtent -x

will give you a list of locked users.

[seankoshy]

Hmm ... when i try to run the command it says '[OM 16954] Entry not in the Directory'

thanks for the help so far,

[mikethebike]

Sean,

thats probably a good thing...no accounts are locked.

lock your email account "ommodu -o "sean kosky" -K", and run that search again

Mick

[seankoshy]

Hey Mick,

Your help was much appreciated. Accounts still get locked once in a while, but this helps me finding out when; also there is another similar post to this where people are also having the same issues. Thanks again,

Sean

[Richard Hall]

A slightly easier way to find 'locked' users is:

Code: Select all

omshowu -m all -l

and then

Code: Select all

ommodu -o <user> -k

to unlock the user.

Richard