Error after each package update
-
Guess it will be the same as always but next time I'll hook it up.
-
It will be different in at least one way, I added some text that does a connectivity test before reinstalling the packages, just wondering if it passes or fails when it lands in this state.
-
For me it works, the text is displayed and the startup finish. I am very happy with this.
Maybe in the gui for the package list it could be an exclamation mark saying that the packages needs to be reinstalled?
I do not not why the upgrade require to sync/upgrade the package but if it is missed at boot time because of lack of connectivity, it should alert the user that he has to do something after the link goes up again. -
Yeah I noticed that even if the upgrade fails something else is still clearing the flag file that says the packages need sync.
-
I don't know if it could be done but is it possible to have in the console during package upgrade or in the gui something saying from witch version the package is upgrade to (Upgrade from 1.1.1.1 => 1.1.1.2 for ex). Sometimes packages are upgraded but the average user like me does not really know why it needs to bu upgraded.
-
It won't upgrade them if there is a new version found. It only reinstalls them after a firmware update. It may happen to pull in a new version when it does that, but if you were to just reboot without doing a firmware update it would not upgrade the package.
-
If you had the serial console hooked up while it upgraded, it would be nice to see the package reinstall messages from the console.
Hey jimp. Today everything worked as expected. Well probably because I had the console attached ;-)
I'll attach my whole screen output log anyway so that you can see what was going on here.
One problem I saw today with the shellcmd package. If I navigate to Services->Shellcmd (https://IP:8443/packages/shellcmd/shellcmd.php) and from there I want to get to the pfSense Dashboard via the pfSense logo on top left I get a 404 Error. This is because the link behind the logo from there is somehow changed to https://IP:8443/packages/shellcmd/index.php where it should be https://IP:8443/index.php…Same problem with the Backup package. There the link points to https://IP:8443/packages/backup/index.php...
Should I open a ticket for that? This should be fixable quite fast in these packages...
-
Yeah that navigation deal is sort of a known issue. I thought there was already a ticket for that, though it was for the Cron package (Cron, Backup, and Shellcmd were all written by the same guy). If you open a ticket make sure it's under the "packages" area (http://redmine.pfsense.org/projects/pfsense-packages) since that is am issue with the individual packages' code and not an issue in the base system.
I'll have a look at the boot log more in depth later, but a quick scan of it looked OK.
