;)

Thanks guys. It's all ok for now. Just can't upgrade. I'll wait.

pfsense upgrade crashed and I had this kind of error.
Unfortunately I can not send the error log file, because I was forced to format and reinstall pfsense.
Yesterday I had a much worse problem: I did upgrade to pfsense 2.4.0.r.20171008.0625 and now I can no longer associate any ip.
I have the same error:
https://forum.pfsense.org/index.php?topic=137672.0
Tonight I have to format and restore the backup.

I'm having the same issue. Every couple of months, the database gets corrupted. The hints from https://forum.pfsense.org/index.php?topic=123008.0 help to get it working, but usually at the expense of the database having been deleted and starting from scratch.

Is there any solution to this problem, yet?

@kpa:

Pkg is fine but pfSense could use more sensible defaults like not autoupdating the repo catalogs every time, it is not required for proper operation. Also none of the options can not be changed via the webgui and the update system is now a giant black box that doesn't reveal any of its inner workings which makes debugging problems very hard.

I've added a couple of options which Chris is going to test later. I can add more if needed.

@rcork:

@Renato:

@rcork:

I'm having the exact same problem. I'm currently on 2.4.0.r.20171003.1349. It says the Latest Base System is 2.4.0.r.20171004.0814. When cat /cf/conf/upgrade_log.txt, all it says is "2.4.0.r.20171004.0814 version of pfSense is available"

Attached is a capture of the console log when I try to update.

If your system is still in this state can you please run following commands and send me output?

pkg -ddd upgrade -n pkg -ddd upgrade -Fn

Thanks

I ran those two commands and the output is attached.

If you didn't upgrade it, could you send me the content of /var/db/pkg from this machine? Files inside this directory don't contain sensitive data and maybe they could help me to reproduce it internally. If it's possible please send to my email renato at pfsense dot org

Thank you

@FranciscoFranco:

How about a report on the fan noise on the Dual-E Quad. Is it loud or quiet? Fixed speed or variable?

I got my board from mouser. The fan is loud, fixed speed and I don't think there's support for a variable one but I may be wrong. I'm thinking of getting a quieter fan. In the meantime, since I'm not pushing the board too much despite having putting a lot of traffic through openVPN clients I just took it off and my temps have stabilized around ~50C. There's many manufacturers using only passive dissipation so that's possible but you would need to engineer it yourself. You can set up the bios to shutdown the board after certain temps.

@jdijulio:

Would it be possible to detect if an SD card is used for boot media, and if so, make this the default option?

No, because we do not want to encourage people to use SD cards for boot media in general anymore. It's slow and prone to failures. It's cheaper, but rarely worth it. Grab an mSATA SSD and don't look back.

I got tired of fighting w/ unbound myself and switched to dnsmasq. For me it was a good move, although others will argue to the contrary. I know Unbound is "better" on paper and the purist in me wants to use it, but it just wasn't as stable for me.  Dnsmasq does everything I need it to and just never seems to have issues. The recent CVEs were fixed in record time. I think from wide disclosure to having the patched binary running on my system was <24 hours, which I consider amazing.

To be fair, I didn't give Unbound much of a chance w/ recent 2.4 snaps and I hear it has improved, but for me there is no compelling reason to switch. Maybe worth it for you to give dnsmasq a try.

Reinstalled the package and the files are now there. Thanks

LOL. Applies to most things.

@jimp:

If you are on 2.4.1 you should reinstall to get to 2.4.0.

The rescue config.xml option in 2.4.0 works wonderfully, you can pick that from the first screen, select your drive, and then go through the install and it will come out with your current config. Back up and running with minimal fuss.

Just did so here and worked fine as well.

As it turned out, the HP 6200 Pro gad the AMT feature enabled but did not have the ME Firmware installed.  All I had to do was to disable the AMT feature and voila….. problem solved.

Renato

New 2.41 dev snapshot install dated 29-Sep-2017 on an APU2C4.  Same thing.  Reboot doesn't work.

Speaking of the old configuration, the error log is like this：

php-fpm 49863 /rc.filter_configure_sync: The gateway: IPv6LAXGWv6 is invalid or unknown, not using it.

There is an old gateway name, but maybe there is still a place where this error indicates where I should be looking for this old gateway name？