Gitlab 502 ошибка whoops gitlab is taking too much time to respond

I installed Gitlab on Raspberry Pi2, and it had worked well for a couple of months. But since shutting down the power of RPi, it doesn’t work anymore. The webpage returns 502 error.

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

So I tried reconfigure (sudo gitlab-ctl reconfigure) but, it failed with the error message:

FATAL: Errono::EAFNOSUPPORT: Address family not supported by protocol - socket(2)

I don’t know how to resolve this problem.

edwardmlyte

15.7k23 gold badges58 silver badges82 bronze badges

asked Oct 21, 2015 at 8:11

I saw issue like this several times.

If GitLab has been worked fine please do not touch anything. Just wait. It seems GitLab has not been started properly

I mean that after booting system you have to wait 1-2 minutes before using GitLab. GitLab needs some time for starting.

answered Oct 12, 2016 at 7:06

VladVlad

3,4651 gold badge30 silver badges24 bronze badges

I am not adding a comment since my answer needs some good formatting.

So that means, your port 8080 is already being used. I would advise to stop GitLab, and change unicorn port from 8080 to 8081 (or some unused port).

After starting/restarting GitLab wait for 2 minutes, and you should be okay. If not, again check gitlab-ctl tail for any errors.

# gitlab-ctl stop

# vi /etc/gitlab/gitlab.rb   (change only these lines, uncomment if required)
unicorn['port'] = 8081
gitlab_git_http_server['auth_backend'] = "http://localhost:8081"

# gitlab-ctl reconfigure  (to apply the changes)
# gitlab-ctl restart
# lsof -i:8081        (check whether unicorn has started properly)

You need to be root or a sudo user (with root privileges) to run these commands.

answered Nov 29, 2015 at 10:38

vikas027vikas027

5,1824 gold badges39 silver badges51 bronze badges

After inspecting the gitlab-ctl tail (reboot loop) it turned out that there is not enough RAM (2GB) and there is no swap file in my fresh Ubuntu setup.

As mentioned in requirements GitLab requires at least 2GB RAM + 2GB swap memory …

So to create a swap file follow those steps:

gitlab-ctl stop
mkdir /swap && touch /swap/swapfile.img
dd if=/dev/zero of=/swap/swapfile.img bs=1024 count=2M # if you want 4G change 2M to 4M
chmod 0600 /swap/swapfile.img
mkswap /swap/swapfile.img
nano /etc/fstab and add «/swap/swapfile.img swap swap sw 0 0»
swapon /swap/swapfile.img

Verify if it works : cat /proc/swaps

Filename                Type        Size    Used    Priority

/swap/swapfile.img      file        2097148 0       -1

gitlab-ctl start

more info about creating swap : here

answered Feb 28, 2018 at 10:58

trojantrojan

1,45519 silver badges27 bronze badges

You can follow below steps to fix this kind of issue.

Update unicorn['port'] to ****.(Different port which is not used for process in the system)
Update nginx['port'] to ****.(Different port which is not used for process in the system)
Update web_server username and web_server group in this file as well and set it to apache’s/httpd’s username and group

Then do gitlab-ctl reconfigure and gitlab-ctl restart

Cà phê đen

1,8652 gold badges21 silver badges20 bronze badges

answered Oct 12, 2016 at 7:16

himeshc_IBhimeshc_IB

8434 silver badges10 bronze badges

You should change your Unicorn Settings
If you need to adjust the Unicorn timeout or the number of workers you can use the following settings in /etc/gitlab/gitlab.rb.
Change the following:

unicorn['worker_processes'] = 3
unicorn['worker_timeout'] = 120 # or any suitable timeout for your server

do not forget to remove # in line start if commented.
Run sudo gitlab-ctl reconfigure for the change to take effect.

answered Jul 29, 2018 at 10:04

Anas NaguibAnas Naguib

99610 silver badges12 bronze badges

