Re: Multiple Apache webdav servers sharing repositories via NFS

[Ryan Schmidt]

On Sep 7, 2013, at 19:24, Nico Kadel-Garcia wrote:

> > http://www.pbs.org/wgbh/evolution/library/01/6/l_016_08.html
> 
> *Do not do this* with write access repositories, is my advice from knowledge 
> of NFS filesystems. Writes, and partial writes, can occur from one host for 
> the next "commit" but not actually be seen on the next "round robin" server 
> until a fairly arbitrary amount of time later, due to propagation delays 
> inherent in NFS. There's a lot tht NFS can do well, but this is not one of 
> those tasks.
> 
> I'd really encourage you, for commercial graide high availability or load 
> distribution, to look at WanDisco's "Multi-Site" or to use a failover load 
> balancer setup. If server 1 goes toes up, serer 2 is available, and handles 
> all the traffic. But mixing and matching back and forth randomly as can 
> happen with round-robin? That sounds like a dangerous idea likely to bite you 
> at really, really bad moments due to simultaneous commits through two 
> different NFS enabled front ends.

It sounds like a great idea, *if* you are using a SAN with a cluster 
filesystem, such as Apple's Xsan. NFS is not a cluster filesystem so that would 
not be a good idea.

Re: Multiple Apache webdav servers sharing repositories via NFS

[Nico Kadel-Garcia]

> http://www.pbs.org/wgbh/evolution/library/01/6/l_016_08.html

*Do not do this* with write access repositories, is my advice from
knowledge of NFS filesystems. Writes, and partial writes, can occur from
one host for the next "commit" but not actually be seen on the next "round
robin" server until a fairly arbitrary amount of time later, due to
propagation delays inherent in NFS. There's a lot tht NFS can do well, but
this is not one of those tasks.

I'd really encourage you, for commercial graide high availability or load
distribution, to look at WanDisco's "Multi-Site" or to use a failover load
balancer setup. If server 1 goes toes up, serer 2 is available, and handles
all the traffic. But mixing and matching back and forth randomly as can
happen with round-robin? That sounds like a dangerous idea likely to bite
you at really, really bad moments due to simultaneous commits through two
different NFS enabled front ends.


On Wed, Sep 4, 2013 at 10:49 PM, Cheyenne Wills wrote:

> I've done several searches, and have found old and conflicting responses
> to the question of sharing a repository via NFS. So what is the current set
> of concerns with sharing repositories using NFS among several web servers?
>
> Here is the scenario, several hundred repositories shared via NFS to a
> couple of webdav (Apache mod-svn) servers.  The Apache servers set up via a
> round-robin DNS server (thus they are all sharing a common virtualhost
> name).  All user access is via webdav (authentication and access controlled
> by an Apache authentication handler).  The users will see a common hostname
> for all repositories.  All the servers are "network close" to each other.
>
> Assuming that the NFS is current (NFS 4) with subtree checking disabled
> (as per the FAQ), are there any gotcha's or other concerns.
>
> I currently have a solution using some custom Apache proxying that is
> working, but I'm looking at trying to simplify my solution.
>

Re: corrupted svn repository with “serialized hash missing terminator” error

[Andreas Mohr]

Hi,

On Sat, Sep 07, 2013 at 05:50:29PM +0530, Nitin Bhide wrote:
>Philip/Stefan/Andreas,
> 
>Thanks for the help. I was able to write a small python script
>specific to
>my needs and recover the repository. It was corrupted revision
>property
>file. I have written the details in blog post.
>
> [1]http://nitinbhide.blogspot.in/2013/09/recovering-from-corrupted-subversion.html

Thanks for openly documenting/sharing your experience!
(and of course congrats for your smashing success)

Now a question that would spring from this would be whether this is
something that could be more automated in Subversion project circles
(for this one user who was nicely able to draw the necessary conclusions
and then even write his own tool, there's probably a dozen more users
who gave up in despair).
That's probably not a feature that svnadmin ought to provide ("form
intermediate revisions out of thin air when encountering corruption in
certain revisions"), but rather an external recovery tool that's made
for that purpose.
But those are just random thoughts of someone who's quite external to all
this... ;)

Andreas Mohr

-- 
GNU/Linux. It's not the software that's free, it's you.

Re: Subversion WC on NFS -- doesn't work again

[Lev Serebryakov]

Hello, Lev.
You wrote 7 сентября 2013 г., 16:02:19:

LS>  FAQ says, that it should work, but for me it doesn't see WC as WC at all:
  Oh, sorry for noise, "rpc.lockd" crashed and I didn't notice that.

-- 
// Black Lion AKA Lev Serebryakov 

Re: corrupted svn repository with “serialized hash missing terminator” error

[Nitin Bhide]

Philip/Stefan/Andreas,

Thanks for the help. I was able to write a small python script specific to
my needs and recover the repository. It was corrupted revision property
file. I have written the details in blog post.
http://nitinbhide.blogspot.in/2013/09/recovering-from-corrupted-subversion.html

Thanks again (especially Philip),

Regards,
Nitin


On Fri, Sep 6, 2013 at 2:36 PM, Philip Martin wrote:

> Nitin Bhide  writes:
>
> > Thanks for the clarification. Does the message mean either in db/revs or
> in
> > db/revprops 'END' tag is missing ?
>
> It means the file ended before the END tag was seen, but it's not
> possible to say exactly what is missing.
>
> --
> Philip Martin | Subversion Committer
> WANdisco // *Non-Stop Data*
>



-- 

