502: Whoops, GitLab is taking too much time to respond

[tskamath]

Hi,

I am writing this after a week of trying to resolve this issue myself. I am running it on DS412+, I cannot get past the 502 page, irrespective of what I do. if you could guide me, it would be great.

Thanks in advance Srikanth Kamath

Configuring nginx::gitlab... stdout 06:00:29 2017-05-31 06:00:29,851 CRIT Supervisor running as root (no user in config file) stdout 06:00:29 2017-05-31 06:00:29,852 WARN Included extra file "/etc/supervisor/conf.d/gitlab-workhorse.conf" during parsing stdout 06:00:29 2017-05-31 06:00:29,852 WARN Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing stdout 06:00:29 2017-05-31 06:00:29,852 WARN Included extra file "/etc/supervisor/conf.d/mail_room.conf" during parsing stdout 06:00:29 2017-05-31 06:00:29,852 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing stdout 06:00:29 2017-05-31 06:00:29,852 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing stdout 06:00:29 2017-05-31 06:00:29,852 WARN Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing stdout 06:00:29 2017-05-31 06:00:29,853 WARN Included extra file "/etc/supervisor/conf.d/unicorn.conf" during parsing stdout 06:00:29 2017-05-31 06:00:29,971 INFO RPC interface 'supervisor' initialized stdout 06:00:29 2017-05-31 06:00:29,971 CRIT Server 'unix_http_server' running without any HTTP authentication checking stdout 06:00:29 2017-05-31 06:00:29,999 INFO supervisord started with pid 1 stdout 06:00:31 2017-05-31 06:00:31,006 INFO spawned: 'sidekiq' with pid 507 stdout 06:00:31 2017-05-31 06:00:31,010 INFO spawned: 'unicorn' with pid 508 stdout 06:00:31 2017-05-31 06:00:31,018 INFO spawned: 'gitlab-workhorse' with pid 509 stdout 06:00:31 2017-05-31 06:00:31,023 INFO spawned: 'cron' with pid 510 stdout 06:00:31 2017-05-31 06:00:31,029 INFO spawned: 'nginx' with pid 511 stdout 06:00:31 2017-05-31 06:00:31,034 INFO spawned: 'sshd' with pid 512 stdout 06:00:32 2017-05-31 06:00:32,399 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) stdout 06:00:32 2017-05-31 06:00:32,399 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) stdout 06:00:32 2017-05-31 06:00:32,400 INFO success: gitlab-workhorse entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) stdout 06:00:32 2017-05-31 06:00:32,400 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) stdout 06:00:32 2017-05-31 06:00:32,400 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) stdout 06:00:32 2017-05-31 06:00:32,401 INFO success: sshd entered RUNNING sta

[jboxberger]

Hello Srikanth,

have you upgraded the RAM of your NAS? It looks like Gitlab is running out of RAM. You need at least 2GB (better 4GB) to run Gitlab properly. https://docs.gitlab.com/ce/install/requirements.html#memory

Here is a short DS412+ RAM Upgrade Tutorial: https://www.youtube.com/watch?v=HeRbuYwqx-M

Please let me know if you have already upgraded your RAM but the error remains.

Kind Regards

[tskamath]

Dear Juri,

Thanks for the quick revert, have some dead laptops with memory, will check after upgrade, thanks once again, you saved me from wasting time trying to get GitLab to run, by tweaking the install & environment variables.

Managed to run Gogs, its quite ok, work good.

Thanks & Regards

Srikanth Kamath, Email: srikanth@tskamath.com Phone: +91 99001 60797 http://tskamath.pactindia.net http://www.tskamath.com CIN: U74900KA2015PTC078261

On 31-May-2017, at 6:26 PM, Juri Boxberger notifications@github.com wrote:

Hello tskamath,

have you upgraded the RAM of your NAS? It looks like HGitlab is running out of RAM. You nead at least 2GB (better 4GB) to run Gitlab properly.

Here is a short Tutorial: https://www.youtube.com/watch?v=HeRbuYwqx-M https://www.youtube.com/watch?v=HeRbuYwqx-M Please let me know if you have already upgraded your RAM but the Error remains.

Kind Regards

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jboxberger/synology-gitlab/issues/15#issuecomment-305177952, or mute the thread https://github.com/notifications/unsubscribe-auth/ADVLn23_5t12K8nq9sxORk1fvfBshgEXks5r_WNlgaJpZM4NrM_M.

[jboxberger]

You're welcome.

Please note that not every RAM is compatible. The Clock Speed Should match and if possible the timings sould be also same or faster. As far as i can rememeber there was also a issue with Single vs. Dual Rank.

Anyways if the RAM is completely incompatible the system don't boot up. The second case is that the system boots but is much slower than before the upgrade, i had this problem with the 712+.

Kind Regards

[tskamath]

Thanks for the upstart I have 2GB x 2 Nos of Samsung, 2GB 2RX8 PC3-10600S-09-10-F2, look like is quite a task to open up the box, I hope it works out, else I will buy the Corsair CM3X2GSD1066 2GB DDR3 SODIMM.

I also have DS712+, ..thanks again.

Thanks & Regards

Srikanth Kamath,

On 31-May-2017, at 10:53 PM, Juri Boxberger notifications@github.com wrote:

You're welcome.

Please note that not every RAM is compatible. The Clock Speed Should match and if possible the timings sould be also same or faster. As far as i can rememeber there was also a issue with Single vs. Dual Rank.

Anyways if the RAM is completely incompatible the system don't boot up. The second case is that the system boots but is much slower than before the upgrade, i had this problem with the 712+.

Kind Regards

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jboxberger/synology-gitlab/issues/15#issuecomment-305257612, or mute the thread https://github.com/notifications/unsubscribe-auth/ADVLn763pAMmVNhuoNLW6jAOqoSQOO1mks5r_aIFgaJpZM4NrM_M.

[LF-DevJourney]

Check the shared memory, 502 Gitlab is taking too much time to respond