Re: ExpireAfter lock meaning...

[Adrian Phillips]

>>>>> "Aaron" == ABostick  <ABostick@mydoconline.com> writes:

    Aaron> When I go to a host which hasn't been rotating its logs and
    Aaron> run "cfagent -q -v -D Hr00", the logs will rotate but I see
    Aaron> a message roughly "saying lock expired after 3878/10
    Aaron> minutes.  Trying to kill expired pid."  I was messing with
    Aaron> my ExpireAfter to see if it helps and have it set to 10
    Aaron> minutes right now.

    Aaron> 3878 minutes is almost 3 days.  Does that mean the
    Aaron> logrotate was trying to run for that long or just that
    Aaron> cfengine thinks it was because it had a stale lock in its
    Aaron> database?  Is this one of those "cfengine-die" problems?  I

Try deleteing all the lock files first then running it; then run it
again after an hour or so to see if the lock error appears again.

    Aaron> Thanks for the help.  I'm basically desperate at this point
    Aaron> trying to get this to work! :)

    Aaron> Aaron Bostick

    Aaron> BTW Target systems are Solaris 8 - Policy Host is Mandrake
    Aaron> 8.2

Um, cfengine version ?

Sincerely,

Adrian Phillips

-- 
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now?  [OK]