Error after each package update
-
I experienced the same issues with my ALIX board under 2.0-BETA4; had to revert back to 1.2.3-RELEASE because the system was too unstable.
jlepthien, would you say most of the packaging and WebGUI freezes have been fixed ? I could install 2.0-BETA5 01/08 and provide some additional feedback.
__.
pac -
Juste to let know know:
with 2.0-BETA5 (i386) built on Tue Jan 11 14:19:18 EST 2011I got this message at boot time:
One moment please, reinstalling packages... pkg_info: no packages match pattern(s)Don't really know what it means…
Also, all my packages have been deinstalled but I don't know my just after the upgrade...
System log show this:
php: /pkg_mgr_install.php: The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '127', the output was '/usr/local/etc/rc.d/postfix.sh: /usr/local/sbin/postfix: not found'It's not the first time that even if a package have been removed the init scripts still alive.
-
One moment please, reinstalling packages... pkg_info: no packages match pattern(s)Don't really know what it means…
That's harmless but we've been trying to track it down.
Also, all my packages have been deinstalled but I don't know my just after the upgrade…
Someone else had that happen but we weren't able to replicate it. Near as I could tell, it was due to an upgrade that was done the last time that wasn't quite right, but the next one was OK and hasn't broken since. If someone can reliably replicate it on current snapshots that might help.
System log show this:
php: /pkg_mgr_install.php: The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '127', the output was '/usr/local/etc/rc.d/postfix.sh: /usr/local/sbin/postfix: not found'It's not the first time that even if a package have been removed the init scripts still alive.
That's up to the individual package maintainer to remove the script on deinstall. Not much to be done about that by the package system in general.
-
Thanks for those infos.
Maybe the package automatic deinstall was because my pppoe connection was down at boot time? It happen in earlier release that after a release upgrade, packages are deinstalled and then reinstalled automatically. I think yesterday it happens. Today, just de deinstall. I am impatient to see what will happen tomorrow! :-)
Just joking. I love pfSense and you all guys do a fantastic works.
Thanks -
Lack of connectivity would explain it, I suppose. Might need some extra logic there to prevent that from happening.
-
I added some code to bail on the package update if there is no connectivity when the function is called. It won't be in the next new snapshot, but the one after.
-
Oh boy. Now all packages except avahi have been automatically reinstalled…
Still, nmap gives me an error:
/libexec/ld-elf.so.1: Shared object "libpcap.so.1" not found, required by "nmap" -
Try to reinstall it now. Remove it first with "x" on the installed packages screen and then pick it from the main list.
See if it behaves any better. I bumped it up to a newer version and made sure the dependencies were fixed.
-
Ok that worked with nmap however I tried updating the snap and after that only five of my six packages git reinstalled. But after having a closer look I saw that they were not working. avahi gives me a 404 and Backup completely misssing. Tried reinstalling all packages with Diagnostics->/Backup/Restore and after that I still have the same avahi error. So I needed to remove and install it again.
At least all these removing/installing doesn't need any reboots anymore…
Thanks for your help again, jimp. Some small glitches but we're on the right way...
-
If you had the serial console hooked up while it upgraded, it would be nice to see the package reinstall messages from the console.
-
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.
