tag rename fails to delete on svnsync mirror

2014-01-30 Thread Jones, Gretchen
Can anyone explain why a tag "renamed" on the master repository is not 
replicated identically on a mirror? A new tag is created on the mirror but the 
old tag is not removed on the mirror. SVN 1.7.4


Gretchen Jones



Re: tag rename fails to delete on svnsync mirror

2014-01-30 Thread Ben Reser
On 1/30/14, 8:52 AM, Jones, Gretchen wrote:
> Can anyone explain why a tag “renamed” on the master repository is not
> replicated identically on a mirror? A new tag is created on the mirror but the
> old tag is not removed on the mirror. SVN 1.7.4

There isn't really sufficient information to give a definitive answer.  I'd
guess since you're talking about a master and mirror that you're using a
master/slave setup.  In order for changes to get from the master to the slave
there needs to be an svnsync run.  Usually that's done via a commit hook.  Are
you sure your hooks are working?



RE: tag rename fails to delete on svnsync mirror

2014-01-30 Thread Jones, Gretchen
Yes, everything is syncing perfectly (AFAIK), No errors are encountered.  

But in this case:
I create a tag on the master, it syncs to the mirror
I rename that tag on the master, it syncs to the mirror
The new tag is present on the mirror but the old tag is not removed.

My gut says it must have something to do with delete permissions, but after an 
hour of searching the listserve messages I gave up on that.

(we are not using  the post commit hook to sync, but instead a scheduled task 
script because the developers thought it (post-commit-hook) was causing too 
much delay on commits).  Again no errors, the revision numbers are perfectly in 
sync.  

The only reason this is a problem is that we use these tags to build remotely 
and it causes confusion with our non-technical build users when they see 
duplicate tags with a single character different. (We use a date in the build 
tag and someone keeps using 2013 instead of 2014)

I would expect that the same "complete" transaction that occurred on the master 
would occur on the mirror.

Gretchen Jones 

-Original Message-
From: Ben Reser [mailto:b...@reser.org]
Sent: Thursday, January 30, 2014 11:04 AM
To: Jones, Gretchen; users@subversion.apache.org
Subject: Re: tag rename fails to delete on svnsync mirror

On 1/30/14, 8:52 AM, Jones, Gretchen wrote:
> Can anyone explain why a tag "renamed" on the master repository is not 
> replicated identically on a mirror? A new tag is created on the mirror 
> but the old tag is not removed on the mirror. SVN 1.7.4

There isn't really sufficient information to give a definitive answer.  I'd 
guess since you're talking about a master and mirror that you're using a 
master/slave setup.  In order for changes to get from the master to the slave 
there needs to be an svnsync run.  Usually that's done via a commit hook.  Are 
you sure your hooks are working?




Re: tag rename fails to delete on svnsync mirror

2014-01-30 Thread Philip Martin
"Jones, Gretchen"  writes:

> Yes, everything is syncing perfectly (AFAIK), No errors are encountered.  
>
> But in this case:
> I create a tag on the master, it syncs to the mirror
> I rename that tag on the master, it syncs to the mirror
>   The new tag is present on the mirror but the old tag is not removed.

Is the rename on the master a single commit that does copy and delete,
or two commits, one for copy and one for delete?  It's still not clear
exactly what problem you are seeing. Is the problem that the commit is
present on the mirror and does not include the delete, or is the commit
missing on the mirror?

What protocol does svnsync use to access the master?

Do you have path based authz rules on the master?

Can you show us 'svn log -v -q -rN' of the commit on the master?  If there
is a corresponding commit on the mirror what does that show?

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*


RE: tag rename fails to delete on svnsync mirror

2014-01-30 Thread Jones, Gretchen
The rename is being done via the "rename" command (tortoisesvn) in the master.  
The commit on the mirror is missing the delete for the old tag.  

Only new tag exists on the master.
Both old tag and new tag now exist on the mirror.  

Gretchen Jones 

-Original Message-
From: Philip Martin [mailto:philip.mar...@wandisco.com]
Sent: Thursday, January 30, 2014 1:39 PM
To: Jones, Gretchen
Cc: Ben Reser; users@subversion.apache.org
Subject: Re: tag rename fails to delete on svnsync mirror

"Jones, Gretchen"  writes:

> Yes, everything is syncing perfectly (AFAIK), No errors are encountered.  
>
> But in this case:
> I create a tag on the master, it syncs to the mirror I rename that tag 
> on the master, it syncs to the mirror
>   The new tag is present on the mirror but the old tag is not removed.

Is the rename on the master a single commit that does copy and delete, or two 
commits, one for copy and one for delete?  It's still not clear exactly what 
problem you are seeing. Is the problem that the commit is present on the mirror 
and does not include the delete, or is the commit missing on the mirror?

What protocol does svnsync use to access the master?

Do you have path based authz rules on the master?

Can you show us 'svn log -v -q -rN' of the commit on the master?  If there is a 
corresponding commit on the mirror what does that show?

--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*



