Gitlab fails to install following Guide

0 replies
VirtuallyCreative
2 posts

Hello!

Recently picked up an 8GB Antsle Nano. The setup has been straightforward but no matter which OS I pick I can't get GitLab installed on a fresh antlet using the directions provided by the Antsle Docs or GitLab's official docs.

I've tried with Ubuntu20, CentOS 7, RasbianOS, and all of them fail to install GitLab with various errors each time at the EXTERNAL_URL step. This output is at that same step from following the RasbianOS guide from GitLab

Does anyone else have issues following along with the provided guides or have an updated resource?

```log
Running handlers:
There was an error running gitlab-ctl reconfigure:

Multiple failures occurred:
* Mixlib::ShellOut::ShellCommandFailed occurred in Chef Infra Client run: gitlab_sysctl[kernel.shmall] (postgresql::enable line 61) had an error: Mixlib::ShellOut::ShellCommandFailed: execute[load sysctl conf kernel.shmall] (/opt/gitlab/embedded/cookbooks/cache/cookbooks/package/resources/gitlab_sysctl.rb line 48) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '255'
---- Begin output of sysctl -e -p /opt/gitlab/embedded/etc/90-omnibus-gitlab-kernel.shmall.conf ----
STDOUT:
STDERR: sysctl: setting key "kernel.shmall": Read-only file system
---- End output of sysctl -e -p /opt/gitlab/embedded/etc/90-omnibus-gitlab-kernel.shmall.conf ----
Ran sysctl -e -p /opt/gitlab/embedded/etc/90-omnibus-gitlab-kernel.shmall.conf returned 255
* Mixlib::ShellOut::ShellCommandFailed occurred in delayed notification: execute[reload all sysctl conf] (package::sysctl line 18) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '255'
---- Begin output of sysctl -e --system ----
STDOUT: * Applying /etc/sysctl.d/90-omnibus-gitlab-kernel.shmall.conf ...
* Applying /etc/sysctl.d/90-omnibus-gitlab-kernel.shmmax.conf ...
* Applying /etc/sysctl.d/98-rpi.conf ...
* Applying /etc/sysctl.d/99-sysctl.conf ...
* Applying /etc/sysctl.d/protect-links.conf ...
* Applying /etc/sysctl.conf ...
STDERR: sysctl: setting key "kernel.shmall": Read-only file system
sysctl: setting key "kernel.shmmax": Read-only file system
sysctl: setting key "kernel.printk": Read-only file system
sysctl: setting key "vm.min_free_kbytes": Read-only file system
sysctl: setting key "fs.protected_hardlinks": Read-only file system
sysctl: setting key "fs.protected_symlinks": Read-only file system
---- End output of sysctl -e --system ----
Ran sysctl -e --system returned 255

Notes:
It seems you haven't specified an initial root password while configuring the GitLab instance.
On your first visit to your GitLab instance, you will be presented with a screen to set a
password for the default admin account with username `root`.

Running handlers complete
Chef Infra Client failed. 6 resources updated in 43 seconds

Notes:
It seems you haven't specified an initial root password while configuring the GitLab instance.
On your first visit to your GitLab instance, you will be presented with a screen to set a
password for the default admin account with username `root`.

dpkg: error processing package gitlab-ce (--configure):
installed gitlab-ce package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
gitlab-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@raspberrypi:~#

Any insight would be appreciated, I'm a front-end developer still learning more on the server/networking side so this is still a bit new to me.

Log in to reply. New here? It takes a minute.