You are here
Pete - Fri, 2015/12/04 - 21:33
Hi Guys,
I deployed the ova template of the latest turnkey-gitlab and everything was working fine. If we leave it for some time (possibly overnight) then when accessing the site we receive 502 Bad Gateway. Running with 4Gb RAM and most issues i have seen relate to memory issues when runngin with 512MB or 1GB RAM so not sure this would be the issue.
Anyone experienced this with the latest version and could possibly shed some light?
Thanks,
Pete
Forum:
Tags:
Hmm that is weird...
Obviously the Nginx front end is running (otherwise you wouldn't be able to connect at all). Probably the first thing to check is whether GitLab itslef is running. something like:
Assuming one of those is not running the GitLab log (/home/git/gitlab/log) may give you some hints on what the issue is. If those services are running then I'd check the Nginx error log (/var/log/nginx/gitlab.error.log) for clues.upping RAM to 8GB seems to have fixed it for now
I doubled the RAM on Friday night as a test and everything is running smoothly this morning when I checked so unable to check service status. I do see the below in the gitlab.error.log file around the time it failed on Friday
also looking through the GitLab Logs (/home/git/gitlab/log/unicorn.stderr.log) I see a large number of "exceeds memory limit" errors ... interestingly enough these errors were logged when the system failed and also now while the system is working?
I will post some more information if it fails again with 8GB RAM
Thanks very much
Pete
Do you have lots of users?
If RAM is a precious commodity; then you could always add more swap (instead or as well as) and see how that affects performance; suggestion here
Only 2 users via LDAP
Only change from vanilla install was to enable LDAP integration and then 2 users were auto-created when they logged in before we started seeing the issue
I will let you know if I see any failures after upgrading to 8GB RAM
Where are you running this?
Add new comment