2.3.2 "Unable to check for updates"/"Unable to retrieve package information"
-
Our pfsense version is 2.3.2-RELEASE-p1 (amd64) and is running on Netgate SG-8860. We are still getting the above notification from the dashboard. I attempted to upgrade pkg using the following command from the console:
pkg update; pkg upgrade pkg
and I got the following:
/root: pkg update; pkg upgrade pkg
Updating pfSense-core repository catalogueā¦
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-core/meta.txz: No route to host
repository pfSense-core has no meta file, using default settings
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-core/packagesite.txz: No route to host
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-pfSense_factory-v2_3_2/meta.txz: No route to host
repository pfSense has no meta file, using default settings
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-pfSense_factory-v2_3_2/packagesite.txz: No route to host
Unable to update repository pfSense
Updating pfSense-core repository catalogue...
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-core/meta.txz: No route to host
repository pfSense-core has no meta file, using default settings
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-core/packagesite.txz: No route to host
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-pfSense_factory-v2_3_2/meta.txz: No route to host
repository pfSense has no meta file, using default settings
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_3_2_amd64-pfSense_factory-v2_3_2/packagesite.txz: No route to host
Unable to update repository pfSense
All repositories are up-to-date.
pkg: Repository pfSense-core cannot be opened. 'pkg update' required
pkg: Repository pfSense cannot be opened. 'pkg update' required
Checking integrity... done (0 conflicting)
Your packages are up to date.All three WAN connections are working and everyone has Internet access.
Does anyone have any ideas on how to fix this?
Thanks for your time.
-
"No route to host" means the firewall can't find a route there.
Check Diagnostics > Routes, is there a default route listed? Is it for one of the working WANs?
See what "firmware.netgate.com" resolves to for you
Try a traceroute from the firewall to firmware.netgate.com to see how far it gets.
-
Yes, there is a default route.
A traceroute from the firewall to firmware.netgate.com doesn't get me anywhere:
traceroute firmware.netgate.com
traceroute to firmware.netgate.com (208.123.73.85), 64 hops max, 40 byte packets
traceroute: sendto: No route to host
1 traceroute: wrote firmware.netgate.com 40 chars, ret=-1
*traceroute: sendto: No route to host
ā¦The unusual thing was after disabling/enabling the LAN interface I was able to get an update list yesterday and was able to reinstall the packages but not enabled them. I leave the firewall on overnight and then come back in the morning and log in I get the "Unable to check for updates" message again.
addendum: I was able to get a traceroute from my workstation:
C:\Users\noel>tracert firmware.netgate.com
Tracing route to firmware.netgate.com [208.123.73.85]
over a maximum of 30 hops:1Ā Ā 4 msĀ Ā 3 msĀ Ā 3 msĀ 203.160.188.129
Ā 2Ā Ā 1 msĀ Ā 3 msĀ Ā 3 msĀ 10.1.13.9
Ā 3Ā Ā 10 msĀ Ā 3 msĀ Ā 4 msĀ 103.21.170.133
Ā 4Ā Ā 27 msĀ Ā 27 msĀ Ā 27 msĀ te0-2-0-1.br02.hkg15.pccwbtn.net [63.217.16.45]5Ā 175 msĀ 174 msĀ 172 msĀ TenGE0-3-0-1.br04.sjo01.pccwbtn.net [63.218.178.
86]
Ā 6Ā 176 msĀ 175 msĀ 172 msĀ pos3-3.cr02.sjo01.pccwbtn.net [63.218.7.10]
Ā 7Ā Ā *Ā Ā Ā 172 msĀ 174 msĀ ae16.cr2.sjc2.us.zip.zayo.com [64.125.31.14]
Ā 8Ā 218 msĀ 219 msĀ 218 msĀ ae27.cs2.sjc2.us.eth.zayo.com [64.125.30.232]
Ā 9Ā 220 msĀ 214 msĀ 215 msĀ ae2.cs2.lax112.us.eth.zayo.com [64.125.28.197]
10Ā 213 msĀ 213 msĀ Ā *Ā Ā ae3.cs2.dfw2.us.eth.zayo.com [64.125.29.20]
11Ā 220 msĀ 219 msĀ 218 msĀ ae27.cr2.dfw2.us.zip.zayo.com [64.125.30.183]
12Ā 214 msĀ 214 msĀ 214 msĀ ae7.er2.dfw2.us.zip.zayo.com [64.125.20.234]
13Ā 226 msĀ 223 msĀ 224 msĀ te-6-1-aus-core-11.zip.zayo.com [64.125.32.202]14Ā 203 msĀ 203 msĀ 207 msĀ net64-20-229-146.static-customer.corenap.com [64
.20.229.146]
15Ā 206 msĀ 205 msĀ 206 msĀ gw2.netgate.com [66.219.34.174]
16Ā 205 msĀ 206 msĀ 207 msĀ fw2.pfmechanics.com [208.123.73.4]
17Ā 206 msĀ 205 msĀ 205 msĀ firmware.netgate.com [208.123.73.85]Trace complete.
-
update (28 Nov 2016):
ISP1 is connected to the WAN interface
LAN is connected to our network
ISP2 is connected to the OPT2 interface
ISP3 is connected to the OPT4 interfaceI have made ISP3's gateway as the default gateway and this results to pfSense not being able to update the packages. When I switch the default gateway to the gateway of ISP1 then pfSense is able to update packages but will eventually go back to being unable to get updates after an uncertain length of time.
These are our observations so far.
-
I just got a crash report on the interfaces.php file in line 80. I neglected to copy the report and paste it here but I had pfSense send the report to the developers.
addendum: Here's the second crash report I got for the morning
amd64 10.3-RELEASE-p9 FreeBSD 10.3-RELEASE-p9 #1 5fc1b19(RELENG_2_3_2): Tue Sep 27 12:25:49 CDT 2016Ā Ā root@factory23-amd64-builder:/builder/factory-232/tmp/obj/builder/factory-232/tmp/FreeBSD-src/sys/pfSense Crash report details: PHP Errors: [28-Nov-2016 07:39:21 Asia/Manila] PHP Fatal error:Ā Call to undefined function pfSense_interface_listget() in /etc/inc/interfaces.inc on line 80 [28-Nov-2016 07:39:21 Asia/Manila] PHP Fatal error:Ā Call to undefined function pfSense_interface_listget() in /etc/inc/interfaces.inc on line 80
-
Don't think your crash has anything to do with your DNS problem on "ISP3 is connected to the OPT4 interface."
I had issues with unable to update or get package before. My problem is was DNS has not route or could not find a route to netgate.com, I'm sure this is your problem as well.