Synology GitLab error 502
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg1y3_5RIon9p2QE9KPBbHXy8CSN0vhnz86kL4UjqB4udokVTtHKFKn7ZHAp248ympdgi69_xOR48mgnUkcYuzi4DZuuM8xReI9hHLe4D_Dizd_nScMoetxXYTVZp8ljhcBisDq2s45vHU/s1600/Gitlab+502+error.jpg)
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) ...