packages do not work after update from pfsense 2.5.2 to pfsense 2.6.0
-
@firefox said in packages do not work after update from pfsense 2.5.2 to pfsense 2.6.0:
@bmeeks
Which tab to check?
Why are you saying Snort is not working? I see nothing but Snort alerts in that system log output. It sure seems to be working to me.
You are on the correct tab, but I did not realize you had configured Snort to send all alerts to your system log. Is there a particular reason you are doing this, like maybe sending the logs to a remote syslog server? If not, then you should turn off Snort logging to syslog so other messages don't get lost in the Snort log noise.
-
@bmeeks
I see it
But in Snort's tab you see something else
I tried to reinstall the packages
But it keeps getting stuckIt stays that way for 12 hours
And did not reinstall
-
I think you have stuck zombie processes running on your box. That certainly seems to be the case for Snort. It is actively showing alerts in syslog (and probably on the ALERTS tab if you look there), but the process that is running does not have a matching PID file in
/var/run/, thus the GUI status shows as "not running".Reboot the firewall. Then when it comes back up, go to SYSTEM > PACKAGE MANAGER and delete the Snort package. When that finishes, reinstall it. That should fix Snort.
Your second screenshot is from Squid. I don't maintain that package, so I can't help you there. But doing the same thing (removing it and then reinstalling it) should work there. The first thing to do is reboot the firewall to be sure any extran
pkgorsnortprocesses are stopped. -
@bmeeks
I did a removal and it got stuck in this situation
-
@firefox said in packages do not work after update from pfsense 2.5.2 to pfsense 2.6.0:
@bmeeks
I did a removal and it got stuck in this situationThat messsage indicates it is trying to download the Snort rules. That can take a few minutes depending on your connection speed and where you are in the world. Also, those rules are hosted on AWS infrastructure. The Snort rules download URL will redirect to an AWS server. There have been cases in the past where other packages users are running like squid, squidguard, or pfBlockerNG have blocked the access to the AWS server or otherwise interfered with the download.
At the very least, if it can't find the AWS host to get the rules, it should evenutally timeout and continue with the install.
-
@bmeeks
I did reinstall the package again
And I left the computer for two hours
And it's done and everything's working now -
I have a perfectly good version of pfsense 2.5.2 working but decided to try 2.6 on another box,
After a fresh install, I tried to install any number of packages, but all responded with the same "Current pkg repository has a new PHP major version. pfSense should be upgraded before installing any new package." Does this mean 2.6 is no longer supported ? I suspect that this is a php version issue, but would appreciate any support that can help resolve this issue. Thanks, -
@parry said in packages do not work after update from pfsense 2.5.2 to pfsense 2.6.0:
Current pkg repository has a new PHP major version. pfSense should be upgraded before installing any new package."
Whoops - found this https://forum.netgate.com/topic/172356/can-i-rebuild-the-pkg-database-without-installing-updated-packages. And it worked
Or i seem to remember a tip from the 2.4.x days.
Switch your System --> Update Branch , to the "Beta" , and switch it back ....
Dont do the update , just the switching.
Should supposedly download the "new" package DB , for each switch. -
@parry said in packages do not work after update from pfsense 2.5.2 to pfsense 2.6.0:
I have a perfectly good version of pfsense 2.5.2 working but decided to try 2.6 on another box,
After a fresh install, I tried to install any number of packages, but all responded with the same "Current pkg repository has a new PHP major version. pfSense should be upgraded before installing any new package." Does this mean 2.6 is no longer supported ? I suspect that this is a php version issue, but would appreciate any support that can help resolve this issue. Thanks,You have to reset the package repo under SYSTEM > UPDATE, but I'm not sure that a version older than 2.7.1 will be showing there. Typically it allows selection of the current RELEASE, the upcoming DEVELOPMENT version, or the PREVIOUS STABLE version. PREVIOUS STABLE in the case of 2.7.2 would be 2.7.1.
Why not install the current 2.7.2 version of pfSense?
-
@parry said in packages do not work after update from pfsense 2.5.2 to pfsense 2.6.0:
Does this mean 2.6 is no longer supported
2.6 is no longer supported
https://docs.netgate.com/pfsense/en/latest/releases/versions.html
