RE: cfagent from cron

[ABostick]

I would like to report seg faults but I cannot always reproduce the error to
get a backtrace.  Basically, due to some misconfiguration of my own, I
killed virtually every cfexecd daemon on 30+ hosts.  I had some recursive
copies set up and then added my masterfiles dir to CVS and did not ignore
the CVS dirs.  CVS files were copied everywhere and that, for some reason,
probably logrotate choking, killed cfexecd as well.

Anyway, 2.0.4pre seems much more stable than 2.0.1, 2.0.2, or 2.0.3.
However, I am still seeing locks that do not expire...  So as soon as I can
trust cron, I will try the cfexecd -F option to see if that is any better
for me.

I have some busy work to do to get cron ready but I will relate my cron
experience as soon as I can.

What bothers me at this point is that from daemon mode, because of the
locking, I do not know if everything is running as it should.  When I go to
a host and run cfagent -q -v , I see everything run and crazy lock expire
timers on some things e.g. (1623/120) minutes and crazy stuff like that.  I
have seen locks expire after 30 days before...

I know I have asked this before but this isn't normal right?

Thanks for the help!
Aaron Bostick

-----Original Message-----
From: Mark.Burgess@iu.hio.no [mailto:Mark.Burgess@iu.hio.no]
Sent: Thursday, August 08, 2002 3:14 PM
To: Bostick, Aaron PH/US
Cc: bianco@jlab.org; help-cfengine@gnu.org
Subject: Re: cfagent from cron



Please don't ignore segfaults, report them. With gdb backtraces, preferably.
If you are using the latest, there should not be any segfaults. There
was a minor bug in 2.0.2 I think... but it's fixed now.

M

On  8 Aug, ABostick@mydoconline.com wrote:
> I have had problems with running cfexecd as a daemon, in that it seg
faults
> at times and appears to have locking issues (processes never expire!)
> running this way.  But when I run cfagent -q -v from a host itself, it
> always works great. 
> 
> Seems to me in my case ( maybe I'm doing something wrong) that running
> cfagent from cron would be much more reliable though I haven't tested
this.
> 
> I just need to get Openssh with BSM audit support installed do I can test
> the cron theory!
> 
> Thanks,
> Aaron
> 
> -----Original Message-----
> From: David J. Bianco [mailto:bianco@jlab.org]
> Sent: Thursday, August 08, 2002 2:16 PM
> To: Bostick, Aaron PH/US
> Cc: help-cfengine@gnu.org
> Subject: Re: cfagent from cron
> 
> 
> On Thu, 2002-08-08 at 15:05, ABostick@mydoconline.com wrote:
>> Is there a benefit from running "cfexecd -F" from cron instead of just
>> "cfagent" from cron?  Why the extra step?
>> 
> 
> The emails generated from cfexecd -F are usually a little nicer,
> even if just because they're easier to filter into folders because
> they have standard subject lines.
> 
> Actually, I'd go one step further.  Instead of running cfexecd -F 
> from cron, I run a short script that starts up cfexecd (without -F)
> if it's not already running. I also start cfexecd at boot.  The
> advantage of this is simple.  Since cfexecd and cron are separate
> and don't rely on each other to run, if one goes down the other can
> restart it.  My cfagent config restarts cron if it's not running
> (which has happened occasionally) and cron restarts cfexecd if it
> doesn't find it running.  A win-win situation.
> 
>       David
> 



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