Why don't I connect to svn.freebsd.org or svnmir.freebsd.org
曾祺元
cytseng at gmail.com
Fri Dec 11 21:37:52 UTC 2015
2015-12-12 5:17 GMT+08:00 Anton Sayetsky <vsasjason at gmail.com>:
> 11 дек. 2015 г. 23:14 пользователь "曾祺元" <cytseng at gmail.com> написал:
>
> >
> > 2015-12-12 4:07 GMT+08:00 Anton Sayetsky <vsasjason at gmail.com>:
> >>
> >> 2015-12-11 22:05 GMT+02:00 曾祺元 <cytseng at gmail.com>:
> >> > Hello FreeBSD Admins
> >> >
> >> > Because we have many freebsd servers want to update by svn (sunlit),
> so we
> >> > want to create a svn mirror site for our servers.
> >> >
> >> > We created our svn mirror site about Aug 26 refer this URL data.
> >> >
> https://www.freebsd.org/doc/en/articles/committers-guide/subversion-primer.html
> >> >
> >> > And it worked well.
> >> >
> >> > But a few days ago, we got this message from svnsync.
> >> > svnsync: E000060: Unable to connect to a repository at URL 'svn://
> >> > svnmir.freebsd.org/ports'
> >> > svnsync: E000060: Can't connect to host 'svnmir.freebsd.org':
> Operation
> >> > timed out
> >> >
> >> > We thought our server be blocked by svnmir.freebsd.org.
> >> >
> >> > So how do we apply for reconnecting to svnmir.freebsd.org or
> svn.freebds.org
> >> > ?
> >> https://www.freebsd.org/doc/handbook/svn.html
> >> >The FreeBSD Subversion repository is:
> >> >svn.FreeBSD.org
> >
> >
> > svnmir.freebsd.org = svn.freebsd.org
> > They are the same IP Address. (140.113.168.170)
> >
> > nslookup svnmireebsd.org
> > Server: 192.168.10.11
> > Address: 192.168.10.11#53
> > ~
> > Non-authoritative answer:
> > svnmir.freebsd.org canonical name = svnmir.geo.freebsd.org.
> > Name: svnmir.geo.freebsd.org
> > Address: 140.113.168.170
> >
> > nslookup svn.freebsd.org
> > Server: 192.168.10.11
> > Address: 192.168.10.11#53
> > ~
> > Non-authoritative answer:
> > svn.freebsd.org canonical name = svnmir.geo.freebsd.org.
> > Name: svnmir.geo.freebsd.org
> > Address: 140.113.168.170
> Unfortunately, I suspect your network connection problem in this case. Try
> to run traceroute.
>
> Thanks
We solve it.
More information about the freebsd-questions
mailing list