cvs access problem...

shylock_1 · 02-12-2010, 07:11 PM

Hi Forum,

I am trying to access the cvs; I issue following commands :

export CVS_RSH=ssh
cvs -d anoncvs@cvs.tuxbox.org:/cvs/tuxbox -z3 co -P .

after several minute later.....

ssh: connect to host cvs.tuxbox.org port 22: No route to host
cvs [checkout aborted]: end of file from server (consult above messages if any)

I get above response. In past many occasion I access this cvs repository without any problem but now without any change in client (in my computer) the whole system kicking cvs command out altogether. I wonder what gone wrong suddenly???
I manage to update the same repository using cvs update; never had any problem before in past.

Is any one came across such sudden change in cvs access. Please guide.

Thank you in advance.

Shy.

meetscott · 02-12-2010, 10:32 PM

Are you forgetting to set CVSROOT in your environment?

I might explain your "end of file" because what you are requesting does not exist without CVSROOT being set. It would also explain the timeout because it might keep trying and failing. CVSROOT may be defaulting to /. Try:

Code:

export CVSROOT=/cvs
export CVS_RSH=ssh
cvs co tuxbox

I think you are making this a little harder than it needs to be.

shylock_1 · 02-13-2010, 06:40 AM

well I tried that too... following result I got.

[shylock_1@tomcat tuxbox]$ export CVSROOT=/cvs
[shylock_1@tomcat tuxbox]$ export CVS_RSH=ssh
[shylock_1@tomcat tuxbox]$ cvs -d anoncvs@cvs.tuxbox.org:/cvs/tuxbox -z3 co -P .
ssh: cvs.tuxbox.org: Temporary failure in name resolution
cvs [checkout aborted]: end of file from server (consult above messages if any)

Any clue what next ... ?

I setup my nameserver's from ISP provider in resolv.conf to ease a search.

I wonder what left next to cover?

Thanks for help.

shy

meetscott · 02-13-2010, 06:33 PM

I think this has nothing to do with cvs. The problem looks to be like you can't even log in with ssh. If you can't log in with ssh then that's where I'd try next.

If you can ping the server then it is likely something with ssh, like the firewall is blocking port 22 or the DNS is not finding your server's IP address. Since you didn't make any changes, I'd speculate DNS is messed up. Or an entry to your /etc/hosts file needs to be added to your client.