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

How to Use GitLab Self-managed
,
1

:hugs: Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

Gitlab not Starting Error 502 Whoops, GitLab is taking too much time to respond.:

I have ran the

sudo gitlab-ctl status

run: alertmanager: (pid 1587) 83s; run: log: (pid 1582) 83s
run: gitaly: (pid 1580) 83s; run: log: (pid 1575) 83s
run: gitlab-exporter: (pid 1576) 83s; run: log: (pid 1573) 83s
run: gitlab-workhorse: (pid 1591) 83s; run: log: (pid 1579) 83s
run: grafana: (pid 1586) 83s; run: log: (pid 1572) 83s
run: logrotate: (pid 1567) 83s; run: log: (pid 1565) 83s
run: nginx: (pid 1588) 83s; run: log: (pid 1584) 83s
run: node-exporter: (pid 1569) 83s; run: log: (pid 1568) 83s
run: postgres-exporter: (pid 1585) 83s; run: log: (pid 1571) 83s
run: postgresql: (pid 1561) 83s; run: log: (pid 1559) 83s
run: prometheus: (pid 1560) 83s; run: log: (pid 1557) 83s
run: puma: (pid 12394) 0s; run: log: (pid 1574) 83s
run: redis: (pid 1583) 83s; run: log: (pid 1577) 83s
run: redis-exporter: (pid 1563) 83s; run: log: (pid 1558) 83s
run: sidekiq: (pid 12015) 2s; run: log: (pid 1578) 83s

All the services are up and running still unable to get the login screen

sudo gitlab-ctl reconfigure

Even after successful Recofiguration, I’m not getting the login page

Can any one help - Please

2

Hi All

The issue is resolved So let me document down the Troubleshooting steps that worked for me

sudo gitlab-ctl status
gitlab-ctl stop
systemctl stop gitlab-runsvdir
ps aux | grep “git”

gitlab-ctl status

now all the services will be stopped

sudo gitlab-ctl reconfigure
gitlab-ctl status

If not started

Run

gitlab-ctl start

if not started again Reboot the Server and wait for 5 min the app will be up and running

3

Next time you might be able to just run gitlab-ctl restart which restarts all the running services.