Scott Ullrich wrote: > On Nov 23, 2007 7:34 AM, Christian Krützfeldt > <[EMAIL PROTECTED]> wrote: >> The other day I had an unexpected power outage and then when it was back on >> pfsense (1.2 RC2) didn't work. >> >> It booted fine until the point where it wanted to start pfsense. The hard >> disk somehow "lost" the symlink for the directory where the configuration >> file is stored. I have no idea how that could happen, but all I needed to do >> is recreate the symlink and after a reboot everything worked fine. >> >> The problem obviously is, when this happens the symlink has to be created >> locally as the server isn't reachable over the network. >> >> Since the code that creates the symlink for the configuration folder and all >> other symlinks is somewhere in there, would it be an option to run this code >> every time the server boots and simply recreate them every time. >> I know this won't solve the problem of the symlink disappearing, but it >> should overcome situations where this happens. > > Not really an option since we have so many ways of storing config.xml. > Hard disk, compact flash, floppy disks, etc. Maybe we need to > record where the config.xml resides and restore from that. But I am > hesitant to make this change to the 1.2 branch as we are about to > release.
when I first started using pfsense with rc1, it was so unstable when either configuring CARP or expecting CARP to failover that the machine would crash or lockup and would nearly always lose the config.xml. even RC2 when changing carp interfaces can still crash pfsense, and I would have to manually recover the config.xml. (this is on regular x86 server)... so, if I'm not the only one who gets this problem then maybe the system needs a boot-time config.xml find/recovery/rescue option? Paul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
