Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326380

Summary: Hudson is not accessible
Product: Community Reporter: David Williams <david_williams>
Component: CI-JenkinsAssignee: Eclipse Webmaster <webmaster>
Status: RESOLVED FIXED QA Contact:
Severity: blocker    
Priority: P3 CC: dennis.huebner, jacek.pospychala, sbouchet, sven.efftinge
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Bug Depends on:    
Bug Blocks: 325817    

Description David Williams CLA 2010-09-28 04:04:39 EDT
When I try to access hudson, by any URL, such as 

https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/

It just spins ("loading ...") ... never responds. 

Unfortunately, since happened at evening/night ... it means a whole day will be lost in Europe. 

And, need I mention, this is the "final drive" to deliver Indigo M2, so a whole day lost is very significant, and jeopardizes staying on schedule.
Comment 1 David Williams CLA 2010-09-28 04:11:50 EDT
FWIW, I did eventually get a "bad gateway" error ... but in this case it wouldn't "go away" just by hitting reload (as it usually does) ... tried a dozen times over 4 to 6 hours. :(
Comment 2 Bouchet Stéphane CLA 2010-09-28 05:32:36 EDT
got a bad gateway after loooong minutes. 

moreover, i can ping the server : 
sbouchet@sbouchet-laptop-HP:~$ ping hudson.eclipse.org
PING hudson.eclipse.org (206.191.52.59) 56(84) bytes of data.
64 bytes from 206.191.52.59: icmp_seq=1 ttl=116 time=150 ms
64 bytes from 206.191.52.59: icmp_seq=2 ttl=116 time=166 ms
64 bytes from 206.191.52.59: icmp_seq=3 ttl=116 time=183 ms
64 bytes from 206.191.52.59: icmp_seq=4 ttl=116 time=149 ms
64 bytes from 206.191.52.59: icmp_seq=5 ttl=116 time=151 ms
^C64 bytes from 206.191.52.59: icmp_seq=6 ttl=116 time=153 ms

--- hudson.eclipse.org ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 25811ms
rtt min/avg/max/mdev = 149.643/159.302/183.808/12.349 ms
Comment 3 Sven Efftinge CLA 2010-09-28 06:15:14 EDT
For that reason (MWE, Xpand and Xtext) might not be able to participate in M2. Dennis (our release engineer) wasn't able to do anything the last couple of hours. :-(
Comment 4 Jacek Pospychala CLA 2010-09-28 07:39:25 EDT
hudson seems to be back now..
Comment 5 Denis Roy CLA 2010-09-28 07:47:23 EDT
I've just restarted the Hudson master.  The slaves seem to have followed along nicely.

I don't think Hudson appreciated me rebooting the dev.eclipse.org servers for a new kernel  :/
Comment 6 David Williams CLA 2010-09-28 10:41:03 EDT
Since its back, I'll close as fixed. 

> I don't think Hudson appreciated me rebooting the 
> dev.eclipse.org servers for a new kernel  :/

I have no idea what this means (how one could effect the other) ... but will suggest perhaps it'd be good to open against Hudson ... if there really is something they may want to do differently, to have a more robust system ... not that it would do us any immediate good ... but I'm assuming we're planning to use this for years to come, and suspect they'd appreciate hearing about "weak points" their users experience. 

Thanks.