Unable to check for updates or Packages
-
This has been working fine up till maybe 1.5 weeks ago.
This is the error I get when the dashboard tries to check for updates to pfsense.
php: /index.php: XMLRPC communication error: php_network_getaddresses: getaddrinfo failed: hostname nor servname provided, or not knownThis is the error I get when going to the package manager.
php: /pkg_mgr_installed.php: XMLRPC communication error: php_network_getaddresses: getaddrinfo failed: hostname nor servname provided, or not known
-
Go in and re-detect your update server.
-
I've gone into System>Firmware>Updater Settings and selected "pfsense i386 stable updates" in the Default Auto Update URLs drop down. This is the url it says it's using http://updates.pfsense.org/_updaters
I think the problem is something else as I can't install any packages either as they don't show up in the package manager. It says "Unable to communicate with www.pfsense.com. Please verify DNS and interface configuration, and that pfSense has functional Internet connectivity." Pfsense has internet access as I can ping say google.com form the diagnostics menu.
-
Check your DNS resolution for pfSense.
-
pfsense.org resolves to 69.64.6.21
-
Do a traceroute to updates.pfsense.org and www.pfsense.org and post the results. Also what are your DNS servers?
-
DNS:
127.0.0.1
68.116.46.70
71.93.22.72
192.168.0.254I'm using 68.116.46.70 and 71.93.22.72 on another pfsense without problems.
Traceroute:
www.pfsense.org1 68-116--.static.mdfd.or.charter.com (68.116..) 0.499 ms 0.582 ms 0.958 ms
2 10.101.9.1 (10.101.9.1) 11.979 ms 11.527 ms 7.499 ms
3 dtr03mdfdor-tge-0-3-0-3.mdfd.or.charter.com (96.34.104.160) 11.294 ms 8.693 ms 9.025 ms
4 96-34-105-194.static.unas.or.charter.com (96.34.105.194) 19.521 ms
edr01mdfdor-tge-0-7-0-10.mdfd.or.charter.com (96.34.104.76) 11.716 ms
edr01mdfdor-tge-0-7-0-1.mdfd.or.charter.com (96.34.104.34) 11.623 ms
5 67-148-50-33.dia.static.qwest.net (67.148.50.33) 20.286 ms 18.989 ms 18.413 ms
6 sea2-pr2-ae5-401.us.twtelecom.net (64.132.69.201) 15.744 ms 15.825 ms 87.887 ms
7 lou1-ar2-xe-0-0-0-0.us.twtelecom.net (66.192.246.6) 85.217 ms 84.077 ms 102.345 ms
8 gsr1.bluegrass.net (216.135.95.6) 82.525 ms 81.608 ms 80.394 ms
9 * * *1 68-116--.static.mdfd.or.charter.com (68.116..) 0.508 ms 0.560 ms 0.948 ms
2 10.101.9.1 (10.101.9.1) 7.741 ms 11.438 ms 7.988 ms
3 dtr03mdfdor-tge-0-3-0-3.mdfd.or.charter.com (96.34.104.160) 9.910 ms 10.082 ms 8.068 ms
4 96-34-105-194.static.unas.or.charter.com (96.34.105.194) 9.011 ms
edr01mdfdor-tge-0-7-0-10.mdfd.or.charter.com (96.34.104.76) 11.630 ms
edr01mdfdor-tge-0-7-0-1.mdfd.or.charter.com (96.34.104.34) 11.664 ms
5 67-148-50-33.dia.static.qwest.net (67.148.50.33) 16.565 ms 18.660 ms 15.988 ms
6 63.146.27.46 (63.146.27.46) 35.247 ms
63.146.27.218 (63.146.27.218) 37.404 ms
63.146.27.46 (63.146.27.46) 39.908 ms
7 ae-6.r20.snjsca04.us.bb.gin.ntt.net (129.250.5.12) 28.289 ms 27.849 ms 29.329 ms
8 ae-4.r21.asbnva02.us.bb.gin.ntt.net (129.250.4.102) 97.443 ms 99.313 ms 107.269 ms
9 ae-2.r23.amstnl02.nl.bb.gin.ntt.net (129.250.2.145) 185.785 ms 180.004 ms 180.381 ms
10 ae-2.r02.amstnl02.nl.bb.gin.ntt.net (129.250.2.159) 192.140 ms 183.189 ms 183.874 ms
11 kpn-2.r02.amstnl02.nl.bb.gin.ntt.net (81.20.64.27) 183.825 ms
kpn-1.r02.amstnl02.nl.bb.gin.ntt.net (81.20.64.26) 187.810 ms
kpn-2.r02.amstnl02.nl.bb.gin.ntt.net (81.20.64.27) 192.835 ms
12 nl-asd-dc2-ias-arg37-te-3-0-0.kpn.net (139.156.113.157) 181.814 ms 185.347 ms 182.049 ms
13 139.156.72.238 (139.156.72.238) 181.059 ms 190.087 ms 187.286 ms
14 * * *Thanks for your help
-
This makes no sense to me. None. Sorry…
-
This is something more than just network problem. If if was a problem with DNS or upstream filtering you would see a more sane error message such as "unable to check for updates".
Have you installed or uninstalled any packages?Steve
-
I first noticed the problem after I was setting up and testing a couple ipsec tunnels. Sometime during the process of setting that up I noticed this problem. I'm 99.9% positive it was working before this point.
-
Are you routing your network through the IPSEC tunnels?
-
Nope. I also have about 20 workstations behind pfsense that have no issues reaching the internet. Also at the moment ipsec is configured but I don't have the tunnels established, intentionally.
-
Try getting rid of 127.0.0.1 DNS…..just for testing.
-
I removed both 127.0.0.1 and 192.168.0.254 from the dns. No change
-
Have you rebooted the firewall?
-
yup I rebooted as well after removing them.
-
Are you still seeing the php errors you referenced in your first post? Or the more expected error you quoted in your second post?
Steve
-
This is the error I was getting in my first topic http://forum.pfsense.org/index.php/topic,51619.0.html
php: /index.php: XMLRPC communication error: Operation timed out
At some point before starting this thread I stopped seeing this error.Since then these are the only two errors I'm seeing.
php: /pkg_mgr_installed.php: XMLRPC communication error: php_network_getaddresses: getaddrinfo failed: hostname nor servname provided, or not known
php: /index.php: XMLRPC communication error: php_network_getaddresses: getaddrinfo failed: hostname nor servname provided, or not known
-
These PHP errors are an indication that something is more seriously awry. You shouldn't be seeing those at all.
Steve
-
I'm getting a 404 on http://updates.pfsense.org/_updaters
-
404 is the correct response from that URL.
If you want to see something try http://updates.pfsense.org/_updaters/version which returns a small file with the current version number.
Steve
-
Thanks. Didn't intend to hijack… I thought it was related.
-
Just to add here, i also have this problem.. for weeks now mine has been saying it cant get update info. Changed nothing.. if i go in and change the update servers still the same. I didnt care too much as i didnt really want to upgrade as mine is running smoothly
-
Is there any files or logs we can look at to help track this down?
-
Seeing those PHP errors often means some file is missing or corrupted. Have you installed/uninstalled any packages?
If there is nothing helpful in the system log then it would a matter of digging in the code to see what is being passed to the php code that it can't handle and why.You may have found a legitimate bug of course.
At this point, unless you really have a need to know why this happened, I would probably reinstall and see if it is repeatable.
Steve
Edit: You could look in /tmp/PHP_errors.log