This error is also occurred when the system, in your case the Raspberry Pi2 (in my case, in an t2.micro AWS EC2 instance) due to not fulfilling the minimum requirements for installing Gitlab.

That is the lack of Memory (t2.micro is 1GiB, but Gitlab requires 4GiB) for further processing. Therefore, provide all the requirements correctly (I occupied a t2.medium instance which is 4GiB instead of t2.micro).
It would be appropriate if the system has been enabled accurately.

answered Nov 9, 2017 at 5:00

Need to set nginx[‘listen_port’] and unicorn[‘port’].
For example:

nginx['listen_port'] = 8081
unicorn['port'] = 8082 #the ports should be different

Then:

sudo gitlab-ctl reconfigure
sudo gitlab-ctl restart

answered Dec 4, 2017 at 12:22

There was a port collision at my site. Jenkins has already run on my site, which uses the 8080 port also.

Change Gitlab or Jenkins port.

answered Mar 19, 2020 at 10:55

betontalpfabetontalpfa

3,4041 gold badge33 silver badges65 bronze badges

Something is listening to the 8080 port, so Unicorn can’t start.
What does the following command indicate?
The ports for Redis, PostgreSQL and Puma can be overridden in

/etc/gitlab/gitlab.rb

as follows:

    redis['port'] = 1234
    postgresql['port'] = 2345
    puma['port'] = 3456

For NGINX port changes please see settings/nginx.md.

see https://docs.gitlab.com/omnibus/common_installation_problems/#tcp-ports-for-gitlab-services-are-already-taken
(TCP ports for GitLab services are already taken)

answered May 16, 2020 at 9:23

ismaelismael

4341 gold badge4 silver badges11 bronze badges

Please note if you got 502 Whoops, GitLab is taking too much time to respond
before going so much with every step

Ensure that your server has at least 4GB of RAM
and give her server at least 10 minutes if you are using digital ocean droplet

answered Nov 22, 2021 at 12:44

I had that kind of error before and turns out that I had not physicall space (in my case, a virtual machine). Check that you have enough space

answered Apr 30, 2022 at 13:45

JoseJose

175 bronze badges

It is posyble that you has change change some configuration file, use this lines in your terminal:

sudo gitlab-ctl reconfigure
sudo gitlab-ctl restart

Now wait a few minutes, and try again.

answered Jul 13, 2018 at 16:34

You should only change external_url http://xxx.xxx.xxx.xx:9090. Don’t change # unicorn['port'] = 8080.

Cà phê đen

1,8652 gold badges21 silver badges20 bronze badges

answered Jun 17, 2019 at 2:45

Источник

GitLab Forum

Источник

Solution 1

I saw issue like this several times.

If GitLab has been worked fine please do not touch anything. Just wait. It seems GitLab has not been started properly

I mean that after booting system you have to wait 1-2 minutes before using GitLab. GitLab needs some time for starting.

Solution 2

I am not adding a comment since my answer needs some good formatting.

So that means, your port 8080 is already being used. I would advise to stop GitLab, and change unicorn port from 8080 to 8081 (or some unused port).

After starting/restarting GitLab wait for 2 minutes, and you should be okay. If not, again check gitlab-ctl tail for any errors.

# gitlab-ctl stop

# vi /etc/gitlab/gitlab.rb   (change only these lines, uncomment if required)
unicorn['port'] = 8081
gitlab_git_http_server['auth_backend'] = "http://localhost:8081"

# gitlab-ctl reconfigure  (to apply the changes)
# gitlab-ctl restart
# lsof -i:8081        (check whether unicorn has started properly)

You need to be root or a sudo user (with root privileges) to run these commands.

Solution 3

After inspecting the gitlab-ctl tail (reboot loop) it turned out that there is not enough RAM (2GB) and there is no swap file in my fresh Ubuntu setup.

As mentioned in requirements GitLab requires at least 2GB RAM + 2GB swap memory …

So to create a swap file follow those steps:

