Bugzilla – Full Text Bug Listing
| Summary: | build2 is offline | ||
|---|---|---|---|
| Product: | Community | Reporter: | Nicolas Bros <nicolas.bros> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | CC: | gdupe, stepper, webmaster, zteve.powell |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Nicolas Bros
Is there anywhere where we can see why a slave is taken offline? There was a build going on it at the time (started 5 hours ago). I'm upping this to major since there seems to be no change in 5 hours. > Is there anywhere where we can see why a slave is taken offline? Actually, I believe it was not manually taken offline. On this page: https://build.eclipse.org/hudson/computer/build2/ , you can see: "Ping response time is too long or timed out." So my guess is that the connection between the master and the slave was broken, and so Hudson considers the slave as offline. Build2 is still offline. Could someone please restart it? Why is this still offline -- can we have an update, at least, please? Sorry guys, this slipped through the cracks ... I'm trying to restart it but I'm getting an error... I'll look into it. Jun 18, 2010 8:47:18 AM hudson.remoting.jnlp.Main$CuiListener error SEVERE: The server rejected the connection: build2 is already connected to this master. Rejecting this connection. java.lang.Exception: The server rejected the connection: build2 is already connected to this master. Rejecting this connection. Ok, it looks good now. offline again It's been restarted. -M. thank you! It's offline again. I've restarted the slave. -M. It's offline again Back online. -M. offline again Back online. -M. build2 is offline again Build2 has been shutdown so it can be converted into a slave host for the new Hudson instance. This was discussed here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=315643#c26 and a message was sent out to cross project last week: https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg04583.html. At this time there are no plans to return it to service as a slave for the current Hudson setup. As such I'll remove it from the running configuration. I'm going to close as 'worksforme' as all the other options seem incorrect. -M. I think this can be closed now. |