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

    System logs

    Scheduled Pinned Locked Moved General pfSense Questions
    13 Posts 3 Posters 2.0k Views
    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.
    • QinnQ
      Qinn @jrey
      last edited by Qinn

      @jrey Did not know that, why is it default enabled?

      pfSense-localdomain-Services-Dynamic-DNS-Check-IP-Services.jpg

      Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
      Firmware: Latest-stable-pfSense CE (amd64)
      Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

      J 1 Reply Last reply Reply Quote 0
      • J
        jrey @Qinn
        last edited by

        @Qinn

        Sorry No Clue, just know that it is.

        Someone didn't think it should be disabled by default and then only enabled if/when dyndns is setup.
        Doing that might take an extra line of code or something.. who knows.

        1 Reply Last reply Reply Quote 1
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Mmm, that's interesting. I don't believe it actually connects out to that if there is no dyndns service configured. I don't see it doing so in a pcap.

          J 1 Reply Last reply Reply Quote 0
          • J
            jrey @stephenw10
            last edited by

            @stephenw10

            according the logs previously it was, that's how I noticed it was enabled and why I turned it off ๐Ÿ˜Š

            Since I don't run DynDNS and never have they only way I could have possibly known it was enabled was because of chatter in the logs.
            Disabled it - no more chatter.

            Admittedly, that was a couple of versions ago. and it could have changed, but has been disabled here ever since with no reason for me to look back.

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Yeah I don't think it actually checks though. It just logs that it's updating anything that is configured. That same way it still logs updates for IPSec and OpenVPN even if none are configured.

              J 1 Reply Last reply Reply Quote 0
              • J
                jrey @stephenw10
                last edited by

                @stephenw10

                Not that log my friend ๐Ÿ™ƒ (I know what you are assuming I was looking at)

                -- the dns log, outbound traffic etc all showed the hits at the time.. that's what tipped me into tracking down the source and turning it off. Not using DynDNS, I initially didn't even know where the setting was, just that there was periodic traffic.

                again awhile ago so maybe the behaviour has changed since then

                for me disabled is the right choice. - that way 100% there is no chatter from it - ever -

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Ah I see! Yeah, no reason to leave it enabled really.

                  1 Reply Last reply Reply Quote 0
                  • QinnQ
                    Qinn
                    last edited by

                    Strange disabled it, but it keeps popping up in the system logs?

                    pfSense-localdomain-Status-System-Logs-System-General(2).jpg

                    Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
                    Firmware: Latest-stable-pfSense CE (amd64)
                    Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

                    J 1 Reply Last reply Reply Quote 0
                    • J
                      jrey @Qinn
                      last edited by

                      @Qinn

                      The Check IP being disabled has nothing to do with those messages.

                      same answer as before.

                      @jrey said in System logs:

                      they appear even if you don't run OpenVPN or IPsec or dyndns
                      system is just checking if it needs to do something. No harm

                      check_reload_status == the system asking if it should be running something and saying that it has asked.

                      The message are misleading as they give the impression they are doing something like "restarting" / "updating"
                      when in fact when you are not running those services, it should likely just say something like
                      "Checked OpenVPN Status - disabled" or;
                      and when you are running them
                      "Checked OpenVPN Status - Restarting"

                      Logging that implies an action is being taken when it is not, is just poor logging. IMHO

                      1 Reply Last reply Reply Quote 2
                      • QinnQ
                        Qinn @jrey
                        last edited by

                        @jrey said in System logs:

                        @Qinn

                        assume you are asking about the restarting messages "check_reload_status" specifically?

                        they appear even if you don't run OpenVPN or IPsec or dyndns
                        system is just checking if it needs to do something. No harm

                        not related but if you are NOT running dyndns you can turn off the "Check IP Services" it will stop the system from checking your IP in at checkip.dyndns.org

                        Screen Shot 2023-12-11 at 11.02.43 AM.png

                        Sorry, my mistake I associated the Check IP Services with the logging, so I have read it wrong, as you clearly stated; "not related, but if you are...."

                        Hardeware: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz 102 GB mSATA SSD (ZFS)
                        Firmware: Latest-stable-pfSense CE (amd64)
                        Packages: pfBlockerNG devel-beta (beta tester) - Avahi - Notes - Ntopng - PIMD/udpbroadcastrelay - Service Watchdog - System Patches

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