help-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Rebuilding cf_lastseen.db


From: Chip Seraphine
Subject: Re: Rebuilding cf_lastseen.db
Date: Wed, 03 Nov 2004 19:07:35 -0600
User-agent: Mozilla Thunderbird 0.8 (X11/20040916)


Wow, you nailed it.  You must have, like, ESPN or something.

Apparently version 3.3 creates a db-3.3.a but not a db.a, so when I copied over the 4.2 archive files in my build lib directory I did not stomp on one. Serves me right.

It occurred to me about 1 ohnosecond after sending the email that if cfengine couldn't handle a missing cf_lastseen.db then the thing would have never installed in the first place. Something about hitting 'transmit' that causes insight to flare up a second or two later....

Mark.Burgess@iu.hio.no wrote:

Make sure you don't have both versions of Berkeley hanging
around, so you are getting the header files from one, and
the library from another...

On  3 Nov, Chip Seraphine wrote:
So I rebuilt my cfengine with BerkeleyDB 3.3 as I have had constant hung agents of late and there was a suggestion on the thread that it helps. (That, and gdb shows that my stuck agents are generally lost somewhere in db-4.2 land.)

The problem is that this makes my cf_lastseen.db file no longer readable:

cfengine:: Directory /var/cfengine/inputs had permission 700, changed it to 750
/var/cfengine/cf_lastseen.db
cfengine:: Couldn't open last-seen database /var/cfengine/cf_lastseen.db
Segmentation Fault (core dumped)

If I delete it, it is still quite unhappy:

cfengine:: Directory /var/cfengine/inputs had permission 700, changed it to 750
/var/cfengine/cf_lastseen.db
cfengine:: Couldn't open last-seen database /var/cfengine/cf_lastseen.db
Segmentation Fault (core dumped)

Putting a zero-byte file also doesn't mollify it:

/var/cfengine/cf_lastseen.db
cfengine:: Couldn't open last-seen database /var/cfengine/cf_lastseen.db
cfengine:: db_open: Bad file number
Segmentation Fault (core dumped)


Any suggestions (short of reinstalling the agent altogether)?

Could we get an option to force this file to be rebuilt from scratch? I don't care about data loss, as the friendstatus stuff is of only minor importance to me. Even better than a db regeneration option would be default agent behavior of simply spitting out a warning and regenerating the file when encountering an invalid cf_lastseen.db file.




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  Mark.Burgess@iu.hio.no
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



_______________________________________________
Help-cfengine mailing list
Help-cfengine@gnu.org
http://lists.gnu.org/mailman/listinfo/help-cfengine


--

Chip Seraphine
Unix Administrator
TradeLink, LLC
312-264-2048
chip@trdlnk.com





reply via email to

[Prev in Thread] Current Thread [Next in Thread]