2.3.1 Update 1 Available

JorgeOliveira

Jorge are you saying they should identify their key by the longer ID of "0x13b987fd9214f8da"? Just curious..

Yes.

This update broke my instance. >:(
(…)
I can get shell as menu choice 8 works but 12 (dev shell) does not.
(...)

This may be caused by network/hardware problem causing an half-baked upgrade process. I'd recommend running this on shell:

pkg upgrade -f

It will download and reinstall all packages. Be aware this may take a considerable amount of time: 30 minutes to 2 hours. Be patient.

rjbradlow

@JorgeOliveira:

@rjbradlow:

This update broke my instance. >:(
(…)
I can get shell as menu choice 8 works but 12 (dev shell) does not.
(...)

This may be caused by network/hardware problem causing an half-baked upgrade process. I'd recommend running this on shell:
pkg upgrade -f
It will download and reinstall all packages. Be aware this may take a considerable amount of time: 30 minutes to 2 hours. Be patient.

Thank you Jorge but I also mentioned that all interfaces were down… and unable to be brought up so no dice there... No Network at all. Totally hosed.
I'm a Linux / bash guy and not familiar enough with the castrated shell in pfSense to attempt trying to fix it by hand.
If you look at the error again it states that the update was looking for a nonexistent directory named 'pear' and thus the missing file 'config.inc' as well.

So am I to gather from your reply that this directory does actually exist and was not downloaded by some networking glitch on a machine that had been updating and working flawlessly up to the latest update?

If so then why would it have been deleted instead of overwritten during a minor update from 2.3.1 to 2.3.1_1?

???

phil.davis

I don't know what the PEAR thing is about, maybe that happ0ened to be the last dir in the searchlist for looking for include files.
You should have a bunch of include files in /etc/inc

/etc/inc/config.inc

Do you have files there?
Does the content of /etc/inc/config.inc look like a bunch of PHP functions?

rjbradlow

@phil.davis:

Does the content of /etc/inc/config.inc look like a bunch of PHP functions?

Yes it is there with all of it's friends and yes it is PHP.

phil.davis

@rjbradlow:

@phil.davis:

Does the content of /etc/inc/config.inc look like a bunch of PHP functions?

Yes it is there with all of it's friends and yes it is PHP.

That's a good start.
/etc/rc.php_ini_setup should create:

/usr/local/etc/php.ini

and that should specify the include path:

include_path = ".:/etc/inc:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form"

and if all that is good, then config.inc (and lots of other include files) should be found.

rjbradlow

@phil.davis:

That's a good start.
/etc/rc.php_ini_setup should create:
/usr/local/etc/php.ini
and that should specify the include path:
include_path = ".:/etc/inc:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form"
and if all that is good, then config.inc (and lots of other include files) should be found.

./rc_php_ini_setup: /usr/bin/grep: not found

Thank you Phil. :)

Downloaded and mounted latest ISO, copied grep from ISO to /usr/bin/

Re-ran /etc/rc_php_ini_setup and exited to find a normal console menu

Further repairs in progress.

2chemlud

Hy!

Don't get me wrong, but is it really worth the effort? Fresh install, extract your config.xml, copy over to fresh install and start over again… max 1 hour, I guess.

regards

chemlud

rjbradlow

@2chemlud:

Hy!

Don't get me wrong, but is it really worth the effort? Fresh install, extract your config.xml, copy over to fresh install and start over again… max 1 hour, I guess.

regards

chemlud

Thanks chemlud,
It was certainly worth the learning experience.

Must have been a botched download like Jorge said.

I booted the cd and did a recovery which extracted the xml file and all was done in a matter of a few minutes after my last post.

quick and painless thanks to everyone's help here and the fine job the devs did with that nice recovery feature.

Thanks to all … great job guys!!

jdillard

@JorgeOliveira:

Just a side-note, using 32bit key IDs is a bad idea. See https://evil32.com for details.

I've found a key on the keyserver for "pfSense Security Team (Security Advisories for pfSense) <security at="" pfsense="" dot="" org="">" with the following fingerprint "E345 EF8C 4539 E974 943C 831D 13B9 87FD 9214 F8DA".

The message is successfully verified with that key.

I'd recommend the applicable public PGP key to be added here for reference: https://www.pfsense.org/security/</security>

It's there now: https://pfsense.org/security/

keen

is 2.3.1 Update 2 in the air ??

my ssh checking update has detected an upgrade, i have reloaded my pfsense box but nothing changed…

what is going ?

cmb

@keen:

is 2.3.1 Update 2 in the air ??

https://forum.pfsense.org/index.php?topic=113435.msg630835#msg630835