Hi Bert,

        From: Bert Huijben [mailto:b...@qqmail.nl] 
        Sent: Wednesday, 25 September 2013 21:04 PM
        To: Geoff Field; 'JANIKOVIC Jan'; users@subversion.apache.org
        Subject: RE: Problem with adding files in SVN 1.8.0+. Is it in the 
tracker already?
        
        

>       I'll just reply in the html form as it will be very hard to convert 
> this thread to plain ascii and I have better things to do than spending half 
> an hour on that.

As much as Outlook (and I know you're using Outlook because the headers of your 
message include "X-Mailer: Microsoft Outlook 15.0") is a sub-optimal tool for 
traditional groups, it's not that hard to change the "Format" selection from 
"HTML" to "Plain Text".

The real problem/pain is that you then have to reformat the message to make 
sense in plain-text format.  I haven't done much to this message and it's a bit 
of a mess.

>       The information in your e-mail says that you can reproduce it on your 
> working copy; and then Philip Martin says he can't reproduce it.

I've given as much detail as I can in the various emails, but I think Philip 
has had problems getting the exact version loaded.

>       I looked through your apache log (attached in yet another followup) and 
> noticed that about every request first fails with a 401 error and then later 
> succeeds.

Yes, that seems to be happening a lot.  Even now after updating versions I'm 
getting a lot of 401s in the log.

>       What authentication configuration does your apache use?

We're using an authz file.  Specifically, we have:
<Location /Subversion/>
    Options Indexes FollowSymLinks

        DAV svn
        SVNListParentPath On
        SVNParentPath L:/Subversion/Repositories
        SSLRequireSSL
        
        # Keep these in sync with location /websvn below
        AuthType SSPI
#       AuthType None
        AuthName "Subversion repositories"
        SSPIAuth On
        SSPIAuthoritative On
        SSPIDomain AAPL
        SSPIOfferBasic On
        Require valid-user

        AuthzSVNAccessFile L:/Subversion/conf/svnaccessfile.conf
</Location>

And yes, I've just double-checked that the /websvn location is identical.

         
>       NTLM/Digest/Basic, with what backend.

Our LoadModules for auth connections include the following lines (omitting the 
commented-out ones):

LoadModule auth_basic_module modules/mod_auth_basic.so
LoadModule sspi_auth_module modules/mod_auth_sspi.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule authz_svn_module modules/mod_authz_svn.so

