anon cvs access down?

Howdy... since forever I've been using anonymous CVS to access FreeBSD sources. For the past few weeks I've noticed that it just doesn't work (using anoncvs1.FreeBSD.org).

Ping to the box isn't even working.

Code:
# ping anoncvs1.FreeBSD.org
PING freebsd-anoncvs.liquidneon.com (216.87.78.137): 56 data bytes

Did "Liquid Neon" pull the plug or something? I'm currently switching over to creating my own local repository mirror via cvsup, which works, but wasn't something I'd been planning for.

Thanks,

Charles
 
ping is the most overrated diagnostic tool ever. Never rely on it, icmp can be disabled by firewalls easily.

Code:
$ tcping 216.87.78.137 5999                                                                                          
216.87.78.137 port 5999 open.

Code:
$ telnet 216.87.78.137 5999
Trying 216.87.78.137...
Connected to cvsup14.freebsd.org.
Escape character is '^]'.
^]

It's up and running from where I'm standing.
 
True, but...

ping is the most overrated diagnostic tool ever. Never rely on it...

Good point... though, as I should have pointed out, there are other indications that it's down (from my perspective). Here's what I'm getting:

Code:
# telnet anoncvs1.FreeBSD.org 5999
Trying 216.87.78.137...
telnet: Unable to connect to remote host

... same for port 22.

Traceroute makes it out of Comcast-land (where I'm connected, in the northeast)... but seems to get bogged down a couple hops later.

I'm left to suspect that there some weirdness going on with BGB-routing or somesuch.
 
For now, try an alternative, like the two mentioned in the Handbook: anoncvs.fr.freebsd.org and anoncvs.tw.freebsd.org (a quick check shows there is also .se, .jp).
 
Try again, Juniper issued an update yesterday that took down a couple of internet backbone providers. Should be fixed by now.
 
SirDice said:
Try again, Juniper issued an update yesterday that took down a couple of internet backbone providers. Should be fixed by now.
Still no go. I've also tried access from a server hosted in California with same result (!) Very curious... but I'm going to move on:

Thanks for all the suggestions, everyone... but the more that I think about this I think I'm better off tying our build processes to a local cvsup-mirrored repo instead of depending on always-there anoncvs access.
 
charles said:
Still no go.
That's too bad.

Thanks for all the suggestions, everyone... but the more that I think about this I think I'm better off tying our build processes to a local cvsup-mirrored repo instead of depending on always-there anoncvs access.
Yeah, that's probably a good idea. With a local CVS server you won't be as dependent.
 
Back
Top