Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Check_reload_Status 100% Cpu … again

    General pfSense Questions
    3
    4
    1.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jonnyD
      last edited by

      Hello,

      i have this Check_reload_Status 100% Cpu issue on my pfsense machine so i checked all my logs to find the real cause…. but nothing.

      What can i do to find the reason?

      Thanks.

      1 Reply Last reply Reply Quote 0
      • ?
        Guest
        last edited by

        i have this Check_reload_Status 100% Cpu issue on my pfsense machine so i checked all my logs to find the real cause…. but nothing.

        Perhaps it will be nice to know more about your;

        • pfSense hardware
        • Internet connection speed
        • all installed and running packets
        • whole network topology and devices

        Have you enabled PowerD (hi adaptive) mode for that unknown CPU?
        This would be my first look at this.

        1 Reply Last reply Reply Quote 0
        • J
          jonnyD
          last edited by

          Thanks for your reply.

          It is a scope7-7568 Appliance with dualcore Atom CPU and 4 GB RAM.

          First Internet connection is 100mbit up / 100 mbit down with static IP and we have a second 200 Mbit down / 25 UP Backup connection with dynamic IPs (configured but not in use currently).

          Default pfsense Setup, no additional packages. Openvpn server is running.

          PowerD is disabled.

          Pfsense runs fine for some hours or sometimes days after a reboot but suddenly this Check_reload_Status process starts and never stops.

          1 Reply Last reply Reply Quote 0
          • luckman212L
            luckman212 LAYER 8
            last edited by

            Having the same issue. SG2440 unit on 2.4 beta snaps. No squid/snort/ntopng or any heavy packages installed. Native DHCP6 on the WAN (seems to possibly be related to DHCP6 or having IPv6 enabled in general). I have had this problem on 2.2 and 2.3 - whatever is causing it is mostly likely a very old bug, I see threads from 2011-2012 asking about the same issue. No good answers.

            I just posted this in the Development section… hoping for a response...

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.