Commit failed Error after upgrading 1.7.7

[Bob Archer]

I recently upgraded Subversion edge to 3.2.0-3352.100 which gave me Subversion 1.7.7.

Since then every now and then when I commit I get the following error:

Commit
Commit failed (details follow):
Server sent unexpected return value (500 Internal Server Error) in response to
POST request for '/svn/manage/!svn/me'

Usually if I just retry the commit it works fine. Not a major issue, but a nuisance.

Any ideas?

[Philip Martin]

Look for more details in the apache log file.

--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download

[Bob Archer]

>> I recently upgraded Subversion edge to 3.2.0-3352.100 which gave me
>> Subversion 1.7.7.
>>
>> Since then every now and then when I commit I get the following error:
>>
>> Commit
>> Commit failed (details follow):
>> Server sent unexpected return value (500 Internal Server Error) in response to
>> POST request for '/svn/manage/!svn/me'
>>
>> Usually if I just retry the commit it works fine. Not a major issue, but a
>> nuisance.
>>
>> Any ideas?
>
>Look for more details in the apache log file.

Paul... I'm not sure which log to look in. Edge has an Error log, Subversion Log, Jetty Log, Console log.

I looked in all of those from today, the error did occur for me this AM and don't seem to find a similar error to the one listed above.

However, the jetty log does have quite a few errors listed.

BOb

[Daniel Shahaf]

Bob Archer wrote on Mon, Nov 05, 2012 at 11:39:30 -0500:
> >> I recently upgraded Subversion edge to 3.2.0-3352.100 which gave me
> >> Subversion 1.7.7.
> >>
> >> Since then every now and then when I commit I get the following error:
> >>
> >> Commit
> >> Commit failed (details follow):
> >> Server sent unexpected return value (500 Internal Server Error) in response to
> >> POST request for '/svn/manage/!svn/me'
> >>
> >> Usually if I just retry the commit it works fine. Not a major issue, but a
> >> nuisance.
> >>
> >> Any ideas?
> >
> >Look for more details in the apache log file.
>
>
> Paul... I'm not sure which log to look in. Edge has an Error log, Subversion Log, Jetty Log, Console log.
>

Philip is referring to what is normally controlled by the "ErrorLog"
httpd.conf directive. The log entries typically end in two numbers
[500, #235000].

[Bob Archer]

Does anyone have any more insite into this? I have looked in the logs and don't see anything wrt to the quoted error.

It seems to be happening on every commit, and an then an immediate retry will be successful.

Thanks,
Bob

[Johan Corveleyn]

Are these clients using serf on these connections? If so, try if
switching to neon helps.

--
Johan

[Bob Archer]

I have no idea. I am using TortioseSVN 1.7.7, which I am pretty sure defaults to neon. There is no http-library setting in the config file. So, I think it is using neon.

Also, I can't seem to figure out in Subversion Edge how to look at the configuration file.

BOb

[Mark Phippard]

If you are using LDAP and the server is on Windows there is a bug in Apache 2.2.23 that can cause an HTTP 500 on the first authenticated request for a user. See:

https://issues.apache.org/bugzilla/show_bug.cgi?id=54140

Sent from my iPad

[Bob Archer]

> If you are using LDAP and the server is on Windows there is a bug in Apache
> 2.2.23 that can cause an HTTP 500 on the first authenticated request for a user.
> See:
>
> https://issues.apache.org/bugzilla/show_bug.cgi?id=54140

Mark... that looks exactly what we are running into. Indeed we are using LDAP and running Edge on a Windows 2008 server.

Are there any plans to release a new version of Edge that will resolve this issue. It is a minor annoyance but my users freak out when they see it.

Thanks.

[Mark Phippard]

On Tue, Nov 13, 2012 at 10:22 AM, Bob Archer <Bob.A...@amsi.com> wrote:
>> If you are using LDAP and the server is on Windows there is a bug in Apache
>> 2.2.23 that can cause an HTTP 500 on the first authenticated request for a user.
>> See:
>>
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=54140
>
> Mark... that looks exactly what we are running into. Indeed we are using LDAP and running Edge on a Windows 2008 server.
>
> Are there any plans to release a new version of Edge that will resolve this issue. It is a minor annoyance but my users freak out when they see it.

Yes. As you can see, the bug was only fixed yesterday. We need to
confirm it still.

--
Thanks

Mark Phippard
http://markphip.blogspot.com/

[Bob Archer]

Ok... no hurry, "fix it right" is better than "fix it fast". I just wasn't sure if Edge releases were done even if there wasn't a new svn release. Hence my query.

BOb