Installing GitLab HA on Amazon Web Services (AWS)

How to Use GitLab
1

Installing GitLab HA on Amazon Web Services (AWS)

I have set up self-managed gitlab app server form the official AMI GitLab EE 12.9.2. I have performed all the needed configuration. All the services are up and running fine. But when we attach the app server with AWS application load balancer, the port 80 showing Health checks failed with these codes: [302] and the port 443 is showing Health checks failed with these codes: [502]. Unable to find any error on the Nginx log. :

  • Gitlab app server attached to Load balancer and it is not passing the helthcheck, even the LB DNS is not giving the gitlab initial page*

Helth check log from Nginx access log:

172.40.1.221 - - [07/May/2020:14:32:00 +0000] “GET /users/sign_in HTTP/1.1” 302 148 “” “ELB-HealthChecker/2.0”
172.40.2.175 - - [07/May/2020:14:32:00 +0000] “GET /users/sign_in HTTP/1.1” 302 148 “” “ELB-HealthChecker/2.0”
172.40.1.221 - - [07/May/2020:14:32:30 +0000] “GET /users/sign_in HTTP/1.1” 302 148 “” “ELB-HealthChecker/2.0”
172.40.2.175 - - [07/May/2020:14:32:30 +0000] “GET /users/sign_in HTTP/1.1” 302 148 “” “ELB-HealthChecker/2.0”

====

All service Status:

====
Checking GitLab subtasks …

Checking GitLab Shell …

GitLab Shell: … GitLab Shell version >= 12.0.0 ? … OK (12.0.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful

Checking GitLab Shell … Finished

Checking Gitaly …

Gitaly: … default … OK

Checking Gitaly … Finished

Checking Sidekiq …

Sidekiq: … Running? … yes
Number of Sidekiq processes … 1

Checking Sidekiq … Finished

Checking Incoming Email …

Incoming Email: … Reply by email is disabled in config/gitlab.yml

Checking Incoming Email … Finished

Checking LDAP …

LDAP: … LDAP is disabled in config/gitlab.yml

Checking LDAP … Finished

Checking GitLab App …

Git configured correctly? … yes
Database config exists? … yes
All migrations up? … yes
Database contains orphaned GroupMembers? … no
GitLab config exists? … yes
GitLab config up to date? … yes
Log directory writable? … yes
Tmp directory writable? … yes
Uploads directory exists? … yes
Uploads directory has correct permissions? … yes
Uploads directory tmp has correct permissions? … skipped (no tmp uploads folder yet)
Init script exists? … skipped (omnibus-gitlab has no init script)
Init script up-to-date? … skipped (omnibus-gitlab has no init script)
Projects have namespace: … can’t check, you have no projects
Redis version >= 2.8.0? … yes
Ruby version >= 2.5.3 ? … yes (2.6.5)
Git version >= 2.22.0 ? … yes (2.24.1)
Git user has default SSH configuration? … yes
Active users: … 1
Is authorized keys file accessible? … yes
Elasticsearch version 5.6 - 6.x? … skipped (elasticsearch is disabled)

Checking GitLab App … Finished

Checking GitLab subtasks … Finished

root@gitlabapp:XXX# gitlab-ctl status
run: alertmanager: (pid 12375) 8085s; run: log: (pid 1303) 10937s
run: gitaly: (pid 1312) 10937s; run: log: (pid 1305) 10937s
run: gitlab-exporter: (pid 7010) 8579s; run: log: (pid 1307) 10937s
run: gitlab-workhorse: (pid 6991) 8579s; run: log: (pid 1321) 10937s
run: grafana: (pid 1316) 10937s; run: log: (pid 1308) 10937s
run: logrotate: (pid 27868) 137s; run: log: (pid 1319) 10937s
run: nginx: (pid 1314) 10937s; run: log: (pid 1306) 10937s
run: node-exporter: (pid 1304) 10937s; run: log: (pid 1302) 10937s
run: prometheus: (pid 1320) 10937s; run: log: (pid 1318) 10937s
run: sidekiq: (pid 6985) 8579s; run: log: (pid 1309) 10937s
run: unicorn: (pid 7596) 8540s; run: log: (pid 1310) 10937s

====

Thanks for taking the time to be thorough in your request, it really helps! :blush: