The key to all of this is to look in your log files. I found out about the database corruption by looking in the logs and I noticed it was complaining about some of the databases. For example, cfenvd was complaining about /var/cfengine/state/cf_learning.db. I tried deleting this database, then ran cfenvd again and this time it didn't dump core.
I should have kept some of the log files because it might have helped you know what to look for. Just look for errors regarding db files. Luke -----Original Message----- From: Baker, Darryl [mailto:[EMAIL PROTECTED] Sent: Thursday, June 02, 2005 4:29 PM To: 'PAUL WILLIAMSON'; [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: Baker, Darryl; [email protected] Subject: RE: cfenvd dumping core It could be the Berkeley DB. I had that same idea. Blowing away all the runlogs, logs, *db and the state directory. This did give me a day and a half with out losing any processes. I'm not sure if cfexecd is crashing or is just exiting on bad data. All I know is that they both are dying and cfenvd is the only one leaving a corefile. _____________________________________________________________________ Darryl Baker _______________________________________________ Help-cfengine mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-cfengine
