Package Manger Issue
-
I'm not sure exactly when it happened, but it was as a result of one of the upgrades from
2.3 to 2.3.2 when I try to display either Installed packages / Available packages,
all I get a message "Unable to retrieve package information"Any suggestions as to how to fix this?
-
I went through the logs and found this….
Feb 16 16:35:59 xinetd 29963 Reconfigured: new=0 old=1 dropped=0 (services) Feb 16 16:35:59 xinetd 29963 readjusting service 6969-udp Feb 16 16:35:59 xinetd 29963 Swapping defaults Feb 16 16:35:59 xinetd 29963 Starting reconfiguration Feb 16 16:35:58 xinetd 29963 Reconfigured: new=0 old=1 dropped=0 (services) Feb 16 16:35:58 xinetd 29963 readjusting service 6969-udp Feb 16 16:35:58 xinetd 29963 Swapping defaults Feb 16 16:35:58 xinetd 29963 Starting reconfiguration Feb 16 16:35:57 check_reload_status Reloading filter Feb 16 16:35:57 php-fpm 18800 /rc.start_packages: The command '/sbin/ifconfig 'em1' delete '172.16.0.200'' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address' Feb 16 16:35:57 php-fpm 18800 [pfBlockerNG] Starting cron process. Feb 16 16:35:57 check_reload_status Reloading filter Feb 16 16:35:57 check_reload_status Syncing firewall Feb 16 16:35:55 php-fpm 18800 /rc.start_packages: The command '/usr/local/etc/rc.d/syslog-ng.sh stop' returned exit code '1', the output was '' Feb 16 16:35:50 supervise/syslog-ng 82446 Daemon exited gracefully, not restarting; exitcode='0' Feb 16 16:35:50 php-fpm 18800 /rc.start_packages: Reloading syslog-ng for configuration sync Feb 16 16:35:50 php-fpm 18800 /rc.start_packages: Restarting/Starting all packages. Feb 16 16:35:49 xinetd 29963 Reconfigured: new=0 old=1 dropped=0 (services) Feb 16 16:35:49 xinetd 29963 readjusting service 6969-udp Feb 16 16:35:49 xinetd 29963 Swapping defaults Feb 16 16:35:49 xinetd 29963 Starting reconfiguration Feb 16 16:35:48 check_reload_status Starting packages Feb 16 16:35:48 check_reload_status Reloading filter Feb 16 16:35:46 check_reload_status Syncing firewallThe address '172.16.0.200'' is coming from the DNSBL Virtual IP in pfBlocker which is currently deactivated.
I have also noticed that the DNS resolver is also throwing errors trying to resolve host names in aliases. (hostname removed for security)
Feb 16 16:47:55 filterdns failed to resolve host xxxxxxxxxxxxxxxxxxxxxxx will retry later again.
I don't know if this is a firewall issue (WAN has an allow any/any/any as the top rule) and there is nothing in the logs.
DNS resolution is working on clients and I can still surf the net.
from a root shell
host google.com FAILS
;; connection timed out; no servers could be reachedping 8.8.8.8 Works
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=56 time=33.534 msAny suggestions would be much appreciated.
-
The address '172.16.0.200'' is coming from the DNSBL Virtual IP in pfBlocker which is currently deactivated.
This bug should be fixed in the next release of pfBlockerNG.
-
The address '172.16.0.200'' is coming from the DNSBL Virtual IP in pfBlocker which is currently deactivated.
This bug should be fixed in the next release of pfBlockerNG.
Thank you, that is good to know…. but until that happens is there a way that I can use the command line to uninstall the package (or maybe all packages) so that I can get my system working again.
-
The error for DNSBL is a notice msg. It was trying to delete the DNSBL vip address that was assigned to that IP, but the DNSBL vip was not assigned when the code ran.
That error won't cause you any issues.
-
Thanks BBcan177…. (and to the others who put so much work into pfSense.)
I'm going to fork this post because I think there are multiple issues:
-
Fundamental design issues that may need to be addressed in pfSense - documented below
-
My current problem which is either an Unbound problem or a configuration error on my part - I'll start a new thread for this.
I'm wondering if I am the only one having these problems with the package manager, or if there is an easy work around from the command line that I may not be aware of.
Possible design issues with Package Manager
Background
All my package manager became totally nonfunctional after a restore.
I wanted to restore my configuration but uninstall pfBlocker temporarily
but couldn't because the package manger wasn't working.Issue #1
Assumption
If I understand the way things are operating the operation of the installed package list is dependent
upon fully functional Internet connectivity - have I got that part correct?Problem
If this is the case, then a package update that causes a loss of Internet connectivity creates a major
problem because there is no easy way to uninstall it. Or am i missing something?Suggestion 1
I would think that the installed packages should be displayed from the running config file (even if
it's just a degraded form to allow removal).Issue #2
Assumption
Also if I understand things correctly there is no easy way to reload all backup items EXCEPT 1 or 2.Problem
Partial restores are very messy/error prone. It is necessary to do about 20 separate restores-one
for each item on the drop down list EXCEPT the one to be excluded. Easy to forget one, or make
an error. A partial restore may also cause other problems as well.Suggestion
Make the restore UI a series of check boxes so that allow easy selection. If code to reload the config
can reload one section, it should be easy to implement this change. -
-
pkg does NOT work offline:
- https://redmine.pfsense.org/issues/6594
pkg behaves like a severe Alzheimer
- https://redmine.pfsense.org/issues/6782
Switch to DNS forwarder to get DNS working if you are unable to fix it manually.
-
All my package manager became totally nonfunctional after a restore.
I wanted to restore my configuration but uninstall pfBlocker temporarily
but couldn't because the package manger wasn't working.Maybe this was your issue?
https://redmine.pfsense.org/issues/6603
