Bugzilla – Full Text Bug Listing
| Summary: | Cannot ssh on eclipse.org servers | ||
|---|---|---|---|
| Product: | Community | Reporter: | Olivier Thomann <Olivier_Thomann> |
| Component: | Servers | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P1 | CC: | denis.roy, mikael.barbero, Silenio_Quarti |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Olivier Thomann
I think it stopped working around 12:00 yesterday. The latest build is {"build":"2016-07-13_11-00-50"}
It may be related to https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg13352.html Maybe, but none of the builds after the last one mentioned in comment 1 has been properly pushed to orion.eclipse.org. So maybe some services have not been restored after the outrage on the 14th. Any ETA for us on this? I really would like to see orion.eclipse.org being updated with a newer build than the one from July 13th. This issue has been resolved. We had to update the known_hosts file for the admin user in build.eclipse.org. Reopening. The build https://hudson.eclipse.org/orion/job/orion-node/600/ had the same failure again. It looks like the ssh connection is not reliable. Silenio, is there something that can be done to improve this? ----------------- Mon Jul 18 15:37:31 EDT 2016 ---------------- Deploying /home/data/httpd/download.eclipse.org/orion/orionode/orionode_2016-07-18_15-30-50.tar.gz to orion.eclipse.org Copying build to orion.eclipse.org Invoking upgrade script on orion.eclipse.org with archive file orionode_2016-07-18_15-30-50.tar.gz ssh: Could not resolve hostname orion.eclipse.org: Name or service not known Deploy complete in 1 seconds ------------------------------------------ Finished: SUCCESS > ssh: Could not resolve hostname orion.eclipse.org: Name or service not known
This is a DNS issue that was caused by temp maintenance. It's been fixed now. Apologies for the inconvenience.
This is still happening. It is intermittent. Usually ssh fails the first time and works after that (see below). The problem is that, in our build, we only attempt to ssh once, so the build is not deployed. Take a look at (https://hudson.eclipse.org/orion/job/orion-node/609/console) towards the end of the log. silenio@build:~> ssh admin@orion.eclipse.org ssh: Could not resolve hostname orion.eclipse.org: Name or service not known silenio@build:~> ssh admin@orion.eclipse.org Last login: Tue Jul 19 12:12:13 2016 from build.eclipse.org orion.eclipse.org orionhub.org *** Please be aware that these servers must be used for purposes approved by the Eclipse Management Organization (EMO) and/or an Eclipse Project Management Committee (PMC). Using these servers to establish outbound connections or to open ports on remote systems is PROHIBITED. Please contact webmaster@eclipse.org for info. Installing and running software applications or services on these servers must be approved by the webmaster. Please contact webmaster@eclipse.org. admin@orion:~> We changed our build scripts to use the IP address of orion.eclipse.org to work around this problem. Hopefully this ip does not change often. The IP should be fairly 'static'. Here the issue was one of the DNS slaves was failing to update so it was causing the resolution to fail every time it was asked. That has been resolved. -M. |