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

Re: repos not accessible after log files removed (II)

From: Jan Hendrik <jan.hendrik_at_bigfoot.com>
Date: 2003-10-01 13:28:51 CEST

Thanks for the all replies and sorry for the delay on my side, but I
was out yesterday. This will become rather long though and
perhaps a debug would be more informative if only someone could
instruct me what to do - I have only very vague ideas about
debugging. And if it needs to make and build and compile a special
version first I would be lost anyway ...

Concerning Re: repos not accessible after log
John Peacock wrote on 30 Sep 2003, 10:19, at least in part:

> Michael Wood wrote:
>
> > He's saying that http:// between two machines causes the problem
> > more frequently than http://localhost/ or file://, but the problems
> > still occur with http://localhost/ and file://.

Thanks for straightening out what I tried to say, Michael! That's
exactly how it seems to be. Usual scenario is I recover the repos
sitting at the server machine, start Apache again and access the
repos with CL client, TSVN and browser (MS IE 5.5 & Opera)
several times with both file:// and http://. Mostly things are fine.
Then I go up to my machine and start doing the same things with
http:// only and it does not take long and the repos is corrupted
again. But as said, sometimes it already starts again while still
being at the server machine.

> If that is what he is saying (and I agree that seems plausible), it
> makes no sense. Apache treats localhost connections identically to
> network connections (except for purposes of authorization). It all
> goes through the same IP stack.

I would expect that, too.

> Is this FAQ applicable?
>
> http://subversion.tigris.org/project_faq.html#windows-xp-server

No, don't have XP. And no, I do not access the repos through file://
on the network drive (though mapped on my machine as J:\). No
machine runs a virus scanner in the background. I'll try to describe
the environment more precisely:

The server is a P4 1.6GB box, 128 MB RAM, 10/100 LAN, W2K
Pro SP2, FAT32, no AV, no firewall, Apache 2.0.47 as service (no
problems since setup about 6-7 weeks ago). SVN was .27 for
about the same time, problem began about a week ago and
persisted after dump/load to a new .30 repos.

My machine is a P200, 144 MB RAM, 10 Mbit LAN, W2K Pro
SP2, FAT32, no AV, Kerio Firewall 2.1.5 with SVN/TSVN allowed
on any ports with local network mask, Apache running with no
problems since mid/end July. SVN started with .25, updated to .27,
now updated together with the above machine to .30.

The repos that started the trouble was originally created on my
machine as a test repos and filled with live data from our website
projects. At first accessed with file:// + svn:// (few time only), later
with http://, too. When I had become familiar with basic SVN the
repos developed into a semi-production repos, that is I kept a few
private copies of other's website projects and committed/updated
them to the repos by both file:// and http://, just as if it had gone
live already. In a second step I copied the repos to the first
machine which shall become the server and relocated my "private"
working copies accordingly. As things still went well I finally moved
the original website projects out of way and checked out working
copies from the repos to start production. For about 10 days this
worked as well, though there were only few commits due to current
work cycle here. At any time it was on the same machine as
Apache. The partition of the repos has ample space (6-8 GB).

I had, however, kept a copy of the repos on my machine for later
tests and further learning. Only test since was removing unused
logfiles.

Trouble began shortly after removing logfiles of the production
repos. I then tried the kept test repos and run into the same things.
Removing logfiles seemed to be the connecting line and at first
things looked like to become stable again when restoring logfiles
from ZIP file before doing a recover. For the update to .30 I did the
dump with logfiles restored.

Obviously when the repos becomes inaccessible on an update or
commit command a pending transaction is left over. I found a few
and removed them, but no cure.

No other soft/hardware installed but the SVN/TSVN updates.

Does this give any clue? Can I give more specific, technical
information? I really like SVN for ease of use, but at some point
something must have gone wrong here and is staying wrong ...

TIA - Jan Hendrik

---------------------------------------
Freedom quote:

     The government's view of the economy
     can be summed up in a few short phrases:
     If it moves, tax it. If it keeps moving, regulate it.
     And if it stops moving, subsidize it.
                -- Ronald Reagan

---------------------------------------
Mailed with Pegasus Mail 3.12c (32bit).
Never heard of it?
Easy to use, full featured - and freely available.
And *no* automatic virus activation and spreading.
Take a look at http://www.pmail.com
Give it a try - and you'll never miss anything else.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 1 13:27:28 2003

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.