Suddenly it is working again. !!! I dont think it has anything to do with
saslauthd !!!
I can se that db_checkpoint.pl runs at:
03,18,33,48 * * * * root /usr/sausalito/sbin/db_checkpoint.pl
Here are the logs: (sorry for the long list folks!)
tail -f -n500 /var/log/dbrecover.log | more
[Wed May 21 12:08:21 CEST 2008] Trying db_recover
db_recover: Finding last valid log LSN: file: 1 offset 2350316
db_recover: Checkpoint at: [1][2345655]
db_recover: Checkpoint LSN: [1][2345655]
db_recover: Previous checkpoint: [1][2345607]
db_recover: Checkpoint at: [1][2345607]
db_recover: Checkpoint LSN: [1][2345607]
db_recover: Previous checkpoint: [1][2341168]
db_recover: DB_ENV->log_flush: LSN past current end-of-log
db_recover: DB_ENV->log_flush: LSN past current end-of-log
db_recover: Recovery function for LSN 1 8638 failed
db_recover: DB_ENV->open: Invalid argument
[Wed May 21 12:08:21 CEST 2008] Finished db_recover
db_checkpoint: open: No such file or directory
[Wed May 21 12:22:02 CEST 2008] Trying db_recover
db_recover: Finding last valid log LSN: file: 1 offset 2350316
db_recover: Checkpoint at: [1][2345655]
db_recover: Checkpoint LSN: [1][2345655]
db_recover: Previous checkpoint: [1][2345607]
db_recover: Checkpoint at: [1][2345607]
db_recover: Checkpoint LSN: [1][2345607]
db_recover: Previous checkpoint: [1][2341168]
db_recover: DB_ENV->log_flush: LSN past current end-of-log
db_recover: DB_ENV->log_flush: LSN past current end-of-log
db_recover: Recovery function for LSN 1 8638 failed
db_recover: DB_ENV->open: Invalid argument
[Wed May 21 12:22:02 CEST 2008] Finished db_recover
db_checkpoint: checkpoint: Wed May 21 12:33:01 2008
db_checkpoint: checkpoint: Wed May 21 12:33:01 2008
db_checkpoint: checkpoint: Wed May 21 12:48:01 2008
db_checkpoint: checkpoint: Wed May 21 12:48:01 2008
[Wed May 21 12:52:01 CEST 2008] Trying db_recover
db_recover: Finding last valid log LSN: file: 1 offset 2353868
db_recover: Checkpoint at: [1][2353820]
db_recover: Checkpoint LSN: [1][2353820]
db_recover: Previous checkpoint: [1][2353772]
db_recover: Checkpoint at: [1][2353772]
db_recover: Checkpoint LSN: [1][2353772]
db_recover: Previous checkpoint: [1][2352884]
db_recover: Recovery complete at Wed May 21 12:52:01 2008
db_recover: Maximum transaction id 80000000 Recovery checkpoint [1][2353820]
[Wed May 21 12:52:01 CEST 2008] Finished db_recover
Recreating db environment
db_checkpoint: checkpoint: Wed May 21 13:03:01 2008
db_checkpoint: checkpoint: Wed May 21 13:03:01 2008
db_checkpoint: checkpoint: Wed May 21 13:18:01 2008
db_checkpoint: checkpoint: Wed May 21 13:18:01 2008
[Wed May 21 13:22:02 CEST 2008] Trying db_recover
I can see that:
the db gets
Recreating db environment
Sometime after 12:52:01, maybe that did it, but I'am still missing the "why
it happed" and "how to prevent it from happening again"
---------------------------------------
Med venlig hilsen,
Supporten Internet 123
Thomas Jensen
support (at mark) i123.dk
http://www.i123.dk
---------------------------------------
----- Original Message -----
From: "Gerald Waugh" <gwaugh (at mark) frontstreetnetworks.com>
To: <coba-e (at mark) bluequartz.org>
Sent: Wednesday, May 21, 2008 3:57 PM
Subject: [coba-e:13008] Re: Error creating new site
> Dan Kriwitsky wrote Wednesday, May 21, 2008 6:39 AM
>> --- thomas <tfj-online (at mark) mail.tele.dk> wrote:
>>
>> > Hi All,
>> >
>> >
>> > I keep getting this error when trying to create a new site
>> >
>> > CCE Error:305 WARN
>> "[[base-disk.couldNotGetId,target=site87,id=GID]]"
>> >
>> >
>> > I have rebooted the machine a couple of times, no dice.
>> >
>> > This did not help:
>> > /etc/init.d/cced.init restart
>> >
>> > From /var/log/messages
>> > May 21 12:05:08 server saslauthd: saslauthd shutdown failed May 21
>> > 12:05:26 server PAM_pwdb[7501]: check pass; user unknown
>> >
>> > This did not help:
>> > /etc/init.d/dbrecover start
>> >
>>
>> Try running:
>> chkconfig --list | grep sasl
>>
>> If it's showing
>> saslauthd 0:off 1:off 2:off 3:off 4:off
>> Try:
>> /etc/rc.d/init.d/saslauthd restart
>> You might have to run that twice.
>>
>> Then see what chkconfig --list | grep sasl shows.
>> If it's still showing off, try:
>> chkconfig saslauthd on
>>
>> See if that helps the problem. There is some strange issue in
>> some servers that saslauthd is not properly restarting. I and
>> others have seen this. Nobody seems to know why it's not
>> happening on all servers. saslauthd does not appear to
>> properly stop on a reboot on some servers, then it doesn't
>> properly start on reboot.
>>
>
> Unless 'Network Services' > 'Email' > 'Enable SMTP Auth' is enabled
> saslautd will not be set to run in runlevel 3.
>
> So check the GUI... Setting.
>
> Then run the chkconfig and look at rc3.d to see it it is on.
> You can test by running /etc/init.d/cced.init restart.
> then look at chkconfig and rc3.d to see if it is setup correctly.
>
> Gerald
>
>