Re: Issue with pre-commit hooks in Subversion 1.7.7

2014-01-30 Thread Ryan Schmidt

On Jan 29, 2014, at 22:18, Ramachandran Raghavendran 
 wrote:

> I’m using Subversion 1.7.7 on windows with hooks written in python 2.7.2
>  
> I’m running SVNLOOK  commands in my pre-commit hook with the syntax as folow
> svnlook log -t  commit_txn   REPOS_PATH
>  
> I’m able to trap and echo the txn number in the hook but the svnlook fails 
> with the following message
> Error: svnlook: E160007: No such transaction '10271-a4o'   
>  
> I coded a sleep statement and am able to see the directory  '10271-a4o.txn' 
> in the repository/db/transaction folder.
>  
> All was well a few hours ago and now this…. 


Regarding “REPOS_PATH” above: is that taken from the first argument that 
Subversion passed to the hook script, or have you hardcoded the repository 
path? If the latter, could you have hardcoded it incorrectly? For example, has 
the repository moved, or have you copied this script to this repository from a 
different repository or have you recently added new repositories and are 
sharing this hook script amongst them all?

I’m not sure it this applies on Windows servers, but on Unix servers another 
thing to check is if the permissions of the repository are correct. For 
example, does the user the hook script is running as have permission to read 
the repository, in particular the transactions directory and this particular 
transaction file?




Subversion Service Keeps Stopping...

2014-01-30 Thread Albert, Anthony (Millennium)
Hello,

My organization is using Subversion on a Hyper-V virtual Machine (successfully 
for some time now), but just today we have been having a critical work-stoppage 
failure that I can't seem to find a solution for.

Symptoms:

-  The SVN service (svnserve.exe) is stopped, so I start it and 10 
seconds later it automatically stops again.

-  When viewing the process in the task manager, I can see that there 
is a quickly increasing amount of RAM being utilized (0 to 700MB in 10 seconds) 
and once it gets around 600MB or 700MB, it disappears from the process list 
(closes down).

-  When I launch the application 'svnserve' with the proper attributes, 
the command window gives me the following error message when it fails:  
"svnserve: Can't create thread: Not enough storage is available to process this 
command"

This is a critical work-stoppage for us and we have no idea why it sometimes 
runs for several minutes, and then sometimes it just quits after 10 seconds.  
Please let me know what is going on or what I can try...

-Tony

Anthony D. Albert
IT Specialist
Millennium Engineering
Office: 321.622.0732
Cell: 321.432.4406
aalb...@meicompany.com



Re: Subversion Service Keeps Stopping...

2014-01-30 Thread Nico Kadel-Garcia
"We have Hyper-V Virtual Machine running svnserve" is like saying "I
have this computer that has keyboard". It's missing a lot of important
details, such as Subversion version, operating system, and basic
system configuraitons like RAM and swap.

>From what you mention, it sounds like it's running out of swap and
killing the svnserve daemon. Given thqt you're apparently running it
on a Windows box, swap handling can be especially adventuresome. How
do you have it set up?

On Thu, Jan 30, 2014 at 3:08 PM, Albert, Anthony (Millennium)
 wrote:
> Hello,
>
>
>
> My organization is using Subversion on a Hyper-V virtual Machine
> (successfully for some time now), but just today we have been having a
> critical work-stoppage failure that I can't seem to find a solution for.
>
>
>
> Symptoms:
>
> -  The SVN service (svnserve.exe) is stopped, so I start it and 10
> seconds later it automatically stops again.
>
> -  When viewing the process in the task manager, I can see that
> there is a quickly increasing amount of RAM being utilized (0 to 700MB in 10
> seconds) and once it gets around 600MB or 700MB, it disappears from the
> process list (closes down).
>
> -  When I launch the application 'svnserve' with the proper
> attributes, the command window gives me the following error message when it
> fails:  "svnserve: Can't create thread: Not enough storage is available to
> process this command"
>
>
>
> This is a critical work-stoppage for us and we have no idea why it sometimes
> runs for several minutes, and then sometimes it just quits after 10 seconds.
> Please let me know what is going on or what I can try...
>
>
>
> -Tony
>
>
>
> Anthony D. Albert
>
> IT Specialist
>
> Millennium Engineering
>
> Office: 321.622.0732
>
> Cell: 321.432.4406
>
> aalb...@meicompany.com
>
>


Re: Subversion Service Keeps Stopping...

2014-01-30 Thread Thorsten Schöning
Guten Tag Albert, Anthony (Millennium),
am Donnerstag, 30. Januar 2014 um 21:08 schrieben Sie:

> -  When viewing the process in the task manager, I can see
> that there is a quickly increasing amount of RAM being utilized (0
> to 700MB in 10 seconds) and once it gets around 600MB or 700MB, it
> disappears from the process list (closes down).

You need to provide some details about the OS you are using, I suspect
a 32 Bit one and svnserve hits the 32 Bit 2 Gig per process limit.
What operation are you doing when the problem arises, a commit?

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon...05151-  9468- 55
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow