Skip to content

GitLab

Closed
Created by Administrator@rootOwner

Fresh installation: 100% CPU, Loading very long, page renders only on abort/waiting till timeout.

Created by: CodeBrauer

I installed today gitlab on my vserver, (Ubuntu 14.04 x64, 2x Xeons Cores, 4GB Ram, openVZ).

On the installation there were no errors - Because I'm using an apache2.4 for default webhosting, and wanted to make gitlab available with a subdomain I found this config. So I created this config and enabled that. (And also enabled the required modules of apache) Now I've edited the gitlab settings:

gitlab:
    host: git.gab3.de
    port: 8080

Now - restarted gitlab with gitlab-ctl restart and restarted my apache to make the vhost happen. And yay. GItlab was available.

But! Gitlab is very slow now: application.js gets not loaded and after the default timeout the page was rendered. And the javascript console of chrome outputs this:

[error] GET http://git.gab3.de/assets/application-d78e3aebfdf9aa068bc71234b2bfea02.js

502 Proxy Error

Also the servers shows up with 100% CPU Load. Normally a Dual Core should work with Gitlab I think? GitLab url: http://git.gab3.de/

So how could I fix that?

EDIT Here my apache vhost for gitlab