On the server, the Services applet gives the following Description information 
for Apache 2 (which is no longer active because it's where we get the problems):

Apache/2.0.54 (win32) DAV/2
mod_ssl/2.0.55
OpenSSL/0.9.8 SVN/1.2.3
mod_python/3.1.3
Python/2.3.5 PHP/5.0.4
mod_auth_sspi/1.0.3

If I've missed anything important, please feel free to give me more detailed 
information on what you need.

>       What is the maximum number of requests per connection?

I'm not entirely sure.  From the Apache2 httpd.conf, I see:

<IfModule mpm_winnt.c>
ThreadsPerChild 250
MaxRequestsPerChild  0
</IfModule>

I'm not entirely sure if the mpm_winnt module is enabled.


>       Can you send us your apache config (with sensitive information replaced 
> by dummy information of course)

I'll reply off-list with the full httpd.conf for Apache2.  There is nothing in 
there that I consider secret.  The authz file is another story, of course, but 
I'll send a copy of that with just the Playground repo information.

>       Thanks,
>
>                       Bert

And thanks for your attention and patience, too.

Regards,

Geoff
         

         

         

        From: Geoff Field [mailto:geoff_fi...@aapl.com.au] 
        Sent: woensdag 25 september 2013 02:25
        To: Bert Huijben; 'JANIKOVIC Jan'; users@subversion.apache.org
        Subject: RE: Problem with adding files in SVN 1.8.0+. Is it in the 
tracker already?

         

        Hi Bert,

         

         

                ________________________________

                                From: Bert Huijben [mailto:b...@qqmail.nl] 
                Sent: Wednesday, 25 September 2013 6:43 AM
                To: 'JANIKOVIC Jan'; users@subversion.apache.org
                Subject: RE: Problem with adding files in SVN 1.8.0+. Is it in 
the tracker already?

                                No,

                 

                There is no issue for this specific part of those threads 
created as nobody was able to produce a reproduction recipe for this problem to 
the developers yet. 

        Surely it would be useful to add the issue report anyway, even if there 
is no easy way to reproduce it.  After all, it is a known issue now.  We can 
then work on the reproduction recipe.

                 

                All the threads you quoted end with this request... So unless 
you add a way to reproduce the problem (perhaps with the help of the earlier 
reporters) to the discussion there is not much we can do for you at this time/

        I'm sure I postedthe method for me to reproduce it.    We were running 
a 1.2.3 server served by Apache 2.0.54 on Windows Server 2003 SP2.  I was then 
using a 1.8.1 client on Windows 7 Pro 32-bit.  I thought I'd posted my recipe 
here:

         

        http://svn.haxx.se/users/archive-2013-08/0035.shtml 
<http://svn.haxx.se/users/archive-2013-08/0035.shtml> 

        However, this is NOT the full recipe. Instead, look at this post:

        http://svn.haxx.se/users/archive-2013-08/0140.shtml

        That contains the steps I took to reliably produce errors with the 
server/client setup we had.  Unlike most of our repositories, the Playground 
repo has always been FSFS.  The problem happened with our BDB repos as well.

                The problem doesn't reproduce with the currently supported 
versions, nor with the older versions we tried to setup specifically to trigger 
the problem quoted here.

        But it's easily reproduced here, and obviously is at other sites too.

                 

                Do you see the problem in all working copies, or just in 
certain scenarios? (E.g. multiple levels of added directories? Mixed revision 
copies? Etc. etc.)

        I saw itin nearly every case.  There were rare occasions when the 
add/commit would just work, but in the majority of cases it would fail.  

                 

                                Bert

                 

                From: JANIKOVIC Jan [mailto:jan.janiko...@power.alstom.com] 
                Sent: dinsdag 24 september 2013 12:51
                To: users@subversion.apache.org
                Subject: Problem with adding files in SVN 1.8.0+. Is it in the 
tracker already?

                 

                Hello,

                 

                There seems to be a problem with the TortoiseSVN1.8.0+, which 
returns a server conflict when a new file is attempted to be added. We observed 
the problem only when adding files to the server running SVN1.5.5. No problems 
were observed when adding files to our second server, running SVN 1.7.x. There 
are further posts about this issue on the Internet, such as 
https://groups.google.com/d/topic/tortoisesvn/cGoClRBMCPc/discussion 

                or 

                
https://groups.google.com/d/msg/tortoisesvn/NggY3JzVJIY/gdEklFV2vLgJ

                 

                Is this issue already in the Subversion tracker 
(http://subversion.apache.org/reporting-issues.html)? If yes, could you please 
tell me the issue number

                 

                Kind regards

                Jan

                 

                Jan Janikovic

                ALPRO Implementation Specialist 

        Regards,

         

        Geoff 

-- 
Apologies for the auto-generated legal boilerplate added by our IT department:


- The contents of this email, and any attachments, are strictly private
and confidential.
- It may contain legally privileged or sensitive information and is intended
solely for the individual or entity to which it is addressed.
- Only the intended recipient may review, reproduce, retransmit, disclose,
disseminate or otherwise use or take action in reliance upon the information
contained in this email and any attachments, with the permission of
Australian Arrow Pty. Ltd.
- If you have received this communication in error, please reply to the sender
immediately and promptly delete the email and attachments, together with
any copies, from all computers.
- It is your responsibility to scan this communication and any attached files
for computer viruses and other defects and we recommend that it be
subjected to your virus checking procedures prior to use.
- Australian Arrow Pty. Ltd. does not accept liability for any loss or damage
of any nature, howsoever caused, which may result
directly or indirectly from this communication or any attached files. 


Reply via email to