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

    System is aware of new version but tells that it is up to date.

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    3 Posts 2 Posters 557 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.
    • P
      pauldistel
      last edited by

      I have some pfSense appliances which behave differently. I have one that was aware of the new version 2.5.0 and notified me correctly. Upgrading went ok. I have two other systems that behave differently.

      One seems not to be aware of the new version and remains on version 2.4.5 P1:

      67a10ba6-a19a-4aab-bb47-af1a77684de2-image.png

      What puzzles me most is the one that seems to be aware of a new version 2.5.0 but keeps telling that it is up to date with version 2.4.5 P1:

      a10b042e-5f36-46ba-b5aa-b97f4fffabc1-image.png

      Switching to the previous version and after some time, switching back, does not solve the issue.

      The below metioned info is from the last system.

      I also tried the update from the console but that gives me other info which does not help me forward:

      7e225071-ffdd-4dfb-9721-0455653938af-image.png

      The command pkg-static info -x pfSense-upgrade:

      7104be8e-8837-4fc4-a69c-e788a7d28f55-image.png

      The command pkg-static bootstrap -f:

      11da31e6-5ea9-4217-b474-eda1086f63f0-image.png

      Any suggestions or help is appreciated!

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @pauldistel
        last edited by

        @pauldistel

        Most probably an issue where pfSense iself can't access DNS.

        b3f1fd99-625e-4b47-a6ca-d4b3ced45825-image.png

        pfSense - the local DNS, the resolver, can't "dail' out to do it job, resolve which permits the "pkg" to load needed files.

        Compare DNS settings among your system.
        Test de DNS - from console.
        Make sure DNS settings are set to default, as they work.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        P 1 Reply Last reply Reply Quote 0
        • P
          pauldistel @Gertjan
          last edited by pauldistel

          @gertjan It was indeed a DNS issue but it was caused by something else. Time was not in sync and therefore DNS was not working. NTP was configured with DNS names only. So a what came first situation was established? The chicken or the egg? :)

          I configured an additional time source by IP. Had the time updated, restarted DNS and everything was fine.

          I do experience some issues with the DNS resolver sometimes. It's a different issue so I should open a new topic for that. It does not always resolve my Active Directory zones defined in the DNS resolver. Restarting the DNS resolver service solves this issue and I find that very strange...

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