Community
Participate
Working Groups
I have a cron job running on build.eclipse.org that fetches files from git.eclipse.org. It worked flawlessly for a while but failed suddenly today. Here is the 'wget ...' output: --2012-01-18 06:12:56-- (try:20) http://git.eclipse.org/c/gyrex/gyrex-releng.git/plain/org.eclipse.gyrex.releng/builder/environments/build.eclipse.org/tagging/git-submission.sh?v20120118-1045 Connecting to git.eclipse.org|206.191.52.44|:80... failed: Connection timed out. Giving up. The URL works find in my browser. Thus, I suspect a specific connection issue. Is it possible that build.eclipse.org got blocked from connecting to git.eclipse.org? I'm also wondering if it should use an internal IP when connecting instead of going through a public IP.
*** Bug 368945 has been marked as a duplicate of this bug. ***
Funny that you're getting .44 as the IP address. I get .53, which is the correct one.
(In reply to comment #2) > Funny that you're getting .44 as the IP address. I get .53, which is the > correct one. Funny? I just tried, it resolves to .44 ... but works! $ wget http://git.eclipse.org/c/gyrex/gyrex-releng.git/plain/org.eclipse.gyrex.releng/builder/environments/build.eclipse.org/tagging/git-submission.sh?v20120118-1045 --2012-01-18 09:45:33-- http://git.eclipse.org/c/gyrex/gyrex-releng.git/plain/org.eclipse.gyrex.releng/builder/environments/build.eclipse.org/tagging/git-submission.sh?v20120118-1045 Resolving git.eclipse.org... 206.191.52.44 Connecting to git.eclipse.org|206.191.52.44|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2104 (2.1K) [text/plain] Saving to: `git-submission.sh?v20120118-1045'
(In reply to comment #3) > (In reply to comment #2) Oh, and I should have said ... that is not from the build machine, but an outside network.
Our internal DNS server must have taken too long to resolve at some point, to which the external DNS servers were used. I've flushed the DNS cache on build... can you confirm that it works (from .53)?
(In reply to comment #4) > Oh, and I should have said ... that is not from the build machine, but an > outside network. Yep, the outside network should resolve to .44, which is the load balancer. From the inside (build), it should never resolve to the load balancer since it won't respond.
It works for me now: e4Build@build:~> wget -O git-stream-report.sh http://git.eclipse.org/c/e4/org.eclipse.e4.releng.git/plain/org.eclipse.e4.builder/scripts/git-stream-report.sh --2012-01-18 10:01:00-- http://git.eclipse.org/c/e4/org.eclipse.e4.releng.git/plain/org.eclipse.e4.builder/scripts/git-stream-report.sh Resolving git.eclipse.org... 206.191.52.53 Connecting to git.eclipse.org|206.191.52.53|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2248 (2.2K) [text/plain] Saving to: `git-stream-report.sh' 100%[======================================>] 2,248 --.-K/s in 0s 2012-01-18 10:01:00 (161 MB/s) - `git-stream-report.sh' saved [2248/2248]
It works now... Should build.eclipse.org have a static entry for git or the outside DNS be removed?
If we put a static entry we'll forget to change it when that specific node goes down for updates. If we remove the external DNS a lot more than just git will be broken should the internal DNS be unavailable.
Denis, wait a second ... I got .51 ... can you confirm that this is correct? gunnar@build:~$ nslookup git Server: 206.191.52.35 Address: 206.191.52.35#53 git.eclipse.org canonical name = dev.eclipse.org. Name: dev.eclipse.org Address: 206.191.52.51
(In reply to comment #10) > Denis, wait a second ... I got .51 ... can you confirm that this is correct? Yes, .51, .53 and .54 would all be correct. I'm rebooting .53 for kernel updates :)
Perfect!
