Ok: run: postgres-exporter: (pid 1595) gitlab-ctl statusĭown: alertmanager: 30s, normally up run: log: (pid 708) 145sĭown: gitaly: 29s, normally up run: log: (pid 706) 145sĭown: gitlab-exporter: 29s, normally up run: log: (pid 713) 145sĭown: gitlab-workhorse: 28s, normally up run: log: (pid 704) 145sĭown: grafana: 28s, normally up run: log: (pid 701) 145sĭown: logrotate: 27s, normally up run: log: (pid 703) 145sĭown: nginx: 27s, normally up run: log: (pid 705) 145sĭown: node-exporter: 27s, normally up run: log: (pid 707) 145s Ok: run: postgresql: (pid 1583) gitlab-ctl start postgres-exporter Ok: down: sidekiq: 1s, normally gitlab-ctl start postgresql Ok: down: redis-exporter: 0s, normally up Ok: down: postgres-exporter: 0s, normally up Ok: down: gitlab-workhorse: 0s, normally up Ok: down: gitlab-exporter: 1s, normally up State: installed (13.3.5-ce.0), upgrade available (13.3.6-ce.0)ĭescription: GitLab Community Edition (including NGINX, Postgres, Redis) Ii gitlab-ce 13.3.5-ce.0 amd64 GitLab Community Edition (including NGINX, Postgres, aptitude show gitlab-ce Below the output (truncated as the full upgrade output is long): dpkg -l | grep gitlab So I had to issue a gitlab-ctl restart to get the remaining services running. One thing to note however, is at the end of the upgrade, not all the services were started. You can see in this instance, it took the backup of the postgres database. However, I then started the postgresql and postgres-exporter services, re-checked to see what services were running so that you could see just the postgres ones are active, and then did the upgrade. You will see below I checked the version I had installed (13.3.5), I then checked what was available (13.3.6). Below I have simulated this on my test server and done an upgrade. In an update to my previous post, the package scripts are relying on at least the postgresql services running so that a backup can be taken. Although I expect it’s done like that to just update gitlab, rather than potentially other updates for the operating system when using apt-get upgrade or yum update. Which should pull in the new version, rather than using the install command. Generally though the docs for upgrade should have: I was trying to find a link to something I read before that did mention that the upgrade process will take care of stopping/starting the services, but haven’t been able to find it. Nowhere is there a gitlab-ctl stop command prior to the upgrade. To update to a newer GitLab version, run:įor GitLab Enterprise Edition: # Debian/Ubuntu That means that it will stop what is required, but leave postgresql running so that it can do what it wants to do.įrom the documentation on the link you provided: The upgrade will take care of it, and stop the services when necessary. You don’t need to stop gitlab when running the upgrade. Gitlab preinstall: sudo touch /etc/gitlab/skip-auto-backupĮrror: %pre(gitlab-ce-13.3.6-ce.0.el7.x86_64) scriptlet failed, exit status 1Įrror in PREIN scriptlet in rpm package gitlab-ce-13.3.6-ce.0.el7.x86_64 Gitlab preinstall: Database backup failed! If you want to skip this backup, run the following command and try again: (See full trace by running task with -trace) opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/backup.rake:10:in block (3 levels) in ' /opt/gitlab/embedded/bin/bundle:23:in load’ opt/gitlab/embedded/service/gitlab-rails/lib/backup/database.rb:51:in dump' /opt/gitlab/embedded/service/gitlab-rails/lib/tasks/gitlab/backup.rake:127:in block (4 levels) in ’ Is the server running locally and acceptingĬonnections on Unix domain socket “/var/opt/gitlab/postgresql/.s.PGSQL.5432”? Gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)ĭumping PostgreSQL database gitlabhq_production … pg_dump: connection to database “gitlabhq_production” failed: could not connect to server: No such file or directory Gitlab preinstall: Skipping version check, if you think this is an error exit now Gitlab preinstall: This node does not appear to be running a database
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |