725665 - 500 Internal Server Error when committing to svn via https

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Pascal Chevrel:pascalc]

I get 500 Internal Server Error (from Europe) when I try to commit on svn using the https protocol today, steven (CCed) who is in North America also had 500 errors in the last days.

svn: E175002: Échec de la propagation (commit), détails : 
svn: E175002: Le serveur a envoyé une valeur inattendue (500 Internal Server Error) en réponse à la requête POST pour '/!svn/me'

Comment 1

[Shyam Mani [:fox2mike]]

What version of the svn client are you on? And can you run an svn status and svn info on the path where the commit is failing?

Comment 2

[Shyam Mani [:fox2mike]]

You can get the version by running svn --version.

Thanks!

Comment 3

[Pascal Chevrel:pascalc]

I am on 1.7.2

Comment 4

[Pascal Chevrel:pascalc]

the commit path is https://svn.mozilla.org/projects/mozilla.com/trunk

Comment 5

[Pascal Chevrel:pascalc]

I can't commit either with svn+ssh protocol, I don't get an error message but the task never ends.

Also, according to viewvc, there hasn't been any commit to svn by anybody in the last 4 hours which is a long time, the problem may affects all paths.

Comment 6

[Pascal Chevrel:pascalc]

Also, I just tried in a VM with Windows XP instead (I am a linux user) using tortoiseSVN 1.7.4 and get the same error message:
Command: Commit  
Error: Commit failed (details follow):  
Error: Server sent unexpected return value (500 Internal Server Error) in response to  
Error:  POST request for '/!svn/me'

Comment 7

[Ashish Vijayaram [:ashish]]

:pascalc can you retry a commit now?

Comment 8

[Pascal Chevrel:pascalc]

Just tried, same error

Comment 9

[Steven Garrity [:sgarrity]]

Just worked for me (I had been getting the same error).

Comment 10

[Brian Hourigan [:digi]]

This should be fixed. One of our svn nodes went down early this morning (~4:12AM PST) and left a lockfile open on our NFS server. Unfortunately the application was killed mid-flight and wasn't able to release the lock

The repo was shut down for ~5 seconds, lock removed, and the repo re-opened. I confirmed with :pascalc on IRC it's now working.