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

Bug 171436

Summary: Can't connect to CVS from emft.eclipse.org vserver
Product: Community Reporter: Nick Boldt <nboldt>
Component: CVSAssignee: Eclipse Webmaster <webmaster>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: borlander
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
Whiteboard:

Description Nick Boldt CLA 2007-01-23 13:08:35 EST
1006 nickb@emft:/tmp $ cvs -d :pserver:anonymous@dev.eclipse.org:/cvsroot/modeling -q co -d releng-common-scripts releng-common/tools/scripts
cvs [checkout aborted]: connect to dev.eclipse.org(206.191.52.52):2401 failed: Connection refused

1007 nickb@emft:/tmp $ cvs -d nickb@dev.eclipse.org:/cvsroot/modeling -q co -d releng-common-scripts releng-common/tools/scripts
can't create temporary directory /tmp/cvs-serv9571
Read-only file system

I'll keep poking at the vserver to see if it's a misconfiguration at my end, but since this just suddenly started happening since last night's outage, I'm inclined to wonder if the problem's at your end. I can connect to CVS from various places in IBMland, from dev.eclipse.org itself (node5, actually), and from home (rogers.com / Toronto), so if it's a problem at your end, it appears to be vserver-specific.

Any suggestions?
Comment 1 Nick Boldt CLA 2007-01-23 13:24:35 EST
Curiouser... I can ssh from emft.eclipse.org to dev.eclipse.org (I get node2 fairly consistently).

However, when I exit from dev back to emft, I get:

logout
-bash: /usr/bin/clear: Input/output error
Connection to dev.eclipse.org closed.

Comment 2 Nick Boldt CLA 2007-01-23 13:36:21 EST
OK, turns out it's my /etc/hosts file on emft.eclipse.org. Seems that dev.eclipse.org is not on 206.191.52.52 anymore, so commenting out that line seems to have fixed things. 

Sorry for the churn.
Comment 3 Nick Boldt CLA 2007-01-23 16:39:21 EST
Actually, it seems I have to add a static IP back into /etc/hosts to make pserver connections work; I'm guessing someone in the IP pool isn't cooperating - looks like node2 is refusing pserver connections, and without a static IP, I get one of the nodes at random (naturally) and will occasionally hit node2, getting this error again:

cvs [checkout aborted]: connect to dev.eclipse.org(206.191.52.52):2401 failed: No route to host
Comment 4 Denis Roy CLA 2007-01-23 16:45:49 EST
This has been fixed.