> -----Original Message-----
> From: Ben Reser [mailto:ben_at_reser.org]
> Sent: zaterdag 1 februari 2014 02:39
> To: Steve Davis; users_at_subversion.apache.org
> Subject: Re: Possible bug in SVN 1.8.3 and 1.8.4 - file locking
>
> On 1/31/14, 1:54 PM, Steve Davis wrote:
> > :: Attempted to lock the working file
> > svn lock c:\dev\Testrepo\NewDoc.txt
> >
> > Response:
> > svn: E200035: sqlite[S19]: LOCK.lock_token may not be NULL
> > svn: E200035: Additional errors:
> > svn: E200035: sqlite[S19]: LOCK.lock_token may not be NULL
>
> What if anything is in the httpd error_log?
>
> Can you capture the network traffic between the server and the client and
> post
> it (removing Authentication headers) for the LOCK request?
>
> > I've first seen this in a Bitnami 2.3.2.1 install, and to try to make
sure it's
> > not already been fixed I just updated to a Bitnami Redmine 2.4.2.0
install:
> > Same result.
>
> I'm not familiar with Bitnami Redmine, can you tell us what version of
httpd
> you have with it?
>
> > I have tried a totally standalone collabnet svn server install of 1.8.5
on a
> > separate machine, and the locks on that are working. I then put 1.8.5
onto
> the
> > server where we're seeing the problem and once again the same problem
> occurred.
> > So this seems to be an issue occurring as a result of the configuration
setup
> > we have on that server. We do make use of an access file on that server,
so
> my
> > next test was to disable the access file setup and retry. This worked
exactly
> > as expected (by using a checkout using the local file system),
responding
> that
> > the file had been locked
> >
> > So, it would seem that this issue is related to the use of the following
> > httpd.conf settings:
> > LoadModule dav_svn_module modules/mod_dav_svn.so
> > LoadModule authz_svn_module modules/mod_authz_svn.s
> > And/or
> >
> > serving the files over https
>
> Doubtful.
>
> > And the related settings pointing to the relevant access authority file.
>
> This is more likely. Can you post your configuration?
And can you check what repository hooks are installed into your repository
by the Bitnami framework?
You can get into this exact problem if you have a pre-lock script that
produces some whitespace only output on stdout.
The output of this hook is used as lock token. (See
http://subversion.apache.org/docs/release-notes/1.6.html#hook-changes)
But in this case the surrounding whitespace is filtered and an empty token
is exactly what remains.
Bert
Received on 2014-02-02 16:26:41 CET