jruff's picture
jruff - Wed, 2015/01/14 - 13:55

I installed the GitLab 13.0 ISO to a Proxmox-VE virtual machine. I then rebooted and went through all of the turnkey-init configurations, including the initial package updating and rebooted. No other changes have been made. When I try to use a browser to open <host ip addr>, I get back "502 Bad Gateway". I have googled around, but have not found anything to help. <host ip addr>:12321 opens and works properly.

Any ideas would be greatly appreciated;

John

Forum: 
Support
Jeremy Davis's picture

Jeremy Davis - Sat, 2015/01/17 - 02:05

Thanks for reporting. I have added a bug report to the TKL Issue Tracker. I'll have a quick look when I get a chance to see if there is perhaps a quick workaround. Sorry that I can't do it straight away.

Jeremy Davis's picture

Jeremy Davis - Fri, 2015/01/23 - 00:15

Apologies about that. My guess is that there is that one of the auto updates is breaking things. I will have a look at it when I get a chance.

Jeremy Davis's picture

Jeremy Davis - Fri, 2015/01/23 - 23:30

After having a read of that thread I recall testing the GitLab appliance some time ago and having a similar issue - that was resolved with more RAM. I had totally forgotten about that. I recall discussing it here in the forums but a quick search didn't bring it up. Anyway it prompted me to do a little more reading too...

It seems that the 502 Nginx error is a resource issue (as per your link David). It can be worked around to a point but here is what GitLab devs say about RAM requirements. Bottom line is that anything less that 1GB and it probably won't work OOTB unless you tweak some settings...

If any of you that are experiencing this issue that are using VMs could please give your TKL GitLab VM 1GB RAM + 1GB swap (or more) and retest? Then we can hopefully confirm that this is a resource issue.

If need be I will do this test myself when I get a chance...

Jeremy Davis's picture

Jeremy Davis - Sat, 2015/01/24 - 01:44

And I can confirm this 'bug' with 512MB RAM (even with 1.5GB of swap - but without any confi changes). However I can also confirm that it works as expected (OOTB) with 1GB RAM and 1GB swap...!

So essentially this is not a bug, but relates to minimum spec requirements. If you wish to run GitLab with less than 1GB of RAM you will need to play with the config - and even then there are no guarantees...

I will also update and close the issue on GitHub...

Jeremy Davis's picture

Jeremy Davis - Sat, 2016/03/05 - 04:47
Actually that was a known issue in v14.0 but only affected systems using SysVInit (only used in Proxmox/LXC and OpenStack builds).

FWIW it will be fixed in v14.1 when it's released (very soon...)

Jeremy Davis's picture

Jeremy Davis - Sat, 2016/01/23 - 01:14
It often takes a few minutes to start. Did you wait for a little while...?
Jeremy Davis's picture

Jeremy Davis - Sun, 2016/01/24 - 04:30
There is a bug in the v14.0 LXC GitLab appliance. When we originally built it we only included a SystemD initscript; but then we had issues with SystemD inside containers. As a workaround we rep-laced SystemD with SysV but didn't include a SysV initscript.

It has been patched and a fixed version will be released as part of v14.1 which should be soon.

In the meantime if you want to have a look at it yourself this is the commit: https://github.com/turnkeylinux-apps/gitlab/commit/a9af3969640938d286046...

vialcollet's picture

vialcollet - Mon, 2016/02/01 - 00:51

Hi there 

I don't know if this is the same issue but I found this issue on github:

https://github.com/gitlabhq/gitlabhq/issues/9936

 

I did the following change and then my lxc container (ubuntu 14 and omnibus install) in proxmox worked.

# gitlab_workhorse['listen_addr'] = "/var/opt/gitlab/gitlab-workhorse/socket"

changed to:

gitlab_git_http_server['listen_addr'] = '/tmp/gitlab-workhorse.socket'

Then

sudo gitlab-ctl reconfigure
Jeremy Davis's picture

Jeremy Davis - Mon, 2016/02/01 - 03:42
Thanks for trying to help out but I doubt that this is the same issue. In TurnKey Linux (these are the TurnKey Linux support forums) we do not enable AppArmor by default in any appliance, including the GitLab appliance.
vialcollet's picture

vialcollet - Tue, 2016/02/02 - 22:09

I had tried the Turnkey appliance but also got this Bad Gateway issue.

Then I installed a git myself in a container and got the same issue that I solved as I reported above. As this seems to be linked to AppArmor on the host, I thought this may also apply to the Turnkey appliance.

Thanks for your answer.

Add new comment