setting up svn server - Connection refused

Frank Shute frank at shute.org.uk
Fri Feb 25 14:36:39 UTC 2011


On Fri, Feb 25, 2011 at 09:23:03AM +0000, Anton Shterenlikht wrote:
>
> I'm learning how to set up svn server.
> I've read through several sections of
> http://svnbook.red-bean.com/nightly/en/
> 
> Here's what I do:
> 
> ZEEV> svnadmin create /home/mexas/zzz
> ZEEV> svnlook info zzz
> 
> 2011-02-25 09:15:28 +0000 (Fri, 25 Feb 2011)
> 0
> ZEEV> svnserve -d
> ZEEV> ps ax | grep svnserve
> 66952  ??  Ss     0:00.01 /usr/local/bin/svnserve.bin -d
> ZEEV> mkdir /home/mexas/zzz.work
> ZEEV> cd /home/mexas/zzz.work/
> 
> When I try to connect to the svn server, I get this:
> 
> 
> ZEEV> svn co svn://localhost/home/mexas/zzz .
> svn: Can't connect to host 'localhost': Network is unreachable

This sounds like it's a problem with your routing table. Does:

$ netstat -r

show a destination of localhost?

$ ping localhost

is useful.

> ZEEV> svn co svn://10.10.10.14/home/mexas/zzz .
> svn: Can't connect to host '10.10.10.14': Connection refused

That's more hopeful. Don't know what's wrong though!

> 
> ZEEV> ifconfig em1
> em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>         options=209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
>         ether 00:13:21:5b:05:1d
>         inet 10.10.10.14 netmask 0xffffff00 broadcast 10.10.10.255
>         inet6 fe80::213:21ff:fe5b:51d%em1 prefixlen 64 scopeid 0x5 
>         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
> ZEEV> 
> 
> I get exactly the same "Connection refused" if I
> connect from another host.
> 
> I turned the firewall off completely.
> 
> What could be the problems?
> 

It was a few years ago that I setup my svn repository and I referenced
the book you're using too. 

I launch it out of inetd.conf.

I've got the line:

svn     stream  tcp     nowait  frank   /usr/local/bin/svnserve svnserve -i

in there. Fixed hosts.allow to only allow machines on the lan to
connect and it works well.

Sorry I can't be more helpful but a different approach to running a
daemon permanently is probably a good idea.


Regards,

-- 

 Frank

 Contact info: http://www.shute.org.uk/misc/contact.html


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20110225/b72c79f1/attachment.pgp


More information about the freebsd-questions mailing list