After Upgrade to 2.3.3 it is not possible to update a updateable packages
-
Upgrades just fine here. Maybe clear your browser cache. Or it"s one of the zillions of pkg flukes. No idea.
-
I haven't yet taken a look at what pfSense does with the updates but pkg will bomb on stale repository metadata and pfSense should execute 'pkg update -f' every time it switches pkg to use a new repository. If it doesn't yet do that it would explain quite a few of these problem reports.
-
I'd have imagined that the repository should FINALLY be non-stale if the upgrade finished (which required 4 switches between stable and development branches here, each followed by option 13 in console + cancelling the upgrade) but maybe it gets stale yet again because a butterfly hit a dandelion down somewhere in the Grand Canyon.
-
Can't install or upgrade packages here via webgui, browser cache isn't the issue, neither is the browser in use. Tried in Chrome, and FF and tried again on a machine with a cleaned up cache just to rule other stuff out. Upgrades work fine in shell.
Happened yesterday during a package install, gave up not really thinking or caring. Today saw there was an update for SQUID, went to apply and same thing happened.
-
Go file bugs, people. NOT about Squid. About pkg.
-
Since installing/reinstalling/upgrading works fine for many of us we'll need more info about the environment to try to reproduce it.
Full install or NanoBSD? i386 or amd64? What packages do you have installed?
If you try to install/upgrade a package while watching in Firebug, Chrome developer mode, or similar, do you see any errors or anything obvious that is trying to happen but failing?
-
I saw your issues above with upgrading packages via the GUI. I decided to skip and go straight to "pkg upgrade".
Squid updated successfully but at the end of the update it was left disabled. I enabled it via the dashboard widget but it would not intercept HTTP (80) traffic. Did a reinstall of just the Squid package and it still wouldn't intercept traffic.
I had to click on the save button on the main squid package configuration tab - to presumably re-write the settings to the appropriate configuration files - even though no changes were made and then restart squid again and it finally started intercepting traffic.
I love the capabilities and performance of pfSense but upgrading anything is a nightmare. It seems I have to do a clean install and manual input all my configuration settings as even a backup and restore tends to mess up some packages.
-
I have the same problem, need to try a few times before getting those pakages upgraded. :o :o
-
No errors in Console, but Network seems to have a problem …
-
Seems to be working if I first hit install as usual. Nothing happens. Then hit browser back button and then Install again. And the installation now starts …
-
I've updated 3 machines and have experienced the exact same problems. 2 of them I just wiped the machines out and reloaded the config which seemed to fix the problem.
-
I found a post somewhere that said doing a pkg update and pkg upgrade seemed to fix the problem.
I just reproduced the problem on another machine I maintain and it gave me the same error so I went to the console (via ssh) and ran pkg update and pkg upgrade and it seemed to get the pkg installer working again via the gui. -
I had the same problem with squidguard.
I updated pfsense from version 2.3.3 to 2.3.3_1 and it solved for me.