gitlab-ctl stop
mkdir /swap && touch /swap/swapfile.img
dd if=/dev/zero of=/swap/swapfile.img bs=1024 count=2M # if you want 4G change 2M to 4M
chmod 0600 /swap/swapfile.img
mkswap /swap/swapfile.img
nano /etc/fstab and add «/swap/swapfile.img swap swap sw 0 0»
swapon /swap/swapfile.img

Verify if it works : cat /proc/swaps

Filename                Type        Size    Used    Priority

/swap/swapfile.img      file        2097148 0       -1

gitlab-ctl start

more info about creating swap : here

Solution 4

You can follow below steps to fix this kind of issue.

Update unicorn['port'] to ****.(Different port which is not used for process in the system)
Update nginx['port'] to ****.(Different port which is not used for process in the system)
Update web_server username and web_server group in this file as well and set it to apache’s/httpd’s username and group

Then do gitlab-ctl reconfigure and gitlab-ctl restart

Solution 5

You should change your Unicorn Settings
If you need to adjust the Unicorn timeout or the number of workers you can use the following settings in /etc/gitlab/gitlab.rb.
Change the following:

unicorn['worker_processes'] = 3
unicorn['worker_timeout'] = 120 # or any suitable timeout for your server

do not forget to remove # in line start if commented.
Run sudo gitlab-ctl reconfigure for the change to take effect.

Comments

I installed Gitlab on Raspberry Pi2, and it had worked well for a couple of months. But since shutting down the power of RPi, it doesn’t work anymore. The webpage returns 502 error.

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

So I tried reconfigure (sudo gitlab-ctl reconfigure) but, it failed with the error message:
```
FATAL: Errono::EAFNOSUPPORT: Address family not supported by protocol - socket(2)
```
I don’t know how to resolve this problem.
I changed port number 8080 to 8081 and added a line gitlab_git_http_server['auth_backend'] = "http://localhost:8081" in a gitlab.rb file because it isn’t there. But, it still gives same error message. FATAL -- : error adding listener addr=127.0.0.1:8080
The line would definitely be there but with port 8080, you would have to uncomment that and change it to port 8081.
I tried reconfigure again. There is another error log in /var/log/gitlab/postgresql/current LOG: received fast shutdown request LOG: database system is shut down LOG: could not bind socket for statistics collector: Cannot assign requested address LOG: trying another address for the statistics collector LOG: could not create socket for statistics collector: Address family not supported by protocol LOG: disabling statistics collector for lack of working socket WARNING: autovacuum not started because of misconfiguration HINT: Enable the "track_counts" option.
What does gitlab-ctl status shows ? Are all processes up ? You might have to troubleshoot postgres. Try lsof -i:5432 or sudo -u postgres psql template1
All processes are running (logrotate, nginx, postgresql, redis, sidekiq, unicorn). Maybe port 5432 is unused. sudo lsof -i:5432 doesn’t return any message.
@SeoHwaEunHa Then you have issues with your postgresql database. It shouldn’t be ideally, I have installed and configured the latest version of GitLab on CentOS 6.7 recently. Try checking PostgreSQL logs and stop/start it manually.
Waiting wasn’t helping me, adding more memory did.
@9swampy, how you add more memory?
I was seeing this issue running GitLab on a Ubuntu VM; allocating a bit more memory helped; from memory I upped from 1 to 2 GB.
How is this any different than 3438276? Also, it is always a good idea to point out files which need to be changed too.
I meet the 502 error, and I change the virtual box memory from 1GB to 2GB, and the error gone.
@vikas027 In my CentOS 6 GitLab there is no gitlab_git_http_server['auth_backend'] tag. I tried with the port, but not working yet. I have no other services running except ssh on 22.
Well, I killed one night and one evening trying to understand what went wrong in my case, I tried different port as It described above and finally I just had extended RAM to 8gb, because I use ubuntu under wmware and 502 is gone. I read ofdoc some time before It, but I thought, that gitlab could run even with less RAM. That behaviour is a bit strange for me

