Project

General

Profile

Bug #5213

Fixing Apache Proxy timeout issues

Added by William Horner over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
14.02.2017
Due date:
% Done:

0%

Estimated time:
Sorting:
Commit Number:
Affected Version:

Description

Apache server regularly timeouts while cloning large repositories and there is little advice on how to fix it. Most advice available concentrates on push, doesnt work for clone and doesnt fix the root issue with is Apache config.

Troubleshooting the issue, there were no problems with memory, processing, disk space. gunicorn continued creating the response even after the proxy had cut the connection. So attention needs to be on the proxy config.

Adding the following to the ProxyPass statement in your standard Apache config example (in the documentation) aligns the timeouts with Rhodecode and fixes the issue:

https://docs.rhodecode.com/RhodeCode-Enterprise/admin/apache-conf-example.html

    # Url to running RhodeCode instance. This is shown as `- URL:` when
    # running rccontrol status.
    ProxyPass / http://127.0.0.1:10002/ **timeout=7200 Keepalive=On**
    ProxyPassReverse / http://127.0.0.1:10002/

Could I recommend updating the relevant lines in your documentation?

I am using the community edition. Fully up to date. Its working well other than the issue with large repositories.

Also available in: Atom PDF