Upgraded to 2.4.4_3 - after 2 days router not working anymore.

albgen

hopefully this was a virtualised router and i did restore a backup.
Do not use the version 2.4.4_3. its total crap

albgen

here is the screenshot.
if sombeody wants the VM image(hyper-V) for this issue i can provide it

chrismacmahon

What did you update from?

As this was a VMware image, why haven't you rolled back to the snapshot pre-update?

albgen

from the UI i did the upgrade! The stable branch
of course i did rolled back(Hyper-V btw) but this is scary sir! what if i had a hardware device

deadpfsense_updatefrom ui.png

chrismacmahon

This is the only instance I have seen like this.

I would follow the steps listed on here: https://docs.netgate.com/pfsense/en/latest/install/upgrade-troubleshooting.html

albgen

i will keep it like this and not upgrade.
If somebody is willing to troubleshoot than i can provide the image

JeGr

Upgraded several physical AND virtual setups without a hitch, so to say

@albgen said in Upgraded to 2.4.4_3 - after 2 days router not working anymore.:

Do not use the version 2.4.4_3. its total crap

is indeed exactly that. We don't have a clue what exactly went wrong with your setup but IMHO has nothing to do with exactly that update.

By the way: your screenshot with the error shows an installation older than 2.4.4-p2. Those libraries with <20131226> point to PHP 5.6 which was deprecated and switched to 7.x with the 2.4.3 update. Since then, it is running PHP 7.1 or 7.2 depending on your version. So that points to something that is older then the 2.4.3 update.
2.4.4-p2 was already running 7.2.10 which has it's libraries located under /usr/lib/php/20170718/xyz.so. So for debugging I'd go down that road and check if that version in your last shot (2.4.4-p2) is really and completely installed. But that sure looks fishy.

albgen

This instance of pfSense is installed on january 2018. After that i did the regular updates from the UI. Thats it. Arrived today and i had a dead box. What happened? well i don't know, it seem this version(2.4.4_3) is braking something.
Never happened since using monowall and pfsense. First time!

Let me point out also that i'm the only one that can manage this box so the chance somebody has done something on the box else is zero! The web interface and the ssh is not even exposed on the wan interface.

chrismacmahon

what is the output of:

pkg search php

albgen

@chrismacmahon said in Upgraded to 2.4.4_3 - after 2 days router not working anymore.:

what is the output of:
pkg search php

i did not even tried to fix it. It is a production system and i just had to be up and running. I just took a backup of the whole image(2.4.4_3) and restored the working one with the 2.4.4._2 version.

What i did noticed is that i could not even ping nothing. just entered on the shell and tried to ping and i got no route to host.

when i will have some time i will restore the not working image on the lab. fi you want i can upload the ihyperv mage (10Gbyte) somewhere so you can see also...

chrismacmahon

I understand that.

what is the output of

pkg search php

Of the current machine.

albgen

@chrismacmahon said in Upgraded to 2.4.4_3 - after 2 days router not working anymore.:

pkg search php

puttyFluid.zip

jimp

Reinstall from 2.4.4-p3 installation media. Choose "recover config.xml" at the first screen of the installer, then proceed to install again.

There are ways to get it back from the state you are stuck in but it's a lot less work to reinstall, if you can.

All of the other procedures are covered at https://docs.netgate.com/pfsense/en/latest/install/upgrade-troubleshooting.html

ady2

Absolutely same issue here, upgraded to 2.4.4p3 from UI on 05/23 and today, 05/25 my pfsense has same issues, no DHCP on any network card, pfsense is not responsive except the shell terminal option, same errors PHP startup. Unable to load dynamic library ...

Is this hardware failure or what?

Will try to reinstall, and apply the restore from backup.

albgen

@ady2 i dont think is a hardware fault. Seems like this upgarde is not handling some certain cases and we fall in this one.
What i dont like is that how this problem can appear after 2 days and not right after the upgrade.
Next time i will upgrade after 1 month of a "stable release"..

Gertjan

@albgen said in Upgraded to 2.4.4_3 - after 2 days router not working anymore.:

f sombeody wants the VM image(hyper-V) for this issue i can provide it

As here https://forum.netgate.com/topic/143656/weird-2-4-4_3-issues/7

With the /usr/local/lib/php/20131226/ folder still in place (old PHP libs) pfSense is pretty brain-dead.

Didn't saw this myself, all upgrades to p3 went fine - including a pfSense running under Hyper-V @home

JeGr

To any who encounters that:

are you able to get to console shell (#8 in menu) as that won't/shouldn't trigger a PHP problem?
if so, are you able to go to /usr/local/lib/php and check (ls -la) what folder there is?
Assuming its some folder like 20170716 (or something 2017...) can you run
- cd /usr/local/lib/php
- ln -s 20170718 20131226
- ls -la (again) and verify there is now a 2013xxxx folder (like the errors claim not to be)
- Ctrl + d (so the console menu should reappear)

So afterwards

Is the console menu now running properly again?
can you now trigger #13 again (update from console)
does it update anything?

Greets

albgen

@JeGr The console reappeard and it started working. The first thing i did was a reboot and than it started the config again...
i guess this is because the network is not the same but i cannot create the same network in the lab.
pf2 reinstall.png

JeGr

Not bad :)
If the console is working with the Symlink workaround, could you run the "update" menu point or manually run pkg update and pkg upgrade afterwards if there are missing updates etc. to indicate a broken update at some point?

Thanks!

albgen

pkg not found... pkg not found.png