Another high CPU post. - Seems to be apinger related


  • Good day guys.

    As you can see on the post count, I'm brand spanking new and a noob when it comes to pfSense as well.

    I hope to get more insight in my problem.

    I'm running Version 2.15.
    I only have "Bandwidthd" as an additional package.

    My setup is very basic, running only a few rules regarding the Traffic Shaper.
    I also had some failover rules which I since have deleted as I though they were contributing to my problem.

    The CPU has suddenlystart running at 100%.
    I've Googled a bit, but haven't been able to identify my problem.
    I've tried to activate and deactivate the Polling option as suggested by some, but it is not the solution to my case.

    I then disabled the apinger service and the CPU usage immediately dropped to 5%. I then deleted my Failover setup, as I thought it could be the cause of the problem, but it did not help.
    It seems the apinger service is the problem.

    What does the apinger service do? Is it okay if I keep it disabled or what would the impact be? Is there a solution for the problem?
    I've added a fews pics, but it does not make any sense to me.

    I would appreciate any feedback/help.

    Thank you.
    :)

    ![PFsense high cpu.JPG](/public/imported_attachments/1/PFsense high cpu.JPG)
    ![PFsense high cpu.JPG_thumb](/public/imported_attachments/1/PFsense high cpu.JPG_thumb)
    ![High cpu.JPG](/public/imported_attachments/1/High cpu.JPG)
    ![High cpu.JPG_thumb](/public/imported_attachments/1/High cpu.JPG_thumb)
    ![RRD graph processes.JPG](/public/imported_attachments/1/RRD graph processes.JPG)
    ![RRD graph processes.JPG_thumb](/public/imported_attachments/1/RRD graph processes.JPG_thumb)


  • apinger basically monitors your gateway for connectivity.  It has been the suspected source of several link-related issues.  If you have the option, try the updated apinger in the 2.2-BETA builds.


  • @KOM:

    apinger basically monitors your gateway for connectivity.  It has been the suspected source of several link-related issues.  If you have the option, try the updated apinger in the 2.2-BETA builds.

    Thank you for the reply.

    How do or where do I get the updated apinger?
    Is it a beta pfsense version?

    Edit:
    I assume you refer to this?

    https://snapshots.pfsense.org/

  • Banned

    2.1.5 also has Aping issues at random.

    CPU count on ESXi matches the one seen in the dashboard though….


  • I assume you refer to this?

    Yes, I should have been more clear that I was referring to an updated pfSense build and not just apinger.


  • @Supermule:

    2.1.5 also has Aping issues at random.

    CPU count on ESXi matches the one seen in the dashboard though….

    Thx for the reply.

    I'm currently on 2.1.5

    CPU count on ESXi matches the one seen in the dashboard though….

    Is that good or bad?


  • @KOM:

    I assume you refer to this?

    Yes, I should have been more clear that I was referring to an updated pfSense build and not just apinger.

    Thank you.

    I might just try this over the weekend.

    :)


  • They are close to an RC build, so while they say you shouldn't use it for production purposes, it's getting very close to release.  Lots of stuff has been fixed, lots of new goodies added.  If you're new, I might recommend that you start off with the new base instead of using the much-older FreeBSD 8.3-based pfSense.