GitLab not there after play runs :-(
rsysadmin-com opened this issue · comments
Hi there!
This is a new Ubuntu 20.04 LTS virtual machine.
I use our own SSL certificates which are proven to work in other internal sites.
Unfortunately the role does not work and GitLab is not even starting:
This is the output of the play:
---] START OF PASTED TEXT
$ ansible-playbook -i inventory install_gitlab.yml
PLAY [gitlab] ****************************************************************************************************************************************************
TASK [Gathering Facts] *******************************************************************************************************************************************
ok: [gitlab01]
TASK [gitlab-install : Include OS-specific variables.] ***********************************************************************************************************
ok: [gitlab01]
TASK [gitlab-install : Check if GitLab configuration file already exists.] ***************************************************************************************
ok: [gitlab01]
TASK [gitlab-install : Check if GitLab is already installed.] ****************************************************************************************************
ok: [gitlab01]
TASK [gitlab-install : Install GitLab dependencies.] *************************************************************************************************************
ok: [gitlab01]
TASK [gitlab-install : Install GitLab dependencies (Debian).] ****************************************************************************************************
changed: [gitlab01]
TASK [gitlab-install : Download GitLab repository installation script.] ******************************************************************************************
changed: [gitlab01]
TASK [gitlab-install : Install GitLab repository.] ***************************************************************************************************************
changed: [gitlab01]
TASK [gitlab-install : Define the Gitlab package name.] **********************************************************************************************************
skipping: [gitlab01]
TASK [gitlab-install : Install GitLab] ***************************************************************************************************************************
changed: [gitlab01]
TASK [gitlab-install : Reconfigure GitLab (first run).] **********************************************************************************************************
changed: [gitlab01]
TASK [gitlab-install : Create GitLab SSL configuration folder.] **************************************************************************************************
[DEPRECATION WARNING]: evaluating 'gitlab_create_self_signed_cert' as a bare variable, this behaviour will go away and you might need to add |bool to the
expression in the future. Also see CONDITIONAL_BARE_VARS configuration toggle. This feature will be removed in version 2.12. Deprecation warnings can be disabled
by setting deprecation_warnings=False in ansible.cfg.
skipping: [gitlab01]
TASK [gitlab-install : Create self-signed certificate.] **********************************************************************************************************
[DEPRECATION WARNING]: evaluating 'gitlab_create_self_signed_cert' as a bare variable, this behaviour will go away and you might need to add |bool to the
expression in the future. Also see CONDITIONAL_BARE_VARS configuration toggle. This feature will be removed in version 2.12. Deprecation warnings can be disabled
by setting deprecation_warnings=False in ansible.cfg.
skipping: [gitlab01]
TASK [gitlab-install : Copy GitLab configuration file.] **********************************************************************************************************
changed: [gitlab01]
RUNNING HANDLER [gitlab-install : restart gitlab] ****************************************************************************************************************
changed: [gitlab01]
PLAY RECAP *******************************************************************************************************************************************************
gitlab01 : ok=12 changed=7 unreachable=0 failed=0 skipped=3 rescued=0 ignored=0
---] END OF PASTED TEXT
root@gitlab01:/opt/gitlab/bin# ./gitlab-ctl status
root@gitlab01:/opt/gitlab/bin#
root@vgitlab01:/opt/gitlab/bin# netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:44322 0.0.0.0:* LISTEN 0 42691 3234/pmproxy
tcp 0 0 0.0.0.0:44323 0.0.0.0:* LISTEN 0 42693 3234/pmproxy
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 101 28292 1050/systemd-resolv
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 68074 10088/sshd: /usr/sb
tcp6 0 0 :::44322 :::* LISTEN 0 42692 3234/pmproxy
tcp6 0 0 :::44323 :::* LISTEN 0 42694 3234/pmproxy
tcp6 0 0 :::22 :::* LISTEN 0 68085 10088/sshd: /usr/sb
udp 0 0 127.0.0.1:323 0.0.0.0:* 0 59747 9181/chronyd
udp 0 0 127.0.0.53:53 0.0.0.0:* 101 28291 1050/systemd-resolv
udp6 0 0 ::1:323 :::* 0 59748 9181/chronyd
root@vgitlab01:/opt/gitlab/bin#
Am I overseeing the obvious? O_o
Thanks in advance!
Best
How are your specs for the VM?
I had similar results when I installed GitLab on a VM that was under spect.
If I remember correctly, GitLab recommends 4CPU and 8GB RAM.
Running "sudo gitlab-ctl status" from terminal should return:
$ sudo gitlab-ctl status
run: alertmanager: (pid 14466) 90s; run: log: (pid 13983) 177s
run: gitaly: (pid 14369) 92s; run: log: (pid 13379) 289s
run: gitlab-exporter: (pid 14351) 92s; run: log: (pid 13842) 197s
run: gitlab-workhorse: (pid 14322) 93s; run: log: (pid 13722) 220s
run: grafana: (pid 15121) 34s; run: log: (pid 14262) 114s
run: logrotate: (pid 13759) 210s; run: log: (pid 13771) 207s
run: nginx: (pid 15112) 35s; run: log: (pid 13750) 213s
run: node-exporter: (pid 14333) 93s; run: log: (pid 13823) 201s
run: postgres-exporter: (pid 14478) 90s; run: log: (pid 14108) 173s
run: postgresql: (pid 13443) 286s; run: log: (pid 13460) 283s
run: prometheus: (pid 14362) 92s; run: log: (pid 13884) 183s
run: puma: (pid 15082) 48s; run: log: (pid 13651) 233s
run: redis: (pid 13240) 298s; run: log: (pid 13257) 295s
run: redis-exporter: (pid 14353) 92s; run: log: (pid 13861) 191s
run: sidekiq: (pid 15056) 56s; run: log: (pid 13673) 225
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.