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

    Bind package upgrades pkg

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    3 Posts 2 Posters 1.6k 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.
    • D
      dsmith10
      last edited by

      I installed the bind package and after that my package interface ( installed and available ) stopped working.

      Reading through forums and doing a bit of digging I sumised that pkg had been upgraded, and sure enough

      Aug  1 18:53:27 london-gw-apu pkg: pkg upgraded: 1.7.2_2 -> 1.8.7
      Aug  1 18:53:37 london-gw-apu pkg: pfsense-bind910-9.10.4P2 installed
      Aug  1 18:53:38 london-gw-apu php: /etc/rc.packages: Beginning package installation for bind .
      Aug  1 18:53:39 london-gw-apu check_reload_status: Syncing firewall
      Aug  1 18:53:39 london-gw-apu check_reload_status: Syncing firewall
      Aug  1 18:53:40 london-gw-apu php-fpm[10606]: /rc.filter_synchronize: Beginning XMLRPC sync to http://192.168.20.3:8080.
      Aug  1 18:53:40 london-gw-apu php-fpm[10606]: /rc.filter_synchronize: XMLRPC sync successfully completed with http://192.168.20.3:8080.
      Aug  1 18:53:41 london-gw-apu php-fpm[14997]: /rc.filter_synchronize: Beginning XMLRPC sync to http://192.168.20.3:8080.
      Aug  1 18:53:43 london-gw-apu check_reload_status: Syncing firewall
      Aug  1 18:53:43 london-gw-apu php: /etc/rc.packages: Successfully installed package: bind.
      Aug  1 18:53:43 london-gw-apu pkg: pfSense-pkg-bind-9.10_8 installed
      Aug  1 18:53:44 london-gw-apu check_reload_status: Reloading filter
      Aug  1 18:53:44 london-gw-apu check_reload_status: Starting packages
      Aug  1 18:53:45 london-gw-apu xinetd[32241]: Starting reconfiguration

      I'm going to try the instructions to reinstall 1.7.2 manually, but should this happen and is there anything we can do to stop it ?

      1 Reply Last reply Reply Quote 0
      • D
        dsmith10
        last edited by

        So I solved this by upgrading from 2.3.1 to 2.3.2, as that clearly uses pkg 1.8.7, which is probably why this happened ?

        Anyway still seems a bit odd that installing a package will break pkg completly.

        1 Reply Last reply Reply Quote 0
        • dotdashD
          dotdash
          last edited by

          There were some notes on it in another post- when the pkg version was behind you could do a 'pkg lock pkg' to prevent the pkg manager from getting updated and breaking everything.

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