Recents

Источник

Recently, there are servers on the cloud that need to be released, and then the gitlab running on the cloud has to move somewhere. Because of limited resources, it borrows to build an environment on other servers (available memory is less than 4,000), but when the goose starts up, it inexplicably appears 502, Excuse me? Then I searched for some solutions on issue blogs (such as modifying ports, restarting or hup A service) and found some information in the log during the adjustment process.

The main idea of this trip is the train of thought. When you open your horizon, you will feel open-minded. It turns out that this is actually a minor problem.

1. It is not clear what the services and uses of the application will be started. Only status will be viewed simply.

2. Baidu is the first thing that comes to mind when you see a mistake. Wouldn’t it be good to look for a log path and read the log first?

3. Unaware of the relationship between services (e.g. postgresql and unicorn), I always knew that Unicorn did not listen to ports properly after booting, but there was no special information in the log (well, maybe because I read the wrong file)[Smile bitterly]

I. false information

Two. Troubleshooting process

1. Start unicorn without listening to port.

Log path: /var/log/gitlab/unicorn/unicorn_stderr.log

PG::ConnectionBad: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"?

  /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/postgresql_adapter.rb:651:in `initialize'
  /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/postgresql_adapter.rb:651:in `new'
  /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/postgresql_adapter.rb:651:in `connect'
  /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/postgresql_adapter.rb:242:in `initialize'
  /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/postgresql_adapter.rb:44:in `new'
  /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/activerecord-4.2.10/lib/active_record/connection_adapters/postgresql_adapter.rb:44:in `postgresql_connection'

··· ···
··· ···

The message is displayed because you can’t connect to the PG, so it’s normal to restart after starting postgresql (well, that’s it).

2,postgresql down

down: postgresql: 0s, normally up, want up; run: log: (pid 623) 15816094s

Through PG’s log path: /var/log/gitlab/postgresql/current, you can see the following information

2018-11-01_08:18:09.49669 FATAL:  could not map anonymous shared memory: Cannot allocate memory
2018-11-01_08:18:09.49671 HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 4292984832 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
2018-11-01_08:18:09.49671 LOG:  database system is shut down

You can also get the same information by commanding `gitlab-ctl tail postgresql’, so you can determine the problem.

This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 4292984832 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
2018-11-01_07:52:06.63024 LOG:  database system is shut down

In the configuration file, the shared_buffers and max_connections of postgresql are restricted.

[root@V2 ~]# cat /etc/gitlab/gitlab.rb |grep -v ^$ |grep -v ^#
external_url 'http://xxx.xxx.xxx.xxx.xxx:8090'
unicorn['worker_timeout'] = 60
unicorn['worker_processes'] = 3
unicorn['listen'] = 'xxx.xxx.xxx.xxx.xxx'
unicorn['port'] = 8870
postgresql['enable'] = true
postgresql['data_dir'] = "/var/opt/gitlab/postgresql/data"
postgresql['shared_buffers'] = "256MB"   # ! **recommend value is 1/4 of total RAM, up to 14GB.**      
postgresql['max_connections'] = 200
nginx['listen_addresses'] = ['*']
nginx['listen_port'] = 8090

The configuration is completed and saved, then the configuration is updated, and the application is restarted.

gitlab-ctl reconfigure   # Update configuration
gitlab-ctl restart       # restart app
gitlab-ctl status        # View service status

Reference material:

1. 502-Whoops, GitLab is taking too much time to respond

2. Postgresql down

3. HTTP 502: Whoops, GitLab is taking too much time to respond. Even after Server restart

Posted by myblue
in Operation & Maintenance
at Nov 04, 2018 — 7:08 PM

Источник

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

Источник

Solution 1

Solution 2

Solution 3

Solution 4

Solution 5

Comments

Recents

Related

I. false information

Two. Troubleshooting process

1. Start unicorn without listening to port.

2,postgresql down

Возможно, вам также будет интересно: