Hallo zusammen,
ich habe GitLab so installiert wie es in dieser Datei steht: linux-guides/gitlab at main · Jean28518/linux-guides · GitHub
Nun habe ich die originelle GitLab docker-compose Datei angepasst und daraus ein AddOn gemacht. Nach der Installation schaue ich in die Logs und lese:
root@la:~/gitlab# docker-compose logs -f
Attaching to gitlab_gitlab_1, gitlab_redis_1, gitlab_postgresql_1
gitlab_gitlab_1 exited with code 128
postgresql_1 | Initializing datadir...
postgresql_1 | Initializing certdir...
postgresql_1 | Initializing logdir...
postgresql_1 | Initializing rundir...
postgresql_1 | Setting resolv.conf ACLs...
postgresql_1 | Initializing database...
postgresql_1 | Configuring hot standby...
postgresql_1 | ‣ Setting postgresql.conf parameter: wal_level = 'hot_standby'
postgresql_1 | ‣ Setting postgresql.conf parameter: max_wal_senders = '16'
postgresql_1 | ‣ Setting postgresql.conf parameter: checkpoint_segments = '8'
postgresql_1 | ‣ Setting postgresql.conf parameter: wal_keep_segments = '32'
postgresql_1 | ‣ Setting postgresql.conf parameter: hot_standby = 'on'
postgresql_1 | ‣ Setting postgresql.conf parameter: data_directory = '/var/lib/postgresql/14/main'
postgresql_1 | ‣ Setting postgresql.conf parameter: log_directory = '/var/log/postgresql'
postgresql_1 | ‣ Setting postgresql.conf parameter: log_filename = 'postgresql-14-main.log'
postgresql_1 | ‣ Setting postgresql.conf parameter: ssl = 'off'
postgresql_1 | Creating database user: gitlab
postgresql_1 | Creating database: gitlabhq_production...
postgresql_1 | ‣ Loading pg_trgm extension...
postgresql_1 | ‣ Loading btree_gist extension...
postgresql_1 | ‣ Granting access to gitlab user...
postgresql_1 | Starting PostgreSQL 14...
postgresql_1 | 2025-03-12 15:00:02.340 UTC [1] LOG: starting PostgreSQL 14.8 (Ubuntu 14.8-1.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, 64-bit
postgresql_1 | 2025-03-12 15:00:02.340 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgresql_1 | 2025-03-12 15:00:02.340 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgresql_1 | 2025-03-12 15:00:02.369 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgresql_1 | 2025-03-12 15:00:02.410 UTC [158] LOG: database system was shut down at 2025-03-12 15:00:02 UTC
postgresql_1 | 2025-03-12 15:00:02.437 UTC [1] LOG: database system is ready to accept connections
postgresql_1 | 2025-03-12 15:36:51.557 UTC [1] LOG: received smart shutdown request
postgresql_1 | 2025-03-12 15:36:51.583 UTC [1] LOG: background worker "logical replication launcher" (PID 164) exited with exit code 1
postgresql_1 | 2025-03-12 15:36:51.583 UTC [159] LOG: shutting down
postgresql_1 | 2025-03-12 15:36:52.006 UTC [1] LOG: database system is shut down
postgresql_1 | Initializing datadir...
postgresql_1 | Initializing certdir...
postgresql_1 | Initializing logdir...
postgresql_1 | Initializing rundir...
postgresql_1 | Setting resolv.conf ACLs...
postgresql_1 | Creating database user: gitlab
postgresql_1 | Creating database: gitlabhq_production...
postgresql_1 | ‣ Loading pg_trgm extension...
postgresql_1 | ‣ Loading btree_gist extension...
postgresql_1 | ‣ Granting access to gitlab user...
postgresql_1 | Starting PostgreSQL 14...
postgresql_1 | 2025-03-12 15:37:27.534 UTC [1] LOG: starting PostgreSQL 14.8 (Ubuntu 14.8-1.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, 64-bit
postgresql_1 | 2025-03-12 15:37:27.534 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgresql_1 | 2025-03-12 15:37:27.534 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgresql_1 | 2025-03-12 15:37:27.587 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgresql_1 | 2025-03-12 15:37:27.643 UTC [83] LOG: database system was shut down at 2025-03-12 15:37:27 UTC
postgresql_1 | 2025-03-12 15:37:27.685 UTC [1] LOG: database system is ready to accept connections
redis_1 | 1:C 12 Mar 2025 14:59:50.001 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 12 Mar 2025 14:59:50.001 # Redis version=6.2.17, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 12 Mar 2025 14:59:50.001 # Configuration loaded
redis_1 | 1:M 12 Mar 2025 14:59:50.007 # Server initialized
redis_1 | 1:M 12 Mar 2025 14:59:50.007 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:signal-handler (1741793811) Received SIGTERM scheduling shutdown...
redis_1 | 1:M 12 Mar 2025 15:36:51.610 # User requested shutdown...
redis_1 | 1:M 12 Mar 2025 15:36:51.638 # Redis is now ready to exit, bye bye...
redis_1 | 1:C 12 Mar 2025 15:37:24.739 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 12 Mar 2025 15:37:24.750 # Redis version=6.2.17, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 12 Mar 2025 15:37:24.750 # Configuration loaded
redis_1 | 1:M 12 Mar 2025 15:37:24.764 # Server initialized
redis_1 | 1:M 12 Mar 2025 15:37:24.771 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 12 Mar 2025 15:37:24.779 # Done loading RDB, keys loaded: 0, keys expired: 0.
Was kann ich bei dem Fehler von ‘gitlab_gitlab_1’ machen? Der Libre Workspace läuft lokal in einer VM.
VG, der LinuxFan