# fping monitoring stops indefinitely after a CRITICAL alert

**URL:** <https://community.netdata.cloud/t/fping-monitoring-stops-indefinitely-after-a-critical-alert/2820>\
**Category:** Help\
**Tags:** agent, alerts\
**Created:** [April 29, 2022, 9:44am UTC](https://community.netdata.cloud/t/fping-monitoring-stops-indefinitely-after-a-critical-alert/2820 "2022-04-29T09:44:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vaiden](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/vaiden/32/1780_2.png) [@vaiden](https://community.netdata.cloud/u/vaiden)\
**Post date:** [April 29, 2022, 9:44am UTC](https://community.netdata.cloud/t/fping-monitoring-stops-indefinitely-after-a-critical-alert/2820/1 "2022-04-29T09:44:49Z")

</div>

Hi.

I’m running netdata 1.12.0-1+deb10u1 on an RPi1B+.  
I’m monitoring my network health via fping.  
Configuration is stock (what you get from ./edit-config) for both fping.conf and health.d/fping.conf.

Once a CRITICAL alarm is raised, fping monitoring stops indefinitely and I have to restart the netdata service in order to resume it.

What am I doing wrong?

---

<div class="post-metadata">

**Author:** ![Manolis\_Vasilakis](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/manolis_vasilakis/32/820_2.png) [@Manolis\_Vasilakis](https://community.netdata.cloud/u/Manolis_Vasilakis)\
**Post date:** [April 29, 2022, 10:16am UTC](https://community.netdata.cloud/t/fping-monitoring-stops-indefinitely-after-a-critical-alert/2820/2 "2022-04-29T10:16:34Z")

</div>

Hey @vaiden , welcome!!

Netdata 1.12.0 is kinda old… can you try to upgrade? And we’ll check if it is still a problem in later versions.

Thanks!!

---

<div class="post-metadata">

**Author:** ![vaiden](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/vaiden/32/1780_2.png) [@vaiden](https://community.netdata.cloud/u/vaiden)\
**Post date:** [April 29, 2022, 11:15am UTC](https://community.netdata.cloud/t/fping-monitoring-stops-indefinitely-after-a-critical-alert/2820/3 "2022-04-29T11:15:01Z")

</div>

Sadly this is the latest version available to the RPi1 architecture.  
I’ve tried compiling the newer version but it’s not worth the heavy lifting.

---

<div class="post-metadata">

**Author:** ![vaiden](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/vaiden/32/1780_2.png) [@vaiden](https://community.netdata.cloud/u/vaiden)\
**Post date:** [May 13, 2022, 7:32am UTC](https://community.netdata.cloud/t/fping-monitoring-stops-indefinitely-after-a-critical-alert/2820/4 "2022-05-13T07:32:26Z")

</div>

At the end, it seams that the default configuration for the fping alerts was not taken into consideration.  
Issue was fixed by simply applying the default configuration:  
`$ ./edit-config health.d/fping.conf`