Gitlab and Jenkins

Question

Hello, I’ve installed Gitlab and Jenkins on my Ubuntu 16.04 server.
It seems to work correctly except when they are both running together Gitlab will go down now and then and give me a 502, then if I refresh it works again.

Jenkins now and then will knock offline too and give me a 502 Bad Gateway.
But if Jenkins is stopped, Gitlab will work perfectly and stay up.
It just seems to be running them together. I’ve already changed Jenkins to use a different port to Gitlab. What else could this be?

Thanks

Answer 1

Woet March 11, 2017

Did you check whether you’re running out of memory?

Reply Report

domzyoung March 11, 2017

@Woet
Silly question, but what’s the best way to check that?
I’m also going to guess and say 2GB RAM isn’t going to run these both at the same time?
Reply Report
- Woet March 11, 2017
  
  Not sure, you can use free -m (look at “available”) or grep -i "oom" /var/log/syslog
  
  Reply Report
  
  domzyoung March 11, 2017
  
  @Woet
  
  I think you’re right actually. Hitting free -m shows available at like 104mb once I’ve restarted, if I then refresh gitlab page it’s like it stops and there’s more available memory again. So I guess I need to resize for more RAM if I want to run both
  
  Reply Report

Answer 2

domzyoung March 11, 2017

@Woet
Silly question, but what’s the best way to check that?
I’m also going to guess and say 2GB RAM isn’t going to run these both at the same time?
Reply Report
- Woet March 11, 2017
  
  Not sure, you can use free -m (look at “available”) or grep -i "oom" /var/log/syslog
  
  Reply Report
  
  domzyoung March 11, 2017
  
  @Woet
  
  I think you’re right actually. Hitting free -m shows available at like 104mb once I’ve restarted, if I then refresh gitlab page it’s like it stops and there’s more available memory again. So I guess I need to resize for more RAM if I want to run both
  
  Reply Report

Answer 3

domzyoung March 11, 2017

@Woet
[http://i557.photobucket.com/albums/ss14/dommzyoung01/2017-03-11_zpsdatzxwmt.png](http://)

I take it this it normal for GitLab?

Reply Report

hansen March 11, 2017

Yep, it seems like multiple people are in exactly the same boat as you - on 2GB droplet:
https://gitlab.com/gitlab-org/gitlab-ce/issues/3587
Reply Report
- domzyoung March 11, 2017
  
  @hansen
  Yeah I was able to save some memory by doing this in gitlab.rb
  
  unicorn['worker_processes'] = 2 in /etc/gitlab/gitlab.rb
  
  and
  
  sidekiq['concurrency'] = 5
  
  So we’ll see how that goes, if not I guess it’s time to increase my droplet.
  
  Reply Report

Answer 4

hansen March 11, 2017

Yep, it seems like multiple people are in exactly the same boat as you - on 2GB droplet:
https://gitlab.com/gitlab-org/gitlab-ce/issues/3587
Reply Report
- domzyoung March 11, 2017
  
  @hansen
  Yeah I was able to save some memory by doing this in gitlab.rb
  
  unicorn['worker_processes'] = 2 in /etc/gitlab/gitlab.rb
  
  and
  
  sidekiq['concurrency'] = 5
  
  So we’ll see how that goes, if not I guess it’s time to increase my droplet.
  
  Reply Report

Related

Question

Gitlab and Jenkins

Related

Leave a comment

Looking for something else?

Sign up for our newsletter

Related

Question

Gitlab and Jenkins

Related

Leave a comment

Related

question

PHP Error Log: authz_core:error - For files that don't exists on my server

question

blocked ip in spam

question

Having MongoDB Startup Errors!

question

How to make web service unavailable. As I develop this application, I'd rather not be burning up CPU or access time when not logged in.

Looking for something else?