help-cfengine
[Top][All Lists]
Advanced

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

Re: cfrun problems with old cfengine version


From: Mark Burgess
Subject: Re: cfrun problems with old cfengine version
Date: Tue, 03 Jan 2006 05:58:01 +0100

The bad file descriptor message says that something in the checksum
database has become corrupted. Try restarting the daemon, and/or
deleting
the checksum database.

M

On Mon, 2006-01-02 at 22:47 -0600, Salvatore Enrico Indiogine wrote:
> cfengine version 1.6.x on Linux RH7.1 and RH9.   Yes, old version on
> old distributions.  At the moment I am not able to upgrade, but it is
> in the works.
> 
> sudo /usr/sbin/cfrun -d1 --no-splay
> 
> in /var/log/messages of the RH7.1 computer (cfenginesrv) where I run cfrun 
> from:
> 
> Received signal SIGPIPE
> cfengine:computername[24728]: Transmission failed/refused talking to
> cfenginesrv:/admin/cfenginesrv/usr/local/sbin/lastlogin.sh in stat
> cfengine:computername[24728]: send: Broken pipe
> cfengine:computername[24728]: Can't stat
> /admin/cfenginesrv/usr/local/sbin/lastlogin.sh in copy
> 
> and then:
> 
> cfd[25316]: cfd: couldn't open checksum database
> cfd[25316]: db_open: Bad file descriptor
> 
> While on the RH9 computer /var/log/messages:
> 
> send: Broken pipe
> cfengine:othercomputer[32332]: Can't stat
> /admin/cfenginesrv/etc/cron.weekly/publishcfg2html.sh in copy
> cfengine:othercomputer[32332]: Received signal SIGPIPE
> cfengine:othercomputer[32332]: Transmission failed/refused talking to
> cfenginesrv:/admin/cfenginesrv/etc/cron.daily/collectlogins.sh in stat
> 
> We have about 20 more computers in the same cfrun.hosts that give no
> error messages.
> 
> Thanks in advance for your kind help.
> 
> --
> Enrico Indiogine
> Parasol Laboratory
> Texas A&M University
> 
> enricoi@cs.tamu.edu
> hindiogine@gmail.com
> 979-845-3937
> 
> 
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-cfengine





reply via email to

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