@Garret
Very strange, resolving the github.com hostname times out with G_CHECK_URL but works with plain wget --spider.
The only thing I can imaging that the timeout value we use (5 seconds) is too short.
Please try:
Code: Select all
timeout=10 G_CHECK_URL https://github.com/foosel/OctoPrint.git
Or even with higher value.
Ah I see
19:19:08 and
19:19:31 as timestamps (so 23 seconds) in your error output, which is indeed veeery long.
See my output which didn't even take 1 second:
root@VM-Stretch:/mnt# wget --spider
https://github.com/foosel/OctoPrint.git
Spider mode enabled. Check if remote file exists.
--2019-03-10 19:42:15--
https://github.com/foosel/OctoPrint.git
Resolving github.com (github.com)... 192.30.253.112, 192.30.253.113
Connecting to github.com (github.com)|192.30.253.112|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location:
https://github.com/foosel/OctoPrint [following]
Spider mode enabled. Check if remote file exists.
--2019-03-10 19:42:15--
https://github.com/foosel/OctoPrint
Connecting to github.com (github.com)|192.30.253.112|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Remote file exists and could contain further links,
but recursion is disabled -- not retrieving.
Which DNS server do you use? I guess this step took so long?:
Resolving github.com (github.com)... 192.30.253.112, 192.30.253.113
If you have a router that can serve as DNS server for your local network (most do), please try to use it. You could do a quick test by adding the routers IP to /etc/resolv.conf, e.g. (in my case):
echo 'nameserver 192.168.178.1' > /etc/resolv.conf
If you use DHCP from the router, it should apply itself automatically as DNS server, otherwise you could try to use the DHCP service IP etc as static IP and then add the router IP as static DNS entry as well.