In theory, there is NO difference between theory and practice.
But, in practice, there IS

Yogi Berra

My company's new product : BootstrapToday - Simple and Sensible Application
Lifecycle Management
http://www.bootstraptoday.com

Subversion WC on NFS -- doesn't work again

[Lev Serebryakov]

Hello, Users.

 FAQ says, that it should work, but for me it doesn't see WC as WC at all:

% mount | grep /usr/home
192.168.134.2:/usr/home on /usr/home (nfs)
% svn status
svn: warning: W155007: '/usr/home/lev/FreeBSD/ports' is not a working copy
% ls -la | grep svn
drwxr-xr-x   4 lev  lev 512 Sep  7 15:58 .svn
% ssh 192.168.134.2 'svn status /usr/home/lev/FreeBSD/ports'
M   /usr/home/lev/FreeBSD/ports/www/serf/Makefile
M   /usr/home/lev/FreeBSD/ports/www/serf/distinfo
A   /usr/home/lev/FreeBSD/ports/www/serf/files
A   /usr/home/lev/FreeBSD/ports/www/serf/files/patch-SConstruct
M   /usr/home/lev/FreeBSD/ports/www/serf/pkg-plist
% svn --version | head -1
svn, version 1.8.3 (r1516576)
% ssh 192.168.134.2 'svn --version | head -1'
svn, version 1.8.3 (r1516576)
%


-- 
// Black Lion AKA Lev Serebryakov 

RE: SilkSVN client crashing

[Bert Huijben]

Hi,

 

Ivan Zhakov and I checked the minidump but the only thing we could find
using the dump is that the application fails when writing an error message.

 

So ‘some error’ occurred while producing the log, but we don’t know which
and somehow the handling corrupted the error state. We are looking for a way
to get more information.

 

 

As part of this investigation we started publishing the debug symbols for
the SlikSvn binaries on http://sliksvn.com/pub/symbols/. 

 

If you know your way around Visual Studio and/or another debugger you might
be able to help us. It might also help to just copy the right .pdb files
next to the .exe/.dll files as that improves the debug output in the .log
file.

 

Bert

 

 

From: Bjarne Grönnevik [mailto:bjarne.gronne...@netent.com] 
Sent: vrijdag 6 september 2013 16:54
To: Bert Huijben; users@subversion.apache.org
Subject: RE: SilkSVN client crashing

 

Hi again Bert,

 

I updated to 1.8.3 and the error is still present.

 

Some extended info about this:

-  I can’t reproduce the crash by running the command on the regular
windows command-line.

-  It happens quite “reliably” when I run the same command from the
python script.

-  The commands seem to be failing when the resulting log is
extensive(like been in development since 2008 with regular updates).

-  I seem to be able to avoid the error using the –l flag(in this
particular case this is fine as I don’t want anything more than a few of the
last entries anyway)

 

See attachment of the python script, its output and the crash log and dump.

I hope that helps.

 

Cheers

/Bjarne

 

From: Bjarne Grönnevik 
Sent: den 6 september 2013 16:09
To: 'Bert Huijben';  
users@subversion.apache.org
Subject: RE: SilkSVN client crashing

 

Hi Bert

 

Sure, I’ll attempt to provoke it with that version.

Get back to you soon with the results.

 

/Bjarne

 

From: Bert Huijben [  mailto:b...@qqmail.nl] 
Sent: den 5 september 2013 10:00
To: Bjarne Grönnevik;  
users@subversion.apache.org
Subject: RE: SilkSVN client crashing

 

Hi Bjarne,

 

Can you run the

svn  log

https://svn.netentertainment.com/cm_games_ng/igames/blacklagoon/blacklagoon-
common/trunk

command.

 

With SlikSvn 1.8.3 (which is available on http://sliksvn.com/en/download)
and if you can reproduce the result send me the log and dump files?

 

Thanks,

Bert

 

 

From: Bjarne Grönnevik [mailto:bjarne.gronne...@netent.com] 
Sent: donderdag 5 september 2013 09:38
To: users@subversion.apache.org  
Subject: SilkSVN client crashing

 

Hi

 

I’m scripting svn via a Python Script and as you can see in the run-log.txt,
svn seems to fail at random occasions(see crash logs). Or at least for
reasons unknown to me.

 

And as the error message suggest helping out by mailing here, I did.

 

Svn version is: svn, version 1.8.1-SlikSvn-1.8.1-X64 (SlikSvn/1.8.1) X64,
compiled Aug 26 2013, 16:52:34 on x86_64/x86-microsoft-windows6.1.7601

 

Os is: Windows 7 Enterprice, 64-bit, Service Pack 1

 

/Bjarne

 

 


Bjarne Grönnevik


Client Developer

Net Entertainment NE AB, Luntmakargatan 18, SE-111 37, Stockholm, SE 
T: +46 709 124 588, M: +46 709 124 588, F: +46 8 578 545 10 
  bjarne.gronne...@netent.com
 www.netent.com 

Better Games

 

This email and the information it contains are confidential and may be
legally privileged and intended solely for the use of the individual or
entity to whom they are addressed. If you have received this email in error
please notify me immediately. Please note that any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of the company. You should not copy it for any
purpose, or disclose its contents to any other person. Internet
communications are not secure and, therefore, Net Entertainment does not
accept legal responsibility for the contents of this message as it has been
transmitted over a public network. If you suspect the message may have been
intercepted or amended please call me. Finally, the recipient should check
this email and any attachments for the presence of viruses. The company
accepts no liability for any damage caused by any virus transmitted by this
email. Thank you.