Re: cfengine watchdog is not biting

i dont think the problematic situation can be simulated, but running the 
changed script shows a missing "then" ;-)

https://github.com/cfengine/masterfiles/blob/70eb84ad845af716fdc53b1299544e7b521a563d/cfe_internal/core/watchdog/templates/watchdog.mustache#L60

after adding it, the scripts runs without errors....

On Thursday, February 22, 2024 at 2:47:24 AM UTC+1 [email protected] 
wrote:

> I opened a pull request: https://github.com/cfengine/masterfiles/pull/2841
>
> Would like some help with testing.  Would be especially great to test on 
> some of these systems where the existing pidfile logic isn't working, 
> besides testing the usual cases.
>
> Best,
> --Mike Weilgart
> On Wednesday, February 21, 2024 at 6:59:41 AM UTC-8 
> [email protected] wrote:
>
>> Thanks for filing the ticket. :D
>>
>> On Tuesday, February 20, 2024 at 6:34:15 AM UTC-6 Xander Cage wrote:
>>
>>> ticket created -> https://northerntech.atlassian.net/browse/CFE-4335
>>>
>>>
>>> On Tuesday, February 20, 2024 at 11:11:20 AM UTC+1 Xander Cage wrote:
>>>
>>>> Hi,
>>>>
>>>> At times the cfengine watchdog script is unable to resolve hanging 
>>>> cf-agents. the reason is that if the system is under high load the watchdog 
>>>> "hangs" because it reads his own stale pid file and is doing simply 
>>>> nothing. 
>>>>
>>>> example:
>>>>
>>>> i had 332 hanging cf-agent processe but the watchdog log just shows 
>>>> this.
>>>>
>>>> Tue Feb 20 10:57:00 CET 2024 Initiating watchdog 6816488
>>>> Tue Feb 20 10:57:00 CET 2024 Aborting execution of watchdog 6816488, 
>>>> existing watchdog process 16450014 running
>>>> Tue Feb 20 10:58:00 CET 2024 Initiating watchdog 44499432
>>>> Tue Feb 20 10:58:00 CET 2024 Aborting execution of watchdog 44499432, 
>>>> existing watchdog process 16450014 running
>>>>
>>>> after deleting the pid file...
>>>>
>>>> Tue Feb 20 10:59:00 CET 2024 Initiating watchdog 25756150
>>>> Tue Feb 20 10:59:01 CET 2024 Found cf-execd not running
>>>> Tue Feb 20 10:59:03 CET 2024 Found 332 occurrences of cf-execd 
>>>> terminating unresponsive cf-agent
>>>> Tue Feb 20 10:59:04 CET 2024 Found 2 symptoms, threshold (0) breached.
>>>> Tue Feb 20 10:59:06 CET 2024 Initiating apoptosis
>>>> Tue Feb 20 10:59:10 CET 2024 Initiating anastasis
>>>>
>>>> i guess there is room for impovement, as this can bring a system down 
>>>> quite easyily.
>>>>
>>>> wbr
>>>>
>>>> chris
>>>>
>>>>

-- 
You received this message because you are subscribed to the Google Groups "help-cfengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msgid/help-cfengine/2096c89e-b581-4dcf-9632-994b2ef1b052n%40googlegroups.com.