1.8 commit failed - nothing in the error logs
From: Andrew Reedick <Andrew.Reedick_at_cbeyond.net>
Date: Mon, 8 Jul 2013 11:18:46 -0500
I just had a commit fail midway on three different 1.8 clients without any kind of error logged in the output, in the client's Event Viewer (Win7,) or on the repo server's httpd logs (linux.) No dump file either. Starting with a fresh checkout made no difference. There's no pre-commit hook. I have used 1.8 to do merges and commits previously.
The commit did work with a 1.7.9 client (collabnet on win7 in a fresh workspace.)
1. Does anyone have any more ideas on where I can check for additional error logging? (on Win7, Cygwin clients, and Apache on a linux repo server.)
This was with three clients, "svn, version 1.8.0 (r1490375)" for all three: Cygwin svn client, TortoiseSVN, and CollabNet's client in a CMD window. Server is at 1.6.18 (r1303927) (CollabNet) over https.
I was adding a vendor branch manually:
After each failed commit, 'svn cleanup' was required since everything was still locked.
On both the cygwin client and collabnet windows client, the check-in just stopped midway at the same point without any message. The exit code was set to 1 however.
The TortoiseSVN client did create an error report, but I think it just means that TortoiseSVN is blocked (firewalled) from connecting to its error reporting server. Plus the 1.7 client commit worked, and I have used the cygwin 1.8 client to do merges and commits previously, so it "can't" be a permissions issue.
This is an archived mail posted to the Subversion Users mailing list.