Lost configuration on reboot?



  • Hello,

    I'm running 2.0-RC1 (i386) built on Mon Mar 7 12:37:11 EST 2011 nanobsd (4g).
    Is it normal that the configuration gets lost on every reboot?

    Thanks,
    Stenio


  • Rebel Alliance Developer Netgate

    No, that is not normal.



  • @jimp:

    No, that is not normal.

    Hi,

    Do you have any suggestion that can help me to solve the problem?

    Thanks,
    Stenio


  • Rebel Alliance Developer Netgate

    Not without a lot more detail. Though the first suggestion is always to upgrade to the most recent snapshot first to see if the problem persists.



  • I'm using 2.0-RC1 (i386) built on Mon Mar 7 12:37:11 EST 2011. It should be the latest.
    If I remember correctly the problem started when I upgraded from 1.2.3 to 2.0B5.
    Do you know if there is a boot log file useful to diagnose the problem?

    Thanks,
    Stenio



  • It would be helpful if you gave more details of what you mean by "configuration gets lost". For example, do you mean pfSense wants to reassign interfaces on every reboot? Do you see a boot time message "lost configuration" or similar? Is the configuration file (/cf/conf/config.xml) empty or missing entirely? etc etc.



  • @wallabybob:

    It would be helpful if you gave more details of what you mean by "configuration gets lost". For example, do you mean pfSense wants to reassign interfaces on every reboot? Do you see a boot time message "lost configuration" or similar? Is the configuration file (/cf/conf/config.xml) empty or missing entirely? etc etc.

    Hi Wallabybob,

    You are right: I'll try to be more detailed.

    When I reboot the firewall I must:

    1. set the interfaces IP addresses;
    2. click on the sliding config restore link;
    3. go to System -> General setup and save;
    4. go to System -> User Manager -> edit admin and save (if I don't do this I cannot log in via SSH);
    5. go to Services -> DNS forwarder and save;
    6. go to OpenVPN -> Server edit and save;
    7. go to VPN -> VPN PPTP edit and save;
    8. reinstall snort and update its rules.

    I don't see lost configuration messages but I see a lot of warning related to missing .inc files (several of them related to snort).
    The config.xml file is not empty now. The next time I'll reboot I'll see if it is missing.

    Thanks for your help,
    Stenio



  • related to the whole thing.  if you try to upgrade, same problem.  bet you have an ata drive? /dev/ad4s1a? ?

    I have posted a couple of times.  you might need to hook up a usb keyboard.. yes,..

    I could NEVER get the upgrade to work, and a rc1 cd would not see the 1.2.3 config.xml when it booted. would not install on any hardware that previosly had fbsd on it.

    needed to wipe out the first 512 bytes of the drive with dd and /dev/zero

    not good.



  • @scheidell:

    related to the whole thing.   if you try to upgrade, same problem.   bet you have an ata drive? /dev/ad4s1a? ?

    Hi Scheidell,

    From dmesg:
    ad2: 3825MB <sandisk sdcfx3-008g="" hdx="" 5.00="">at ata1-master PIO4 
    From Diagnostic: nanobsd:
    Bootup slice is currently: ad2s1</sandisk>


Log in to reply