[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Commit failed because I couldn't connect.

From: Mertens, Bram <mertensb_at_mazdaeur.com>
Date: Wed, 14 Dec 2011 09:56:03 +0100

>

Mazda Motor Logistics Europe NV, Blaasveldstraat 162, B-2830 Willebroek
VAT BE 0406.024.281, RPR Mechelen, ING 310-0092504-52, IBAN : BE64 3100 0925 0452, SWIFT : BBRUBEBB

-----Original Message-----
> From: benang_at_cs.its.ac.id [mailto:benang_at_cs.its.ac.id]
> Sent: woensdag 14 december 2011 9:35
> To: users_at_subversion.apache.org
> Subject: Commit failed because I couldn't connect.
>
> Hi, I'm a new member in the maillist. Nice to meet all of you. Now, for my
> question. This is my current system:
>
> The SVN-client: windows xp pro + Tortoise SVN 1.6.16, Build 21511
> The SVN-server: windows xp pro + WANDisco uberSVN 11.10 beta + SVN
> 1.6.17
> + XAMPP 1.7.4
>
> The SVN worked for a few weeks, but today it doesn't. This is the message
> from tortoise:
>
> Commit failed (details follow):
> OPTIONS of 'http://192.168.1.116:9880/NSsFS-2D-RBU/trunk': could not
> connect to
> server (http://192.168.1.116:9880)
>
>
> I've tried to browse the link from a browser and it also didn't work. So I
> guess the problem is at the apache server or so. My assumption is the
> apache from uberSVN and XAMPP clashed. How do I solve this? Thanks a lot
> in advance.

Welcome to the list.

Don't take this wrong, it is meant to help you, but please read http://catb.org/~esr/faqs/smart-questions.html .

Basically you are asking someone else to do your job by saying "it doesn't work" and expecting someone else to take your hand and walk you through it.

A lot of people on this list are very helpful but you need to show you at least tried to solve it and ask specific questions.

For example: how did you come to the assumption that uberSVN and XAMPP clash? If it worked for a few weeks, the config seems to at least work. What changed?

What happened? What do the log files say?
Have you tried to telnet to port 9880 on 192.168.1.116?
Can you connect to the SVN repo on that server locally (that "sweet 127.0.0.1" in your signature)?

In basic troubleshooting you start with as few components as possible: just SVN, no remote connection, no tortoise, no web server.
Then you test by adding one component at a time.
And check the log files.

Regards

Bram
Received on 2011-12-14 09:56:41 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.