JIRA Subversion Plugin 504 Gateway Time-out

[Thomas]

Hi

I have a problem while trying to add subversion repository.

I want to use http protocol. I have this error:

An error occured while activating the connection: svn: E175002: OPTIONS of '/rep_name': 504 Gateway Time-out (http://server_adres)
svn: E175002: OPTIONS request failed on '/rep_name'.

I can reach repository from the server using browser without any problems.

I dont have much option here to setup plugin.

No matter what http address I use, I have same error (gateway time-out)

Any ideas? What could it be?

Jira: 6 with Subversion Plugin: 0.10.13

[Mark Symons · Accepted solution]

Does this help?

SVN is using old proxy configuration

[Thomas]

Do you mean svn server?

We still have our old (but current) jira 4 with subversion plugin 0.10.7 and it is connected to the same svn server. Of course there's no problem.

Do I need to configure something extra in jira 6 or svn server?

[Mark Symons]

Sorry, Thomas. I provided a bad link... pointing back at this question and not at the SVN-384 issue that I intended to. All fixed now via an edit.

If SVN-384 is a false lead, then there's still a couple of things to investigate.

Your JIRA logs report "http://server_adres". Is that address the address of your proxy server?


If it is, then have you spoken to the administrator of that proxy server? Get them to answer why it is that one of your JIRA servers has a problem and the other does not. I'm presuming that your JIRA v4 server has the same proxy configuration required to get UPM working.

Maybe there logs will help explain why there was an HTTP 504. It might not be that the proxy is timing out connecting to SVN. HTTP 504 is defined as:

   The server, while acting as a gateway or proxy, did not receive a
   timely response from the upstream server specified by the URI (e.g.
   HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed
   to access in attempting to complete the request.

Note the reference to "auxiliary server".

[Thomas]

Thank you Mark. You were right, it was all about proxy. I set proxy in setenv.sh because jira market is outside our network. without that proxy settings of course subversion plugin works. Now I have to find out how to exclude subversion plugin from that rule.

Subversion plugin is finally able to connect to svn server. Since our new jira 6 is a standalone version there is a small issue. Subversion plugin tries create folder .subversion/auth/svn.simple in /home/jira directory. Unfortunately for standalone version, jira instalation package creates user "jira" but without home directory. I added in setenv.sh additional line: -Duser.home=/opt/atlassian/jira

I thought that this solve the problem but unfortunately it does not. now I have this:

An error occured while activating the connection: svn: E204899: Cannot create directory '/opt/atlassian/jira/.subversion/auth/svn.simple'.

It looks like permission issue for jira user. Any sugestion?

[Thomas]

Thank you Mark.

Proxy was the problem.

[Mark Symons]

Have you looked at the logs on your Subversion server?

Just one week ago, I had some unexpected HTTP errors relating to a Jenkins plugin showing up in my JIRA logs. The Glassfish logs for the Jenkins server had events that correlated. Events that had a totally different "take" on the problem and which allowed the problem to be fixed very quickly indeed.

If your Subversion logs contain nothing at all then even that is useful...confirming that the HTTP 504 is coming from somewhere else (proxy).

Seeing as how you are using HTTP (not encrypted) then it might be useful to try an use a tool like Wireshark to look at the actual traffic. That would let you better compare your browser connection (which is working) with your Subversion Plus plugin connection (which is not).

[Kinto Soft]

The original question is regarding the Atlassian's plugin rather than Subversion Plus ;).

Well, @Thomas is welcome to the Subversion Plus community if he want to make the change.

[Mark Symons]

Whoops. Yes, the question was indeed about Subversion rather than Subversion Plus. My mind filtered out the "0.10.13" tell-tale.

Despite that, my advice is unchanged... have a look at the Subversion server logs, etc.

[Thomas]

Ok I checked and on the SVN server side log shows nothing. It looks like the problem is on the jira server side. In logs I dont see nothing additional besides that "504 gateway time-out" message.

We had problems with connection to the jira market so I added this line in setenv.sh file:

JVM_SUPPORT_RECOMMENDED_ARGS="
-Dhttp.proxyHost=proxy -Dhttp.proxyPort=80"

But I dont think it has something to do with this problem.

Any idea how to fix it?

[Kinto Soft]

Not always it is the same, browsers sometimes are configured for autologin in proxies, for instance.

[Thomas]

I used links (console browser) just for test, on the same server where jira is. This browser isn't configured in a particular way.