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

    Package configuration settings lost during upgrade

    2.0-RC Snapshot Feedback and Problems - RETIRED
    2
    3
    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.
    • rcfaR
      rcfa
      last edited by

      I noticed that after the autoupdates I pretty much regularly have to reconfigure a series of optional packages.
      e.g. arpwatch will have to be told again what interface to watch before it can be launched successfully, similarly with bandwidthd. The antivirus package needs to have its options set again, as does ntop, squid, squidGard, and widentd.

      So what I wonder:
      a) am I doing something wrong?
      b) if not, is this expected behavior?
      c) if not, do others have the same problem?
      d) if not, any ideas as to what might be the cause for this issue on my system?

      This is a regular pfSense amd64 install (not nanoBSD)

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        That is not normal. Hard to say what exactly might be causing that. Normally when a package is removed, its settings remain. Only one I am aware of that would clear its settings out would be snort.

        Use the config history to run some diffs and see when things disappear (Diag > Backup/Restore, Config History tab)

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • rcfaR
          rcfa
          last edited by

          I removed for now the imspector-wip package, since its settings page didn't load correctly, so maybe that points to some other issues that might cause this. If after the next build is available I autoupdate, and have the same issue again, I know this wasn't the solution, and will investigate further.

          Currently the config history starts with an entry that corresponds to when I did the last autoupdate, and it reads simply:

          "7/26/11 07:10:12 (system): made unknown change "

          No shit! :D

          What follows later are only the changes to reconfigure the packages and the deletion of the imspector-wip package.
          The problem will be: if the problem persists, then it looks like it not only resets the packages, but also the config history, which makes it kind of difficult to trace what's going on.

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