upsource and HTTP 500/502 and SVN Propfind

Hi,

I installed upsource and am using a nginx as a reverse proxy. I gave the vm 2 CPUs and 8 GB of ram. Unfortunately some user expierence a lot of HTTP-500/502-Errors which I hope are going away with higher proxy read/connect timeouts. Is there any other parameter which can be tweaked there? Also we are getting a lot of svn-requests from upsource which are mostly propfinds, which does not seem to be related to a checkout of the repository.

15 comments
Comment actions Permalink

We get always the same svn propfind commands on objets in the repository which are already ignored or not there anymore.

0
Comment actions Permalink

Hi Fabian,

Could you please post (or send to upsource-support@jetbrains.com) logs from Upsource home dir and access logs from your SVN, so we can analyze the nature and frequency of this requests.


0
Comment actions Permalink

Could you specify which logs from upsource you want? The whole log directory is 257M big.

0
Comment actions Permalink

Upsource-monitoring and upsource-analyzer folders from logs directory.

You can upload a file via https://uploads.jetbrains.com/ form and let us know the exact file name.

0
Comment actions Permalink

I send the logs to the mail address mentioned above. Since the 22.04.2015 I redirected all requests to the svn-server to 127.0.0.2 so the logs does not get spammed.

0
Comment actions Permalink

Hi Fabian,

Also, when you have a chance please drop access logs from SVN, as mentioned above. It will give us full picture.

Thanks in advance.

0
Comment actions Permalink

Sorry I forgot to attach them. I send them to the same e-mail address as before. As you can see, there are svn propfinds for these entries rotating multiple times per second (about 400 accesses in like 2 seconds). Although after they were deleted, upsource still tried to get them or the log.

0
Comment actions Permalink

Fabian,

What we found - Upsource is trying to connect to your SVN repository and find the number of last commit and for some reasons this attempt fails with the following error:

Failed to complete an action for moovel:moovel. Failed to collect current revision for moovel:moovel. svn: E175002: OPTIONS of '/svn/public_dms/moovel/trunk': 405 Method Not Allowed (https://source.dmc.de)

This attempts don't have timeouts, so it happens continuously, several times per seconds (a bit more then several J). In the version that is currently under development we added connection timeout so it shouldn't happen in the same way and SVN log wouldn't get spammed.

But it still doesn't resolve the issues with "Method Not Allowed" error.   Could you please check if Upsource is running under user account that has sufficient permissions to your SVN repository. Does "test connection" button in the project settings give any errors or warnings?


0
Comment actions Permalink

In revision 2429 are still the dependencies in the repository, which are later deleted to reduce the size of the repository. Could that be a problem? Otherwise which svn command is upsource trying to do? The user to get the svn repository has full access to it.

0
Comment actions Permalink

Upsource is trying two commands "svn info" and "svn ls". Could you please try to run these commands for the mentioned revision from the svn client? What will is say?

0
Comment actions Permalink

If I try to access a directory/file which is still there, I get the information via 'svn [ls|info] -r 2429 <path>'. But if the directory/file is deleted, I get a warning:

svn: warning: W160013: '/svn/public_dms/!svn/rvr/3323/moovel/trunk/node_modules' path not found
svn: E200009: Could not list all targets because some targets don't exist

0
Comment actions Permalink

I looked further into the matter and found that answer [0] on stackoverflow.com. As you can see the svn command used, does not work with files which are delted, but the one provided by 'Bert Huljben'. Maybe that can solve the issue?


[0] http://stackoverflow.com/questions/401331/examining-history-of-deleted-file

0
Comment actions Permalink

Hi Fabian,

Thanks for sending it, but Upsource doesn't view history of deleted files. And errors in your logs are not about not finding some files but regarding "405 Method Not Allowed". We do not have a direct answer on this error right now, but will continue investigating it.

The good news are that Upsource 2.0 will be released soon. We have improved connection algorithms there, especially in case of some errors during connect, so high load on SVN server should go away.

0
Comment actions Permalink

Thanks for the help, if we have any problems with 2.0, we will work it out then.

0
Comment actions Permalink

We get the same problems as before with upsource 2 EA.

0

Please sign in to leave a comment.