You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Paul van den Bergen <pa...@gmail.com> on 2007/03/20 04:17:41 UTC

subversion server on FreeBSD 6.2 - cannot connect

Hi All,

I'm trying to set up a subversion server on a miniITX box running a
freebsd server (no X) and vanilla subversion - no appache, either
straight svn or svn+ssh.

followed the basics from 2 howtos on the net - OnLamp and another (I
can't recall off the top of my head)

I can svn import, svn commit and svn checkout using the file method
from either the svn user or other users using the file:/// method.

I cannot svn to the repository using tortoise SVN from the windows XP
box on the same network.

any suggestions welcome for where to start looking - I'm all out.



-- 
Dr Paul van den Bergen

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: subversion server on FreeBSD 6.2 - cannot connect

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Mar 20, 2007, at 02:08, Paul van den Bergen wrote:

> On 3/20/07, Ryan Schmidt wrote:
>
>> On Mar 19, 2007, at 23:17, Paul van den Bergen wrote:
>>
>> > I'm trying to set up a subversion server on a miniITX box running a
>> > freebsd server (no X) and vanilla subversion - no appache, either
>> > straight svn or svn+ssh.
>> >
>> > followed the basics from 2 howtos on the net - OnLamp and  
>> another (I
>> > can't recall off the top of my head)
>> >
>> > I can svn import, svn commit and svn checkout using the file method
>> > from either the svn user or other users using the file:/// method.
>> >
>> > I cannot svn to the repository using tortoise SVN from the  
>> windows XP
>> > box on the same network.
>
>
>> Why can't you connect using TortoiseSVN? What error message
>> do you get?
>
> depends on how I try to access the server - usually something like
> "cannot connect to server" or " seerver unexpectedly disconnected" and
> occasionally "connection actively refused"
>
> I'm flailing around in the dark a bit here.
>
>> Are you also using the file:/// protocol in TortoiseSVN or are you
>> trying one of the other protocols, such as svn://, svn+ssh://,
>> http:// or https://?
>
> well, no, because file:/// only works on local hdd's right (no NFS or
> samba here)?
>
> basically this is the first step into building a small secure system.
> so starting with just svn: or maybe svn+ssh://
>
> on the BSD svn server I have svnserve running either as a deamon or as
> an inetd service. - in either case local file:/// method works. in
> both cases cannot get a connection to the box as svn or svn+ssh (this
> is a headless box that I SSH into BTW - so the network is connected.)

Ah, ok, I missed this piece of information: On the FreeBSD server,  
you can use file:/// to access the repository on the FreeBSD server.  
Then you tried TortoiseSVN on a Windows client and wanted to access  
the repo via svn:// and svn+ssh:// and that didn't work.


>> If so, can you use those other protocols from the command line?
>
> How do I do that (from the winXP box)?

I don't use Windows, but I assume you would open a DOS prompt and  
type "svn <whatever>" or possibly "C:\Path\to\Subversion\svn  
<whatever>". But let's not even worry about the Windows machine for  
now. Use the terminal of the FreeBSD machine to attempt to connect  
via svn:// or svn+ssh:// or both, whichever you want to ultimately use.


>> Is the appropriate server set up for that access protocol?
>
> Um. I don't understand the question. the server should accept svn
> incoming services, right? inetd handles the call and involces svnserve
> _or_ the deamon recognises the incoming svn or svn over ssh
> connection?  have I missed a step?

You hadn't thus far said what protocol you were using, or whether you  
had started svnserve or apache, as appropriate. That's all I meant.  
Since you're trying to access via svn://, the svnserve process needs  
to be running (or started via inetd, presumably; I'm not very  
familiar with inetd). For svn+ssh:// access, you need an ssh server  
running (and in this case, no already-running svnserve process will  
be used, but rather, svn will start an svnserve process as you log in  
via ssh, and will end the process when it's done). Obviously you'll  
also need your firewall configured to allow traffic on the ports  
svnserve (3690) or ssh (22) uses, depending on which protocol you'll  
use.


>> If your problem is limited to TortoiseSVN, and the svn command line
>> functions properly, then you need to ask the question on the
>> TortoiseSVN mailing list, not here.
>
> I don';t know where the problem lies. If you could let me know where
> the tortise SVn email list is at I'd be happy to sub to that too.

If we end up finding it's a TortoiseSVN problem, their mailing list  
is users@tortoisesvn.tigris.org and you can subscribe and read the  
archives here:

http://tortoisesvn.tigris.org/servlets/ProjectMailingListList

But try it from the command line first to try to prove TortoiseSVN's  
innocence.


-- 

To reply to the mailing list, please use your mailer's Reply To All  
function


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: subversion server on FreeBSD 6.2 - cannot connect

Posted by Paul van den Bergen <pa...@gmail.com>.
On 3/20/07, Ryan Schmidt <su...@ryandesign.com> wrote:
> On Mar 19, 2007, at 23:17, Paul van den Bergen wrote:
>
> > I'm trying to set up a subversion server on a miniITX box running a
> > freebsd server (no X) and vanilla subversion - no appache, either
> > straight svn or svn+ssh.
> >
> > followed the basics from 2 howtos on the net - OnLamp and another (I
> > can't recall off the top of my head)
> >
> > I can svn import, svn commit and svn checkout using the file method
> > from either the svn user or other users using the file:/// method.
> >
> > I cannot svn to the repository using tortoise SVN from the windows XP
> > box on the same network.
> >
> > any suggestions welcome for where to start looking - I'm all out.
>
> You need to provide more information.

OK, ask and I'll try and provide it...


Why can't you connect using
> TortoiseSVN? What error message do you get?
depends on how I try to access the server - usually something like
"cannot connect to server" or " seerver unexpectedly disconnected" and
occasionally "connection actively refused"

I'm flailing around in the dark a bit here.

Are you also using the
> file:/// protocol in TortoiseSVN or are you trying one of the other
> protocols, such as svn://, svn+ssh://, http:// or https://?

well, no, because file:/// only works on local hdd's right (no NFS or
samba here)?

basically this is the first step into building a small secure system.
so starting with just svn: or maybe svn+ssh://

on the BSD svn server I have svnserve running either as a deamon or as
an inetd service. - in either case local file:/// method works. in
both cases cannot get a connection to the box as svn or svn+ssh (this
is a headless box that I SSH into BTW - so the network is connected.)


 If so,
> can you use those other protocols from the command line?
How do I do that (from the winXP box)?

 Is the
> appropriate server set up for that access protocol?
Um. I don't understand the question. the server should accept svn
incoming services, right? inetd handles the call and involces svnserve
_or_ the deamon recognises the incoming svn or svn over ssh
connection?  have I missed a step?

If your problem
> is limited to TortoiseSVN, and the svn command line functions
> properly, then you need to ask the question on the TortoiseSVN
> mailing list, not here.

I don';t know where the problem lies. If you could let me know where
the tortise SVn email list is at I'd be happy to sub to that too.

>
>
>
> --
>
> To reply to the mailing list, please use your mailer's Reply To All
> function
>
>
>


-- 
Dr Paul van den Bergen

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: subversion server on FreeBSD 6.2 - cannot connect

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Mar 19, 2007, at 23:17, Paul van den Bergen wrote:

> I'm trying to set up a subversion server on a miniITX box running a
> freebsd server (no X) and vanilla subversion - no appache, either
> straight svn or svn+ssh.
>
> followed the basics from 2 howtos on the net - OnLamp and another (I
> can't recall off the top of my head)
>
> I can svn import, svn commit and svn checkout using the file method
> from either the svn user or other users using the file:/// method.
>
> I cannot svn to the repository using tortoise SVN from the windows XP
> box on the same network.
>
> any suggestions welcome for where to start looking - I'm all out.

You need to provide more information. Why can't you connect using  
TortoiseSVN? What error message do you get? Are you also using the  
file:/// protocol in TortoiseSVN or are you trying one of the other  
protocols, such as svn://, svn+ssh://, http:// or https://? If so,  
can you use those other protocols from the command line? Is the  
appropriate server set up for that access protocol? If your problem  
is limited to TortoiseSVN, and the svn command line functions  
properly, then you need to ask the question on the TortoiseSVN  
mailing list, not here.



-- 

To reply to the mailing list, please use your mailer's Reply To All  
function


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org