Shared object "libdl.so.1" not found, required by "openvpn"

foxrcesar

@jimp may have been recommended this way since always, but it is so normal to update a package, the first time I see cause so many problems for openvpn.

faust

@jimp said in Shared object "libdl.so.1" not found, required by "openvpn":

The recommendation for pfSense has always been to remove all packages and then upgrade

So say you have some packages configured (squid, zabbix-agent, openvpn-export etc).
You need to:
1/ remove them
2/ reboot
3/ upgrade
4/ reinstall them
5/ configure them

Can you confirm?

jimp

Read the upgrade guide, it has the officially recommended procedure.

foxrcesar

@faust so it's in the recommendation that's right ... I'll never update a package again.

jimp

@foxrcesar said in Shared object "libdl.so.1" not found, required by "openvpn":

@jimp may have been recommended this way since always, but it is so normal to update a package, the first time I see cause so many problems for openvpn.

That is not normal for pfSense and never has been. I'm not sure what you're thinking of. Not even that way for FreeBSD. You update the base OS and then update installed software because when making a version jump, the binaries might be backward compatible but they are not necessarily forward compatible. Also you'll end up reinstalling all packages after anyway since they wouldn't match the base OS after upgrade if they were pulled from an old repo.

jimp

@foxrcesar said in Shared object "libdl.so.1" not found, required by "openvpn":

@faust so it's in the recommendation that's right ... I'll never update a package again.

We have code in place now to prevent these kinds of problems in the future.

I can't replicate this kind of error on 2.4.3-p1 installs now. Every package update or install request fails saying there is a new version, upgrade first.

KOM

@jimp Thank you. This will surely save some people down the road.

foxrcesar

@jimp Thanks for the explanation, it makes sense and I see that you have a warning when trying to install a new package in a late version of pfsense, I will update pfsense and I do not have the option to update the packages separately. have a nice day.

faust

@jimp

Read the upgrade guide, it has the officially recommended procedure."

Thank you, I read it more than once but some points remains not clear sorry...
I can't find answer to point 5/ (do we need to reconfigure packages or configuration are kept?).
I am only talking about official pfSense packages, I understand you cannot maintain third party packages.

jimp

Package configurations are kept, unless the package does otherwise. Some packages have an option to not retain the configuration. In those cases, it's up to you and how you configured those packages.

faust

@jimp Thank you for this confirmation.
I don't now what are the implication for the package manager but I think that the proposition of @KOM should be considered as it would prevent a lots of trouble.

Agreed, like not showing package upgrades that would break their systems due to missing dependencies. I thought it was ridiculous that users could break their systems by upgrading a package that relied on a major pfSense upgrade. Either the package shouldn't have been presented in the first place, or the package installer should have bailed out right away when the requirements weren't met.

Because my mistake (and I am surely not alone) was to think that pfSense package manager was similar to PKG or APT (as it relies on PKG) and it is clearly not as simple as that. You are allowed to upgrade a package without upgrading the whole system (and break it).

jimp

Except as I've said a few times now, you can't do that anymore. There is code in place to prevent that from happening. We've done all we can to protect against that in the future.

faust

@jimp said in Shared object "libdl.so.1" not found, required by "openvpn":

Except as I've said a few times now, you can't do that anymore. There is code in place to prevent that from happening. We've done all we can to protect against that in the future.

Ok perfect, but I will check this point on next upgrade because I actually had the problem upgrading from 2.4.3-p1...