Gitlab docker commands

 sudo docker exec -it <container_id> bash

Check for all GitLab services running in gitlab

gitlab-ctl status 

To stop any GitLab services

gitlab-ctl stop prometheus

To start any GitLab services

gitlab-ctl startprometheus

When Sidekiq Is Stopped:

• Email Notifications Won't Be Sent: Since Sidekiq is responsible for handling background tasks like email delivery, if you stop Sidekiq, the forgot password email won't be sent to the user.
  • The request for a password reset will still be processed, but the system will not be able to send the email due to Sidekiq being down.
• Other Email-Related Features: Any other features that rely on email notifications (like user invitations, confirmation emails, or CI/CD notifications) will also be affected.

To check whether GitLab is enforcing authentication (which could be affecting the ELB health check), run the following inside the GitLab Rails console (command: gitlab-rails console):

ApplicationSetting.first.password_authentication_enabled_for_web

or

ApplicationSetting.first.password_authentication_enabled_for_git



If signin_enabled is false, you can either:
ApplicationSetting.first.update!(signin_enabled: true)
If it returns false, it means authentication is required for all requests, and ELB’s health check to / will fail because it gets redirected to /users/sign_in.
If it returns true, GitLab allows unauthenticated users to access the site, meaning ELB should be able to perform health checks properly.