--- On Thu, 6/18/09, Gerald Waugh <gwaugh (at mark) frontstreetnetworks.com> wrote:
> From: Gerald Waugh <gwaugh (at mark) frontstreetnetworks.com>
> Subject: [coba-e:15710] Re: db corrupt?
> To: coba-e (at mark) bluequartz.org
> Date: Thursday, June 18, 2009, 1:08 PM
> WebTent Support wrotre
> >
> > We are getting this message when I could not reset a
> user password and trying to restart sendmail, dovecot and
> dbrecover...
> >
> > [root (at mark) tpa-hosting ~]# /etc/init.d/dbrecover start
> > Checking consistency of user and group information...
> *** glibc detected *** double free or corruption (top):
> 0x080d56d0 ***
> > /etc/init.d/dbrecover: line 49: 3704
> Aborted
> $DBRECOVER -v -h $DBHOME >>$LOGFILE
> 2>&1
> > failed
>
> Should use
> /etc/init.d/ dbrecover stop
> /etc/init.d/ dbrecover start
>
> When attempting to change passwords, look at the following
> /var/log/admserv/adm_error for errors
> and
> /var/log/messages and grep for cced, look for errors
> and
> run makemap on /etc/init.d/virtusertahle (just to be
> sure it's OK)
>
> Gerald
>
Thanks Gerald, no errors when doing 'dbrecover stop', but same error when using start. When trying 'makemap hash /etc/mail/virtusertable.db < /etc/mail/virtusertable', nothing returned. The /var/log/messages has a lot of these...
Jun 18 13:28:57 tpa-hosting PAM_pwdb[11919]: check pass; user unknown
Also, if I grep cced, all seems to look good, but no logins are working. My messages log does not want to wrap lines, so all I can see is...
[root@tpa-hosting ~]# grep cced /var/log/messages|tail -25
Jun 18 13:30:30 tpa-hosting cced(smd)[17313]: client 0:[0:17273]: SET 838 . Di
Jun 18 13:30:30 tpa-hosting cced(smd)[17313]: client 0:[0:17273]: SET succeeded
Jun 18 13:30:30 tpa-hosting cced(smd)[17313]: client 0:[0:17273]: SET 838 . Di
Jun 18 13:30:30 tpa-hosting cced(smd)[17313]: client 0:[0:17273]: SET succeeded
Jun 18 13:30:30 tpa-hosting cced(smd)[17316]: client [0:17273] has admin rights
Jun 18 13:30:31 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET 17 . Dis
Jun 18 13:30:31 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET succeeded
Jun 18 13:30:31 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET 17 . mys
Jun 18 13:30:31 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET succeeded
Jun 18 13:30:32 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET 17 . Net
Jun 18 13:30:32 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET succeeded
Jun 18 13:30:33 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET 17 . Adm
Jun 18 13:30:33 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET succeeded
Jun 18 13:30:34 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET 17 . RAI
Jun 18 13:30:34 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET succeeded
Jun 18 13:30:35 tpa-hosting cced(smd)[17382]: client [0:17378] has admin rights
Jun 18 13:30:35 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET 17 . SMA
Jun 18 13:30:35 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET succeeded
Jun 18 13:30:36 tpa-hosting cced(smd)[17394]: client [0:17392] has admin rights
Jun 18 13:30:36 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET 17 . DMA
Jun 18 13:30:36 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET succeeded
Jun 18 13:30:36 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET 17 . Dis
Jun 18 13:30:36 tpa-hosting cced(smd)[17008]: client 0:[0:16976]: SET succeeded
Jun 18 13:30:36 tpa-hosting cced(smd)[17402]: client [0:16976] has admin rights
Jun 18 13:30:37 tpa-hosting cced(smd)[17411]: client [0:16976] has admin rights
If you believe we will need to start restores to another server, can you tell me how I can get eth0 to stay down? It keeps starting back on its own.
Thanks again, Robert