Synology GitLab error 502

How to fix the GitLab 502 error

Occasionally when starting GitLab, I get a 502 error ("Whoops, GitLab is taking too much time to respond").  It appears to happen when my Synology NAS has restarted after a power outage.

Checking the Docker GitLab log, I can seen continual messages about trying to restart the "unicorn" process.  This also causes high CPU usage.
2017-03-27 00:35:08,892 INFO spawned: 'unicorn' with pid 27723
2017-03-27 00:35:09,896 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-27 00:35:14,277 INFO exited: unicorn (exit status 1; not expected)
...

To fix the problem, create a terminal window within the Docker application.  Or login to the GitLab console from the root console of your NAS.
# docker exec -it synology_gitlab bash
Then delete the PID file for unicorn.  This will be a stale PID value that doesn't exist any more.
root@synology_gitlab:/home/git/gitlab# rm /home/git/gitlab/tmp/pids/unicorn.pid
The unicorn process should now start properly, and after a minute or two you should be able to login to GitLab.  If necessary, check the log for any additional diagnostics:
root@synology_gitlab:/home/git/gitlab# tail -f /var/log/gitlab/gitlab/unicorn.stderr.log
I, [2017-03-27T11:18:45.310166 #12729] INFO -- : reaped #<Process::Status: pid 12759 exit 0> worker=2
I, [2017-03-27T11:18:45.310584 #12729] INFO -- : master complete
I, [2017-03-27T11:18:58.143931 #12771] INFO -- : Refreshing Gem list
I, [2017-03-27T11:24:51.374610 #436] INFO -- : Refreshing Gem list
I, [2017-03-27T11:27:03.707925 #436] INFO -- : listening on addr=/home/git/gitlab/tmp/sockets/gitlab.socket fd=14
I, [2017-03-27T11:27:03.710037 #436] INFO -- : listening on addr=127.0.0.1:8080 fd=15
I, [2017-03-27T11:27:03.741193 #486] INFO -- : worker=0 ready
I, [2017-03-27T11:27:03.772663 #489] INFO -- : worker=1 ready
I, [2017-03-27T11:27:03.795237 #436] INFO -- : master process ready
I, [2017-03-27T11:27:03.801966 #492] INFO -- : worker=2 ready
If the process is still not running, restart the GitLab package.

TIP: Check out my instructions for Backup and Restore for GitLab.

Comments

清影 said…
I face the issue just now and try many way to fix the issue, but it still happen.
Thanks for the post. I follow the instructions and then gitlab back to normal now.
You save my code/data in the gitlab. Thank you.
31 October 2017 at 01:59
Unknown said…
Thank you. Saved we a bunch of time. Thumbs up.
27 March 2018 at 07:20
Post a Comment

Popular posts from this blog

Resolving FOSCAM connection dropouts

Image
I bought a FOSCAM FI8908W wireless IP webcam off eBay recently. It has lots of features for the price. However, I've had problems with being unable to connect to the camera after a period of time (an hour or so). Power cycling the camera would fix the problem. I've tried upgrading to the latest firmware (version 11.14.2.17 is supposed to fix WiFi disconnection problems), but it did not fix my problem. Problem analysis The problem is not related to my browser or the wireless network. I've tried disabling DHCP (router based static IP). It turns out the problem is that the webcam simply ceases to respond to ARP  (Address Resolution Protocol) requests (once in this broken state). ARP is a mechanism to translate between IP addresses and device MAC addresses. It underpins all IP communications over both Ethernet and WiFi, since at the lowest level it relies on exchange of packets between device MAC addresses. The ARP protocol allows a network device to discover t...
Read more

Building an automatic chicken door opener

Image
We recently got chickens and found them to be noisy in the morning because they wanted to be let out of their coop.  Of course, we just wanted to sleep in.  What we needed was an automatic door opener. Here's our 3 hens (Edna, Dora and the bantam Dotty).  Click for more photos. Here's the chicken coop, with the addition of an automatic door opener.  The chicken coop was purchased from Pets Station . There are some (expensive) automatic chicken doors that are available for purchase, but I decided to design and make my own.  You are welcome to copy or adapt the design to suit your own requirements.
Read more

TVersity media serving to the Astone AP-300

Image
TVersity is a digital media server that can share media over your home network using UPnP/DNLA. This is kind-of like Windows file sharing/SMB, except that a digital media server can be a lot smarter.  You get access to traditional media such as picture, audio or movie files, like you would through network file sharing.  TVersity though can take things further, supporting: On-the-fly transcoding of media into a format suitable for your media player, Downloading content from the Internet, Streaming media as it is being downloaded or transcoded, Tagging of media to present a smarter content view instead of just a traditional directory structure, Improved network performance compared with normal network file sharing.  I'm able to stream 1080p video rather than having to copy it to the internal HDD My media player is a Astone AP-300 and is similar to many others in that it has network connectivity, HD video support, and of-course acts as a UPnP Media Player/Render...
Read more