Hiya Mike.
Yes, it was due to DB corruption.
Imho, the busier the server is in terms of user managment, the more
chances you have for something go wrong with the DB.
Especially if access to BQ administration is granted to customers that
dont know exactly how to deal with the aplication and make mistakes,
force page reloads while saving something important like a user in BQ
(over and over again) and sometimes the DB goes nuts.
Well, you can get it back on track with a dbrecover but the funny thing
is that everything seems to be working normally until someone lets you
know that cant access his mbox, or cant login to FTP (sometimes we get
these calls ^ the number of clients we have... fun)
And then you know, the "usual" problem just striked back.
On a few machines we have running, we got only 1 case where this happens
constantly... It has over 2k users.
So far, apart from this little "mailscanner .lock" problem, the db
lockup issue seems to be solved.
Gustavo
mailing list escreveu:
> --- Gustavo Silva <pseudo (at mark) zbronx.com> wrote:
>
>
>> I started receiving the same message after doing the flat-file password
>> db upgrade procedure. Or it was a BIG coincidence =)
>> Anyway... Is this your case?
>>
>
> Why the conversion from /var/db to /etc/passwd and /etc/shadow? I searched the
> archive and saw something about db corruption but was not certain if this is
> the reason for the conversion.
>
>
> Mike
>
>
> ____________________________________________________________________________________
> You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
> http://tc.deals.yahoo.com/tc/blockbuster/text5.com
>
>