GitLab アップデート 履歴
Table of Contents
8.16.6 -> 8.16.9
gitlab
$ sudo yum update gitlab-ce-8.16.9-ce.0.el7.x86_64.rpm
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
gitlab-ce-8.16.9-ce.0.el7.x86_64.rpm を調べています: gitlab-ce-8.16.9-ce.0.el7.x86_64
次のリポジトリーへの更新として gitlab-ce-8.16.9-ce.0.el7.x86_64.rpm を設定します: gitlab-ce-8.16.6-ce.0.el7.x86_64
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:8.16.6-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:8.16.9-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
依存性を解決しました
=======================================================================================================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
=======================================================================================================================================================================================================
更新します:
gitlab-ce x86_64 8.16.9-ce.0.el7 /gitlab-ce-8.16.9-ce.0.el7.x86_64 767 M
トランザクションの要約
=======================================================================================================================================================================================================
更新 1 パッケージ
合計容量: 767 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1500285738_2017_07_17_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-8.16.9-ce.0.el7.x86_64 1/2
*. *.
*** ***
***** *****
.****** *******
******** ********
,,,,,,,,***********,,,,,,,,,
,,,,,,,,,,*********,,,,,,,,,,,
.,,,,,,,,,,,*******,,,,,,,,,,,,
,,,,,,,,*****,,,,,,,,,.
,,,,,,****,,,,,,
.,,,***,,,,
*,.
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ `/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
gitlab: Thank you for installing GitLab!
gitlab: To configure and start GitLab, RUN THE FOLLOWING COMMAND:
sudo gitlab-ctl reconfigure
gitlab: GitLab should be reachable at http://hogehoge:10080
gitlab: Otherwise configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
gitlab: And running reconfigure again.
gitlab:
gitlab: For a comprehensive list of configuration options please see the Omnibus GitLab readme
gitlab: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
gitlab:
gitlab: GitLab now ships with a newer version of PostgreSQL (9.6.1), and will be used
gitlab: as the default in the next major release. To upgrade, RUN THE FOLLOWING COMMANDS:
sudo gitlab-ctl pg-upgrade
gitlab: For more details, please see:
gitlab: https://docs.gitlab.com/omnibus/settings/database.html#upgrade-packaged-postgresql-server
gitlab:
整理中 : gitlab-ce-8.16.6-ce.0.el7.x86_64 2/2
Shutting down all GitLab services except those needed for migrations
ok: down: gitlab-workhorse: 1s, normally up
ok: down: logrotate: 0s, normally up
ok: down: nginx: 0s, normally up
ok: down: postgresql: 1s, normally up
ok: down: redis: 0s, normally up
ok: down: sidekiq: 0s, normally up
ok: down: unicorn: 0s, normally up
Checking PostgreSQL executables: OK
ok: run: postgresql: (pid 22999) 1s
ok: run: redis: (pid 23007) 0s
run: postgresql: (pid 22999) 1s; run: log: (pid 745) 3130375s
run: redis: (pid 23007) 0s; run: log: (pid 756) 3130375s
Reconfiguring GitLab to apply migrations
/sbin/init: オプション '--version' を認識できません
-.mount loaded active mounted /
gitlab Reconfigured!
Restarting previously running GitLab services
ok: run: gitlab-workhorse: (pid 23601) 0s
ok: run: logrotate: (pid 23608) 0s
ok: run: nginx: (pid 23610) 0s
ok: run: postgresql: (pid 22999) 37s
ok: run: redis: (pid 23007) 36s
ok: run: sidekiq: (pid 23590) 1s
ok: run: unicorn: (pid 23619) 0s
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else. If you need to roll back to the previous version you can
use the database backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-8.16.9-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-8.16.6-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:8.16.9-ce.0.el7
完了しました!
PostgreSQL 9.2.18 -> PostgreSQL 9.6.1
$ sudo gitlab-ctl pg-upgrade
Checking for an omnibus managed postgresql: OK
Checking version of running PostgreSQL: OK
Checking for a newer version of PostgreSQL to install: OK
Upgrading PostgreSQL to 9.6.1
Checking if existing PostgreSQL instances needs to be upgraded: OK
Checking if the PostgreSQL directory has been symlinked elsewhere: OK
Checking if PostgreSQL bin files are symlinked to the expected location: OK
Toggling deploy page:cp /opt/gitlab/embedded/service/gitlab-rails/public/deploy.html /opt/gitlab/embedded/service/gitlab-rails/public/index.html
Toggling deploy page: OK
Toggling services:ok: down: logrotate: 0s, normally up
ok: down: sidekiq: 0s, normally up
Toggling services: OK
Waiting 30 seconds to ensure tasks complete before PostgreSQL upgrade
Please hit Ctrl-C now if you want to cancel the upgrade
Stopping the database:ok: down: postgresql: 1s, normally up
Stopping the database: OK
Update the symlinks: OK
Creating temporary data directory: OK
Initializing the new database: OK
Upgrading the data: OK
Move the old data directory out of the way: OK
Rename the new data directory: OK
Upgrade is complete, doing post configuration steps
Running reconfigure:Starting Chef Client, version 12.12.15
resolving cookbooks for run list: ["gitlab"]
Synchronizing Cookbooks:
- runit (0.14.2)
- package (0.0.0)
- gitlab (0.0.1)
Installing Cookbook Gems:
Compiling Cookbooks...
Recipe: gitlab::default
* directory[/etc/gitlab] action create (up to date)
/sbin/init: オプション '--version' を認識できません
-.mount loaded active mounted /
Converging 284 resources
* directory[/etc/gitlab] action create (up to date)
* directory[Create /var/opt/gitlab] action create (up to date)
* directory[/opt/gitlab/embedded/etc] action create (up to date)
* template[/opt/gitlab/embedded/etc/gitconfig] action create (up to date)
Recipe: gitlab::web-server
* group[Webserver user and group] action create (up to date)
* user[Webserver user and group] action create (up to date)
Recipe: gitlab::users
* directory[/var/opt/gitlab] action create (up to date)
* group[GitLab user and group] action create (up to date)
* user[GitLab user and group] action create (up to date)
* template[/var/opt/gitlab/.gitconfig] action create (up to date)
Recipe: gitlab::gitlab-shell
* ruby_block[directory resource: /var/opt/gitlab/git-data] action run (skipped due to not_if)
* ruby_block[directory resource: /var/opt/gitlab/git-data/repositories] action run (skipped due to not_if)
* ruby_block[directory resource: /var/opt/gitlab/.ssh] action run (skipped due to not_if)
* directory[/opt/gitlab/embedded/service/gitlab-shell/hooks/] action create (up to date)
* directory[/var/log/gitlab/gitlab-shell/] action create (up to date)
* directory[/var/opt/gitlab/gitlab-shell] action create (up to date)
* templatesymlink[Create a config.yml and create a symlink to Rails root] action create
* template[/var/opt/gitlab/gitlab-shell/config.yml] action create (up to date)
* link[Link /opt/gitlab/embedded/service/gitlab-shell/config.yml to /var/opt/gitlab/gitlab-shell/config.yml] action create (up to date)
(up to date)
* link[/opt/gitlab/embedded/service/gitlab-shell/.gitlab_shell_secret] action create (up to date)
* execute[/opt/gitlab/embedded/service/gitlab-shell/bin/gitlab-keys check-permissions] action run
- execute /opt/gitlab/embedded/service/gitlab-shell/bin/gitlab-keys check-permissions
* bash[Set proper security context on ssh files for selinux] action run
- execute "bash" "/tmp/chef-script20170717-24218-tq1pp3"
Recipe: gitlab::gitlab-rails
* directory[/var/log/gitlab] action create (up to date)
* ruby_block[directory resource: /var/opt/gitlab/gitlab-rails/shared] action run (skipped due to not_if)
* ruby_block[directory resource: /var/opt/gitlab/gitlab-rails/shared/artifacts] action run (skipped due to not_if)
* ruby_block[directory resource: /var/opt/gitlab/gitlab-rails/shared/lfs-objects] action run (skipped due to not_if)
* ruby_block[directory resource: /var/opt/gitlab/gitlab-rails/uploads] action run (skipped due to not_if)
* ruby_block[directory resource: /var/opt/gitlab/gitlab-ci/builds] action run (skipped due to not_if)
* ruby_block[directory resource: /var/opt/gitlab/gitlab-rails/shared/pages] action run (skipped due to not_if)
* directory[create /var/opt/gitlab/gitlab-rails/etc] action create (up to date)
* directory[create /opt/gitlab/etc/gitlab-rails] action create (up to date)
* directory[create /var/opt/gitlab/gitlab-rails/working] action create (up to date)
* directory[create /var/opt/gitlab/gitlab-rails/tmp] action create (up to date)
* directory[create /var/opt/gitlab/gitlab-rails/upgrade-status] action create (up to date)
* directory[create /var/log/gitlab/gitlab-rails] action create (up to date)
* directory[/var/opt/gitlab/backups] action create (up to date)
* directory[/var/opt/gitlab/gitlab-rails] action create (up to date)
* directory[/var/opt/gitlab/gitlab-ci] action create (up to date)
* template[/opt/gitlab/etc/gitlab-rails/gitlab-rails-rc] action create (up to date)
* file[/opt/gitlab/embedded/service/gitlab-rails/.secret] action delete (up to date)
* file[/var/opt/gitlab/gitlab-rails/etc/secret] action delete (up to date)
* templatesymlink[Create a database.yml and create a symlink to Rails root] action create
* template[/var/opt/gitlab/gitlab-rails/etc/database.yml] action create (up to date)
* link[Link /opt/gitlab/embedded/service/gitlab-rails/config/database.yml to /var/opt/gitlab/gitlab-rails/etc/database.yml] action create (up to date)
(up to date)
* templatesymlink[Create a secrets.yml and create a symlink to Rails root] action create
* template[/var/opt/gitlab/gitlab-rails/etc/secrets.yml] action create (up to date)
* link[Link /opt/gitlab/embedded/service/gitlab-rails/config/secrets.yml to /var/opt/gitlab/gitlab-rails/etc/secrets.yml] action create (up to date)
(up to date)
* templatesymlink[Create a resque.yml and create a symlink to Rails root] action create
* template[/var/opt/gitlab/gitlab-rails/etc/resque.yml] action create (up to date)
* link[Link /opt/gitlab/embedded/service/gitlab-rails/config/resque.yml to /var/opt/gitlab/gitlab-rails/etc/resque.yml] action create (up to date)
(up to date)
* templatesymlink[Create a aws.yml and create a symlink to Rails root] action delete
* template[/var/opt/gitlab/gitlab-rails/etc/aws.yml] action delete (up to date)
* link[Link /opt/gitlab/embedded/service/gitlab-rails/config/aws.yml to /var/opt/gitlab/gitlab-rails/etc/aws.yml] action delete (up to date)
(up to date)
* templatesymlink[Create a smtp_settings.rb and create a symlink to Rails root] action delete
* template[/var/opt/gitlab/gitlab-rails/etc/smtp_settings.rb] action delete (up to date)
* link[Link /opt/gitlab/embedded/service/gitlab-rails/config/initializers/smtp_settings.rb to /var/opt/gitlab/gitlab-rails/etc/smtp_settings.rb] action delete (up to date)
(up to date)
* templatesymlink[Create a relative_url.rb and create a symlink to Rails root] action delete
* template[/var/opt/gitlab/gitlab-rails/etc/relative_url.rb] action delete (up to date)
* link[Link /opt/gitlab/embedded/service/gitlab-rails/config/initializers/relative_url.rb to /var/opt/gitlab/gitlab-rails/etc/relative_url.rb] action delete (up to date)
(up to date)
* templatesymlink[Create a gitlab.yml and create a symlink to Rails root] action create
* template[/var/opt/gitlab/gitlab-rails/etc/gitlab.yml] action create (up to date)
* link[Link /opt/gitlab/embedded/service/gitlab-rails/config/gitlab.yml to /var/opt/gitlab/gitlab-rails/etc/gitlab.yml] action create (up to date)
(up to date)
* templatesymlink[Create a rack_attack.rb and create a symlink to Rails root] action create
* template[/var/opt/gitlab/gitlab-rails/etc/rack_attack.rb] action create (up to date)
* link[Link /opt/gitlab/embedded/service/gitlab-rails/config/initializers/rack_attack.rb to /var/opt/gitlab/gitlab-rails/etc/rack_attack.rb] action create (up to date)
(up to date)
* templatesymlink[Create a gitlab_workhorse_secret and create a symlink to Rails root] action create
* template[/var/opt/gitlab/gitlab-rails/etc/gitlab_workhorse_secret] action create (up to date)
* link[Link /opt/gitlab/embedded/service/gitlab-rails/.gitlab_workhorse_secret to /var/opt/gitlab/gitlab-rails/etc/gitlab_workhorse_secret] action create (up to date)
(up to date)
* templatesymlink[Create a gitlab_shell_secret and create a symlink to Rails root] action create
* template[/var/opt/gitlab/gitlab-rails/etc/gitlab_shell_secret] action create (up to date)
* link[Link /opt/gitlab/embedded/service/gitlab-rails/.gitlab_shell_secret to /var/opt/gitlab/gitlab-rails/etc/gitlab_shell_secret] action create (up to date)
(up to date)
* directory[/opt/gitlab/etc/gitlab-rails/env] action create (up to date)
* file[/opt/gitlab/etc/gitlab-rails/env/HOME] action create (up to date)
* file[/opt/gitlab/etc/gitlab-rails/env/RAILS_ENV] action create (up to date)
* file[/opt/gitlab/etc/gitlab-rails/env/LD_PRELOAD] action create (up to date)
* file[/opt/gitlab/etc/gitlab-rails/env/SIDEKIQ_MEMORY_KILLER_MAX_RSS] action create (up to date)
* file[/opt/gitlab/etc/gitlab-rails/env/BUNDLE_GEMFILE] action create (up to date)
* file[/opt/gitlab/etc/gitlab-rails/env/PATH] action create (up to date)
* file[/opt/gitlab/etc/gitlab-rails/env/ICU_DATA] action create (up to date)
* file[/opt/gitlab/etc/gitlab-rails/env/PYTHONPATH] action create (up to date)
* link[/opt/gitlab/embedded/service/gitlab-rails/tmp] action create (up to date)
* link[/opt/gitlab/embedded/service/gitlab-rails/public/uploads] action create (up to date)
* link[/opt/gitlab/embedded/service/gitlab-rails/log] action create (up to date)
* link[/var/log/gitlab/gitlab-rails/sidekiq.log] action create (skipped due to not_if)
* file[/opt/gitlab/embedded/service/gitlab-rails/db/schema.rb] action create (up to date)
* remote_file[/var/opt/gitlab/gitlab-rails/VERSION] action create (up to date)
* remote_file[/var/opt/gitlab/gitlab-rails/REVISION] action create (up to date)
* file[/var/opt/gitlab/gitlab-rails/RUBY_VERSION] action create (up to date)
* execute[chown -R root:root /opt/gitlab/embedded/service/gitlab-rails/public] action run
- execute chown -R root:root /opt/gitlab/embedded/service/gitlab-rails/public
* execute[clear the gitlab-rails cache] action nothing (skipped due to action :nothing)
* bash[generate assets] action nothing (skipped due to action :nothing)
* file[/var/opt/gitlab/gitlab-rails/config.ru] action delete (up to date)
Recipe: gitlab::gitlab-ci-proxying
* template[/var/opt/gitlab/nginx/conf/gitlab-ci-http.conf] action delete (up to date)
Recipe: gitlab::selinux
* execute[semodule -i /opt/gitlab/embedded/selinux/rhel/7/gitlab-7.2.0-ssh-keygen.pp] action rungitlab-7.2.0-ssh-keygen 1.0
(skipped due to not_if)
Recipe: gitlab::add_trusted_certs
* directory[/etc/gitlab/trusted-certs] action create (up to date)
* directory[/opt/gitlab/embedded/ssl/certs] action create (up to date)
* file[/opt/gitlab/embedded/ssl/certs/README] action create (up to date)
* ruby_block[Move existing certs and link to /opt/gitlab/embedded/ssl/certs] action run (skipped due to only_if)
Recipe: gitlab::default
* service[create a temporary unicorn service] action nothing (skipped due to action :nothing)
* service[create a temporary ci-unicorn service] action nothing (skipped due to action :nothing)
* service[create a temporary sidekiq service] action nothing (skipped due to action :nothing)
* service[create a temporary ci-sidekiq service] action nothing (skipped due to action :nothing)
* service[create a temporary mailroom service] action nothing (skipped due to action :nothing)
Recipe: runit::systemd
* directory[/usr/lib/systemd/system] action create (up to date)
* cookbook_file[/usr/lib/systemd/system/gitlab-runsvdir.service] action create (up to date)
* file[/etc/systemd/system/default.target.wants/gitlab-runsvdir.service] action delete (up to date)
* execute[systemctl daemon-reload] action nothing (skipped due to action :nothing)
* execute[systemctl enable gitlab-runsvdir] action nothing (skipped due to action :nothing)
* execute[systemctl start gitlab-runsvdir] action nothing (skipped due to action :nothing)
Recipe: gitlab::redis
* group[user and group for redis] action create (up to date)
* user[user and group for redis] action create (up to date)
* group[Socket group] action create (up to date)
* directory[/var/opt/gitlab/redis] action create (up to date)
* directory[/var/log/gitlab/redis] action create (up to date)
* template[/var/opt/gitlab/redis/redis.conf] action create (up to date)
* directory[/opt/gitlab/sv/redis] action create (up to date)
* directory[/opt/gitlab/sv/redis/log] action create (up to date)
* directory[/opt/gitlab/sv/redis/log/main] action create (up to date)
* template[/opt/gitlab/sv/redis/run] action create (up to date)
* template[/opt/gitlab/sv/redis/log/run] action create (up to date)
* template[/var/log/gitlab/redis/config] action create (up to date)
* ruby_block[reload redis svlogd configuration] action nothing (skipped due to action :nothing)
* file[/opt/gitlab/sv/redis/down] action delete (up to date)
* link[/opt/gitlab/init/redis] action create (up to date)
* link[/opt/gitlab/service/redis] action create (up to date)
* ruby_block[supervise_redis_sleep] action run (skipped due to not_if)
* service[redis] action nothing (skipped due to action :nothing)
Recipe: gitlab::postgresql
* group[Postgresql user and group] action create (up to date)
* user[Postgresql user and group] action create (up to date)
* directory[/var/opt/gitlab/postgresql] action create (up to date)
* directory[/var/opt/gitlab/postgresql/data] action create (up to date)
* directory[/var/log/gitlab/postgresql] action create (up to date)
* link[/var/opt/gitlab/postgresql/data] action create (skipped due to not_if)
* file[/var/opt/gitlab/postgresql/.profile] action create (up to date)
* directory[create /etc/sysctl.d for kernel.shmmax] action create (up to date)
* file[create /opt/gitlab/embedded/etc/90-omnibus-gitlab-kernel.shmmax.conf kernel.shmmax] action create (up to date)
* link[/etc/sysctl.d/90-omnibus-gitlab-kernel.shmmax.conf] action create (up to date)
* file[delete /etc/sysctl.d/90-postgresql.conf kernel.shmmax] action delete (skipped due to only_if)
* file[delete /etc/sysctl.d/90-unicorn.conf kernel.shmmax] action delete (skipped due to only_if)
* file[delete /opt/gitlab/embedded/etc/90-omnibus-gitlab.conf kernel.shmmax] action delete (skipped due to only_if)
* file[delete /etc/sysctl.d/90-omnibus-gitlab.conf kernel.shmmax] action delete (skipped due to only_if)
* execute[load sysctl conf kernel.shmmax] action nothing (skipped due to action :nothing)
* directory[create /etc/sysctl.d for kernel.shmall] action create (up to date)
* file[create /opt/gitlab/embedded/etc/90-omnibus-gitlab-kernel.shmall.conf kernel.shmall] action create (up to date)
* link[/etc/sysctl.d/90-omnibus-gitlab-kernel.shmall.conf] action create (up to date)
* file[delete /etc/sysctl.d/90-postgresql.conf kernel.shmall] action delete (skipped due to only_if)
* file[delete /etc/sysctl.d/90-unicorn.conf kernel.shmall] action delete (skipped due to only_if)
* file[delete /opt/gitlab/embedded/etc/90-omnibus-gitlab.conf kernel.shmall] action delete (skipped due to only_if)
* file[delete /etc/sysctl.d/90-omnibus-gitlab.conf kernel.shmall] action delete (skipped due to only_if)
* execute[load sysctl conf kernel.shmall] action nothing (skipped due to action :nothing)
* directory[create /etc/sysctl.d for kernel.sem] action create (up to date)
* file[create /opt/gitlab/embedded/etc/90-omnibus-gitlab-kernel.sem.conf kernel.sem] action create (up to date)
* link[/etc/sysctl.d/90-omnibus-gitlab-kernel.sem.conf] action create (up to date)
* file[delete /etc/sysctl.d/90-postgresql.conf kernel.sem] action delete (skipped due to only_if)
* file[delete /etc/sysctl.d/90-unicorn.conf kernel.sem] action delete (skipped due to only_if)
* file[delete /opt/gitlab/embedded/etc/90-omnibus-gitlab.conf kernel.sem] action delete (skipped due to only_if)
* file[delete /etc/sysctl.d/90-omnibus-gitlab.conf kernel.sem] action delete (skipped due to only_if)
* execute[load sysctl conf kernel.sem] action nothing (skipped due to action :nothing)
* execute[/opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8] action run (skipped due to not_if)
* template[/var/opt/gitlab/postgresql/data/postgresql.conf] action create
- update content in file /var/opt/gitlab/postgresql/data/postgresql.conf from 63e003 to 22228d
--- /var/opt/gitlab/postgresql/data/postgresql.conf 2017-07-17 19:06:34.906725980 +0900
+++ /var/opt/gitlab/postgresql/data/.chef-postgresql.conf20170717-24218-8wv0vc 2017-07-17 19:06:56.584348005 +0900
@@ -1,3 +1,7 @@
+# This file is managed by gitlab-ctl. Manual changes will be
+# erased! To change the contents below, edit /etc/gitlab/gitlab.rb
+# and run `sudo gitlab-ctl reconfigure`.
+
# -----------------------------
# PostgreSQL configuration file
# -----------------------------
@@ -27,7 +31,7 @@
# Memory units: kB = kilobytes Time units: ms = milliseconds
# MB = megabytes s = seconds
# GB = gigabytes min = minutes
-# TB = terabytes h = hours
+# h = hours
# d = days
@@ -38,16 +42,16 @@
# The default values of these variables are driven from the -D command-line
# option or PGDATA environment variable, represented here as ConfigDir.
-#data_directory = 'ConfigDir' # use data in another directory
- # (change requires restart)
-#hba_file = 'ConfigDir/pg_hba.conf' # host-based authentication file
- # (change requires restart)
-#ident_file = 'ConfigDir/pg_ident.conf' # ident configuration file
- # (change requires restart)
+#data_directory = 'ConfigDir' # use data in another directory
+ # (change requires restart)
+#hba_file = 'ConfigDir/pg_hba.conf' # host-based authentication file
+ # (change requires restart)
+#ident_file = 'ConfigDir/pg_ident.conf' # ident configuration file
+ # (change requires restart)
# If external_pid_file is not explicitly set, no extra PID file is written.
-#external_pid_file = '' # write an extra PID file
- # (change requires restart)
+#external_pid_file = '(none)' # write an extra PID file
+ # (change requires restart)
#------------------------------------------------------------------------------
@@ -56,52 +60,48 @@
# - Connection Settings -
-#listen_addresses = 'localhost' # what IP address(es) to listen on;
- # comma-separated list of addresses;
- # defaults to 'localhost'; use '*' for all
- # (change requires restart)
-#port = 5432 # (change requires restart)
-max_connections = 100 # (change requires restart)
-#superuser_reserved_connections = 3 # (change requires restart)
-#unix_socket_directories = '/tmp' # comma-separated list of directories
- # (change requires restart)
-#unix_socket_group = '' # (change requires restart)
-#unix_socket_permissions = 0777 # begin with 0 to use octal notation
- # (change requires restart)
-#bonjour = off # advertise server via Bonjour
- # (change requires restart)
-#bonjour_name = '' # defaults to the computer name
- # (change requires restart)
+listen_addresses = '' # what IP address(es) to listen on;
+ # comma-separated list of addresses;
+ # defaults to 'localhost', '*' = all
+ # (change requires restart)
+port = 5432 # (change requires restart)
+max_connections = 200 # (change requires restart)
+# Note: Increasing max_connections costs ~400 bytes of shared memory per
+# connection slot, plus lock space (see max_locks_per_transaction).
+#superuser_reserved_connections = 3 # (change requires restart)
+unix_socket_directories = '/var/opt/gitlab/postgresql' # (change requires restart)
+#unix_socket_group = '' # (change requires restart)
+#unix_socket_permissions = 0777 # begin with 0 to use octal notation
+ # (change requires restart)
+#bonjour = off # advertise server via Bonjour
+ # (change requires restart)
+#bonjour_name = '' # defaults to the computer name
+ # (change requires restart)
# - Security and Authentication -
-#authentication_timeout = 1min # 1s-600s
-#ssl = off # (change requires restart)
-#ssl_ciphers = 'HIGH:MEDIUM:+3DES:!aNULL' # allowed SSL ciphers
- # (change requires restart)
-#ssl_prefer_server_ciphers = on # (change requires restart)
-#ssl_ecdh_curve = 'prime256v1' # (change requires restart)
-#ssl_cert_file = 'server.crt' # (change requires restart)
-#ssl_key_file = 'server.key' # (change requires restart)
-#ssl_ca_file = '' # (change requires restart)
-#ssl_crl_file = '' # (change requires restart)
+#authentication_timeout = 1min # 1s-600s
+#ssl = off # (change requires restart)
+#ssl_ciphers = 'ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH' # allowed SSL ciphers
+ # (change requires restart)
+#ssl_renegotiation_limit = 512MB # amount of data between renegotiations
#password_encryption = on
#db_user_namespace = off
-#row_security = on
-# GSSAPI using Kerberos
+# Kerberos and GSSAPI
#krb_server_keyfile = ''
+#krb_srvname = 'postgres' # (Kerberos only)
#krb_caseins_users = off
# - TCP Keepalives -
# see "man 7 tcp" for details
-#tcp_keepalives_idle = 0 # TCP_KEEPIDLE, in seconds;
- # 0 selects the system default
-#tcp_keepalives_interval = 0 # TCP_KEEPINTVL, in seconds;
- # 0 selects the system default
-#tcp_keepalives_count = 0 # TCP_KEEPCNT;
- # 0 selects the system default
+#tcp_keepalives_idle = 0 # TCP_KEEPIDLE, in seconds;
+ # 0 selects the system default
+#tcp_keepalives_interval = 0 # TCP_KEEPINTVL, in seconds;
+ # 0 selects the system default
+#tcp_keepalives_count = 0 # TCP_KEEPCNT;
+ # 0 selects the system default
#------------------------------------------------------------------------------
@@ -110,63 +110,42 @@
# - Memory -
-shared_buffers = 128MB # min 128kB
- # (change requires restart)
-#huge_pages = try # on, off, or try
- # (change requires restart)
-#temp_buffers = 8MB # min 800kB
-#max_prepared_transactions = 0 # zero disables the feature
- # (change requires restart)
-# Caution: it is not advisable to set max_prepared_transactions nonzero unless
-# you actively intend to use prepared transactions.
-#work_mem = 4MB # min 64kB
-#maintenance_work_mem = 64MB # min 1MB
-#replacement_sort_tuples = 150000 # limits use of replacement selection sort
-#autovacuum_work_mem = -1 # min 1MB, or -1 to use maintenance_work_mem
-#max_stack_depth = 2MB # min 100kB
-dynamic_shared_memory_type = posix # the default is the first option
- # supported by the operating system:
- # posix
- # sysv
- # windows
- # mmap
- # use none to disable dynamic shared memory
+shared_buffers = 924MB # min 128kB
+ # (change requires restart)
+#temp_buffers = 8MB # min 800kB
+#max_prepared_transactions = 0 # zero disables the feature
+ # (change requires restart)
+# Note: Increasing max_prepared_transactions costs ~600 bytes of shared memory
+# per transaction slot, plus lock space (see max_locks_per_transaction).
+# It is not advisable to set max_prepared_transactions nonzero unless you
+# actively intend to use prepared transactions.
+work_mem = 8MB # min 64kB
+maintenance_work_mem = 16MB # 16MB # min 1MB
+#max_stack_depth = 2MB # min 100kB
-# - Disk -
-
-#temp_file_limit = -1 # limits per-process temp file space
- # in kB, or -1 for no limit
-
# - Kernel Resource Usage -
-#max_files_per_process = 1000 # min 25
- # (change requires restart)
-#shared_preload_libraries = '' # (change requires restart)
+#max_files_per_process = 1000 # min 25
+ # (change requires restart)
+shared_preload_libraries = '' # (change requires restart)
# - Cost-Based Vacuum Delay -
-#vacuum_cost_delay = 0 # 0-100 milliseconds
-#vacuum_cost_page_hit = 1 # 0-10000 credits
-#vacuum_cost_page_miss = 10 # 0-10000 credits
-#vacuum_cost_page_dirty = 20 # 0-10000 credits
-#vacuum_cost_limit = 200 # 1-10000 credits
+#vacuum_cost_delay = 0ms # 0-100 milliseconds
+#vacuum_cost_page_hit = 1 # 0-10000 credits
+#vacuum_cost_page_miss = 10 # 0-10000 credits
+#vacuum_cost_page_dirty = 20 # 0-10000 credits
+#vacuum_cost_limit = 200 # 1-10000 credits
# - Background Writer -
-#bgwriter_delay = 200ms # 10-10000ms between rounds
-#bgwriter_lru_maxpages = 100 # 0-1000 max buffers written/round
-#bgwriter_lru_multiplier = 2.0 # 0-10.0 multiplier on buffers scanned/round
-#bgwriter_flush_after = 0 # 0 disables,
- # default is 512kB on linux, 0 otherwise
+#bgwriter_delay = 200ms # 10-10000ms between rounds
+#bgwriter_lru_maxpages = 100 # 0-1000 max buffers written/round
+#bgwriter_lru_multiplier = 2.0 # 0-10.0 multipler on buffers scanned/round
# - Asynchronous Behavior -
-#effective_io_concurrency = 1 # 1-1000; 0 disables prefetching
-#max_worker_processes = 8 # (change requires restart)
-#max_parallel_workers_per_gather = 0 # taken from max_worker_processes
-#old_snapshot_threshold = -1 # 1min-60d; -1 disables; 0 is immediate
- # (change requires restart)
-#backend_flush_after = 0 # 0 disables, default is 0
+#effective_io_concurrency = 1 # 1-1000. 0 disables prefetching
#------------------------------------------------------------------------------
@@ -175,102 +154,75 @@
# - Settings -
-#wal_level = minimal # minimal, replica, or logical
- # (change requires restart)
-#fsync = on # flush data to disk for crash safety
- # (turning this off can cause
- # unrecoverable data corruption)
-#synchronous_commit = on # synchronization level;
- # off, local, remote_write, remote_apply, or on
-#wal_sync_method = fsync # the default is the first option
- # supported by the operating system:
- # open_datasync
- # fdatasync (default on Linux)
- # fsync
- # fsync_writethrough
- # open_sync
-#full_page_writes = on # recover from partial page writes
-#wal_compression = off # enable compression of full-page writes
-#wal_log_hints = off # also do full page writes of non-critical updates
- # (change requires restart)
-#wal_buffers = -1 # min 32kB, -1 sets based on shared_buffers
- # (change requires restart)
-#wal_writer_delay = 200ms # 1-10000 milliseconds
-#wal_writer_flush_after = 1MB # 0 disables
+wal_level = minimal
+ # (change requires restart)
+#fsync = on # turns forced synchronization on or off
+#synchronous_commit = on # synchronization level; on, off, or local
+#wal_sync_method = fsync # the default is the first option
+ # supported by the operating system:
+ # open_datasync
+ # fdatasync (default on Linux)
+ # fsync
+ # fsync_writethrough
+ # open_sync
+#full_page_writes = on # recover from partial page writes
+wal_buffers = -1 # -1 # min 32kB, -1 sets based on shared_buffers
+ # (change requires restart)
+#wal_writer_delay = 200ms # 1-10000 milliseconds
-#commit_delay = 0 # range 0-100000, in microseconds
-#commit_siblings = 5 # range 1-1000
+#commit_delay = 0 # range 0-100000, in microseconds
+#commit_siblings = 5 # range 1-1000
# - Checkpoints -
+min_wal_size = 80MB
+max_wal_size = 1GB
+checkpoint_timeout = 5min # range 30s-1h, default 5min
+checkpoint_completion_target = 0.9 # checkpoint target duration, 0.0 - 1.0, default 0.5
+checkpoint_warning = 30s # 0 disables, default 30s
-#checkpoint_timeout = 5min # range 30s-1d
-#max_wal_size = 1GB
-#min_wal_size = 80MB
-#checkpoint_completion_target = 0.5 # checkpoint target duration, 0.0 - 1.0
-#checkpoint_flush_after = 0 # 0 disables,
- # default is 256kB on linux, 0 otherwise
-#checkpoint_warning = 30s # 0 disables
-
# - Archiving -
-#archive_mode = off # enables archiving; off, on, or always
- # (change requires restart)
-#archive_command = '' # command to use to archive a logfile segment
- # placeholders: %p = path of file to archive
- # %f = file name only
- # e.g. 'test ! -f /mnt/server/archivedir/%f && cp %p /mnt/server/archivedir/%f'
-#archive_timeout = 0 # force a logfile segment switch after this
- # number of seconds; 0 disables
+#archive_mode = off # allows archiving to be done
+ # (change requires restart)
+#archive_command = '' # command to use to archive a logfile segment
+#archive_timeout = 0 # force a logfile segment switch after this
+ # number of seconds; 0 disables
#------------------------------------------------------------------------------
# REPLICATION
#------------------------------------------------------------------------------
-# - Sending Server(s) -
-
-# Set these on the master and on any standby that will send replication data.
-
-#max_wal_senders = 0 # max number of walsender processes
- # (change requires restart)
-#wal_keep_segments = 0 # in logfile segments, 16MB each; 0 disables
-#wal_sender_timeout = 60s # in milliseconds; 0 disables
-
-#max_replication_slots = 0 # max number of replication slots
- # (change requires restart)
-#track_commit_timestamp = off # collect timestamp of transaction commit
- # (change requires restart)
-
# - Master Server -
-# These settings are ignored on a standby server.
+# These settings are ignored on a standby server
-#synchronous_standby_names = '' # standby servers that provide sync rep
- # number of sync standbys and comma-separated list of application_name
- # from standby(s); '*' = all
-#vacuum_defer_cleanup_age = 0 # number of xacts by which cleanup is delayed
+max_wal_senders = 0
+ # (change requires restart)
+#wal_sender_delay = 1s # walsender cycle time, 1-10000 milliseconds
+wal_keep_segments = 10
+#vacuum_defer_cleanup_age = 0 # number of xacts by which cleanup is delayed
+#replication_timeout = 60s # in milliseconds; 0 disables
+#synchronous_standby_names = '' # standby servers that provide sync rep
+ # comma-separated list of application_name
+ # from standby(s); '*' = all
# - Standby Servers -
-# These settings are ignored on a master server.
+# These settings are ignored on a master server
-#hot_standby = off # "on" allows queries during recovery
- # (change requires restart)
-#max_standby_archive_delay = 30s # max delay before canceling queries
- # when reading WAL from archive;
- # -1 allows indefinite delay
-#max_standby_streaming_delay = 30s # max delay before canceling queries
- # when reading streaming WAL;
- # -1 allows indefinite delay
-#wal_receiver_status_interval = 10s # send replies at least this often
- # 0 disables
-#hot_standby_feedback = off # send info from standby to prevent
- # query conflicts
-#wal_receiver_timeout = 60s # time that receiver waits for
- # communication from master
- # in milliseconds; 0 disables
-#wal_retrieve_retry_interval = 5s # time to wait before retrying to
- # retrieve WAL after a failed attempt
+hot_standby = off
+ # (change requires restart)
+#max_standby_archive_delay = 30s # max delay before canceling queries
+ # when reading WAL from archive;
+ # -1 allows indefinite delay
+#max_standby_streaming_delay = 30s # max delay before canceling queries
+ # when reading streaming WAL;
+ # -1 allows indefinite delay
+#wal_receiver_status_interval = 10s # send replies at least this often
+ # 0 disables
+#hot_standby_feedback = off # send info from standby to prevent
+ # query conflicts
#------------------------------------------------------------------------------
@@ -283,7 +235,6 @@
#enable_hashagg = on
#enable_hashjoin = on
#enable_indexscan = on
-#enable_indexonlyscan = on
#enable_material = on
#enable_mergejoin = on
#enable_nestloop = on
@@ -293,35 +244,31 @@
# - Planner Cost Constants -
-#seq_page_cost = 1.0 # measured on an arbitrary scale
-#random_page_cost = 4.0 # same scale as above
-#cpu_tuple_cost = 0.01 # same scale as above
-#cpu_index_tuple_cost = 0.005 # same scale as above
-#cpu_operator_cost = 0.0025 # same scale as above
-#parallel_tuple_cost = 0.1 # same scale as above
-#parallel_setup_cost = 1000.0 # same scale as above
-#min_parallel_relation_size = 8MB
-#effective_cache_size = 4GB
+#seq_page_cost = 1.0 # measured on an arbitrary scale
+#random_page_cost = 4.0 # same scale as above
+#cpu_tuple_cost = 0.01 # same scale as above
+#cpu_index_tuple_cost = 0.005 # same scale as above
+#cpu_operator_cost = 0.0025 # same scale as above
+effective_cache_size = 1848MB # Default 128MB
# - Genetic Query Optimizer -
#geqo = on
#geqo_threshold = 12
-#geqo_effort = 5 # range 1-10
-#geqo_pool_size = 0 # selects default based on effort
-#geqo_generations = 0 # selects default based on effort
-#geqo_selection_bias = 2.0 # range 1.5-2.0
-#geqo_seed = 0.0 # range 0.0-1.0
+#geqo_effort = 5 # range 1-10
+#geqo_pool_size = 0 # selects default based on effort
+#geqo_generations = 0 # selects default based on effort
+#geqo_selection_bias = 2.0 # range 1.5-2.0
+#geqo_seed = 0.0 # range 0.0-1.0
# - Other Planner Options -
-#default_statistics_target = 100 # range 1-10000
-#constraint_exclusion = partition # on, off, or partition
-#cursor_tuple_fraction = 0.1 # range 0.0-1.0
+#default_statistics_target = 100 # range 1-10000
+#constraint_exclusion = partition # on, off, or partition
+#cursor_tuple_fraction = 0.1 # range 0.0-1.0
#from_collapse_limit = 8
-#join_collapse_limit = 8 # 1 disables collapsing of explicit
- # JOIN clauses
-#force_parallel_mode = off
+#join_collapse_limit = 8 # 1 disables collapsing of explicit
+ # JOIN clauses
#------------------------------------------------------------------------------
@@ -330,92 +277,93 @@
# - Where to Log -
-#log_destination = 'stderr' # Valid values are combinations of
- # stderr, csvlog, syslog, and eventlog,
- # depending on platform. csvlog
- # requires logging_collector to be on.
+#log_destination = 'stderr' # Valid values are combinations of
+ # stderr, csvlog, syslog, and eventlog,
+ # depending on platform. csvlog
+ # requires logging_collector to be on.
# This is used when logging to stderr:
-#logging_collector = off # Enable capturing of stderr and csvlog
- # into log files. Required to be on for
- # csvlogs.
- # (change requires restart)
+#logging_collector = off # Enable capturing of stderr and csvlog
+ # into log files. Required to be on for
+ # csvlogs.
+ # (change requires restart)
# These are only used if logging_collector is on:
-#log_directory = 'pg_log' # directory where log files are written,
- # can be absolute or relative to PGDATA
-#log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # log file name pattern,
- # can include strftime() escapes
-#log_file_mode = 0600 # creation mode for log files,
- # begin with 0 to use octal notation
-#log_truncate_on_rotation = off # If on, an existing log file with the
- # same name as the new log file will be
- # truncated rather than appended to.
- # But such truncation only occurs on
- # time-driven rotation, not on restarts
- # or size-driven rotation. Default is
- # off, meaning append to existing files
- # in all cases.
-#log_rotation_age = 1d # Automatic rotation of logfiles will
- # happen after that time. 0 disables.
-#log_rotation_size = 10MB # Automatic rotation of logfiles will
- # happen after that much log output.
- # 0 disables.
+#log_directory = 'pg_log' # directory where log files are written,
+ # can be absolute or relative to PGDATA
+#log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # log file name pattern,
+ # can include strftime() escapes
+#log_file_mode = 0600 # creation mode for log files,
+ # begin with 0 to use octal notation
+#log_truncate_on_rotation = off # If on, an existing log file with the
+ # same name as the new log file will be
+ # truncated rather than appended to.
+ # But such truncation only occurs on
+ # time-driven rotation, not on restarts
+ # or size-driven rotation. Default is
+ # off, meaning append to existing files
+ # in all cases.
+#log_rotation_age = 1d # Automatic rotation of logfiles will
+ # happen after that time. 0 disables.
+#log_rotation_size = 10MB # Automatic rotation of logfiles will
+ # happen after that much log output.
+ # 0 disables.
# These are relevant when logging to syslog:
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'
-#syslog_sequence_numbers = on
-#syslog_split_messages = on
-# This is only relevant when logging to eventlog (win32):
-#event_source = 'PostgreSQL'
+#silent_mode = off # Run server silently.
+ # DO NOT USE without syslog or
+ # logging_collector
+ # (change requires restart)
+
# - When to Log -
-#client_min_messages = notice # values in order of decreasing detail:
- # debug5
- # debug4
- # debug3
- # debug2
- # debug1
- # log
- # notice
- # warning
- # error
+#client_min_messages = notice # values in order of decreasing detail:
+ # debug5
+ # debug4
+ # debug3
+ # debug2
+ # debug1
+ # log
+ # notice
+ # warning
+ # error
-#log_min_messages = warning # values in order of decreasing detail:
- # debug5
- # debug4
- # debug3
- # debug2
- # debug1
- # info
- # notice
- # warning
- # error
- # log
- # fatal
- # panic
+#log_min_messages = warning # values in order of decreasing detail:
+ # debug5
+ # debug4
+ # debug3
+ # debug2
+ # debug1
+ # info
+ # notice
+ # warning
+ # error
+ # log
+ # fatal
+ # panic
-#log_min_error_statement = error # values in order of decreasing detail:
- # debug5
- # debug4
- # debug3
- # debug2
- # debug1
- # info
- # notice
- # warning
- # error
- # log
- # fatal
- # panic (effectively off)
+#log_min_error_statement = error # values in order of decreasing detail:
+ # debug5
+ # debug4
+ # debug3
+ # debug2
+ # debug1
+ # info
+ # notice
+ # warning
+ # error
+ # log
+ # fatal
+ # panic (effectively off)
-#log_min_duration_statement = -1 # -1 is disabled, 0 logs all statements
- # and their durations, > 0 logs only
- # statements running at least this number
- # of milliseconds
+log_min_duration_statement = -1 # -1 is disabled, 0 logs all statements
+ # and their durations, > 0 logs only
+ # statements running at least this number
+ # of milliseconds
# - What to Log -
@@ -428,45 +376,35 @@
#log_connections = off
#log_disconnections = off
#log_duration = off
-#log_error_verbosity = default # terse, default, or verbose messages
+#log_error_verbosity = default # terse, default, or verbose messages
#log_hostname = off
-#log_line_prefix = '' # special values:
- # %a = application name
- # %u = user name
- # %d = database name
- # %r = remote host and port
- # %h = remote host
- # %p = process ID
- # %t = timestamp without milliseconds
- # %m = timestamp with milliseconds
- # %n = timestamp with milliseconds (as a Unix epoch)
- # %i = command tag
- # %e = SQL state
- # %c = session ID
- # %l = session line number
- # %s = session start timestamp
- # %v = virtual transaction ID
- # %x = transaction ID (0 if none)
- # %q = stop here in non-session
- # processes
- # %% = '%'
- # e.g. '<%u%%%d> '
-#log_lock_waits = off # log lock waits >= deadlock_timeout
-#log_statement = 'none' # none, ddl, mod, all
-#log_replication_commands = off
-#log_temp_files = -1 # log temporary files equal or larger
- # than the specified size in kilobytes;
- # -1 disables, 0 logs all temp files
-log_timezone = 'Japan'
+log_line_prefix = '' # default '', special values:
+ # %a = application name
+ # %u = user name
+ # %d = database name
+ # %r = remote host and port
+ # %h = remote host
+ # %p = process ID
+ # %t = timestamp without milliseconds
+ # %m = timestamp with milliseconds
+ # %i = command tag
+ # %e = SQL state
+ # %c = session ID
+ # %l = session line number
+ # %s = session start timestamp
+ # %v = virtual transaction ID
+ # %x = transaction ID (0 if none)
+ # %q = stop here in non-session
+ # processes
+ # %% = '%'
+#log_lock_waits = off # log lock waits >= deadlock_timeout
+#log_statement = 'none' # none, ddl, mod, all
+#log_temp_files = -1 # log temporary files equal or larger
+ # than the specified size in kilobytes;
+ # -1 disables, 0 logs all temp files
+#log_timezone = '(defaults to server environment setting)'
-# - Process Title -
-
-#cluster_name = '' # added to process titles if nonempty
- # (change requires restart)
-#update_process_title = on
-
-
#------------------------------------------------------------------------------
# RUNTIME STATISTICS
#------------------------------------------------------------------------------
@@ -475,9 +413,9 @@
#track_activities = on
#track_counts = on
-#track_io_timing = off
-#track_functions = none # none, pl, all
-#track_activity_query_size = 1024 # (change requires restart)
+#track_functions = none # none, pl, all
+track_activity_query_size = 1024 # (change requires restart)
+#update_process_title = on
#stats_temp_directory = 'pg_stat_tmp'
@@ -493,32 +431,29 @@
# AUTOVACUUM PARAMETERS
#------------------------------------------------------------------------------
-#autovacuum = on # Enable autovacuum subprocess? 'on'
- # requires track_counts to also be on.
-#log_autovacuum_min_duration = -1 # -1 disables, 0 logs all actions and
- # their durations, > 0 logs only
- # actions running at least this number
- # of milliseconds.
-#autovacuum_max_workers = 3 # max number of autovacuum subprocesses
- # (change requires restart)
-#autovacuum_naptime = 1min # time between autovacuum runs
-#autovacuum_vacuum_threshold = 50 # min number of row updates before
- # vacuum
-#autovacuum_analyze_threshold = 50 # min number of row updates before
- # analyze
-#autovacuum_vacuum_scale_factor = 0.2 # fraction of table size before vacuum
-#autovacuum_analyze_scale_factor = 0.1 # fraction of table size before analyze
-#autovacuum_freeze_max_age = 200000000 # maximum XID age before forced vacuum
- # (change requires restart)
-#autovacuum_multixact_freeze_max_age = 400000000 # maximum multixact age
- # before forced vacuum
- # (change requires restart)
-#autovacuum_vacuum_cost_delay = 20ms # default vacuum cost delay for
- # autovacuum, in milliseconds;
- # -1 means use vacuum_cost_delay
-#autovacuum_vacuum_cost_limit = -1 # default vacuum cost limit for
- # autovacuum, -1 means use
- # vacuum_cost_limit
+autovacuum = on # Enable autovacuum subprocess? 'on'
+ # requires track_counts to also be on.
+log_autovacuum_min_duration = -1 # -1 disables, 0 logs all actions and
+ # their durations, > 0 logs only
+ # actions running at least this number
+ # of milliseconds.
+autovacuum_max_workers = 3 # max number of autovacuum subprocesses
+ # (change requires restart)
+autovacuum_naptime = 1min # time between autovacuum runs
+autovacuum_vacuum_threshold = 50 # min number of row updates before
+ # vacuum
+autovacuum_analyze_threshold = 50 # min number of row updates before
+ # analyze
+autovacuum_vacuum_scale_factor = 0.02 # fraction of table size before vacuum
+autovacuum_analyze_scale_factor = 0.01 # fraction of table size before analyze
+autovacuum_freeze_max_age = 200000000 # maximum XID age before forced vacuum
+ # (change requires restart)
+autovacuum_vacuum_cost_delay = 20ms # default vacuum cost delay for
+ # autovacuum, in milliseconds;
+ # -1 means use vacuum_cost_delay
+autovacuum_vacuum_cost_limit = -1 # default vacuum cost limit for
+ # autovacuum, -1 means use
+ # vacuum_cost_limit
#------------------------------------------------------------------------------
@@ -527,50 +462,44 @@
# - Statement Behavior -
-#search_path = '"$user", public' # schema names
-#default_tablespace = '' # a tablespace name, '' uses the default
-#temp_tablespaces = '' # a list of tablespace names, '' uses
- # only default tablespace
+#search_path = '"$user",public' # schema names
+#default_tablespace = '' # a tablespace name, '' uses the default
+#temp_tablespaces = '' # a list of tablespace names, '' uses
+ # only default tablespace
#check_function_bodies = on
#default_transaction_isolation = 'read committed'
#default_transaction_read_only = off
#default_transaction_deferrable = off
#session_replication_role = 'origin'
-#statement_timeout = 0 # in milliseconds, 0 is disabled
-#lock_timeout = 0 # in milliseconds, 0 is disabled
-#idle_in_transaction_session_timeout = 0 # in milliseconds, 0 is disabled
+statement_timeout = 0
#vacuum_freeze_min_age = 50000000
#vacuum_freeze_table_age = 150000000
-#vacuum_multixact_freeze_min_age = 5000000
-#vacuum_multixact_freeze_table_age = 150000000
-#bytea_output = 'hex' # hex, escape
+#bytea_output = 'hex' # hex, escape
#xmlbinary = 'base64'
#xmloption = 'content'
-#gin_fuzzy_search_limit = 0
-#gin_pending_list_limit = 4MB
# - Locale and Formatting -
datestyle = 'iso, mdy'
#intervalstyle = 'postgres'
-timezone = 'Japan'
+#timezone = '(defaults to server environment setting)'
#timezone_abbreviations = 'Default' # Select the set of available time zone
- # abbreviations. Currently, there are
- # Default
- # Australia (historical usage)
- # India
- # You can create your own file in
- # share/timezonesets/.
-#extra_float_digits = 0 # min -15, max 3
-#client_encoding = sql_ascii # actually, defaults to database
- # encoding
+ # abbreviations. Currently, there are
+ # Default
+ # Australia
+ # India
+ # You can create your own file in
+ # share/timezonesets/.
+#extra_float_digits = 0 # min -15, max 3
+#client_encoding = sql_ascii # actually, defaults to database
+ # encoding
# These settings are initialized by initdb, but they can be changed.
-lc_messages = 'en_US.UTF-8' # locale for system error message
- # strings
-lc_monetary = 'en_US.UTF-8' # locale for monetary formatting
-lc_numeric = 'en_US.UTF-8' # locale for number formatting
-lc_time = 'en_US.UTF-8' # locale for time formatting
+lc_messages = 'C' # locale for system error message
+ # strings
+lc_monetary = 'C' # locale for monetary formatting
+lc_numeric = 'C' # locale for number formatting
+lc_time = 'C' # locale for time formatting
# default configuration for text search
default_text_search_config = 'pg_catalog.english'
@@ -579,7 +508,6 @@
#dynamic_library_path = '$libdir'
#local_preload_libraries = ''
-#session_preload_libraries = ''
#------------------------------------------------------------------------------
@@ -587,12 +515,14 @@
#------------------------------------------------------------------------------
#deadlock_timeout = 1s
-#max_locks_per_transaction = 64 # min 10
- # (change requires restart)
-#max_pred_locks_per_transaction = 64 # min 10
- # (change requires restart)
+#max_locks_per_transaction = 64 # min 10
+ # (change requires restart)
+# Note: Each lock table slot uses ~270 bytes of shared memory, and there are
+# max_locks_per_transaction * (max_connections + max_prepared_transactions)
+# lock table slots.
+#max_pred_locks_per_transaction = 64 # min 10
+ # (change requires restart)
-
#------------------------------------------------------------------------------
# VERSION/PLATFORM COMPATIBILITY
#------------------------------------------------------------------------------
@@ -600,11 +530,10 @@
# - Previous PostgreSQL Versions -
#array_nulls = on
-#backslash_quote = safe_encoding # on, off, or safe_encoding
+#backslash_quote = safe_encoding # on, off, or safe_encoding
#default_with_oids = off
#escape_string_warning = on
#lo_compat_privileges = off
-#operator_precedence_warning = off
#quote_all_identifiers = off
#sql_inheritance = on
#standard_conforming_strings = on
@@ -619,26 +548,13 @@
# ERROR HANDLING
#------------------------------------------------------------------------------
-#exit_on_error = off # terminate session on any error?
-#restart_after_crash = on # reinitialize after backend crash?
+#exit_on_error = off # terminate session on any error?
+#restart_after_crash = on # reinitialize after backend crash?
#------------------------------------------------------------------------------
-# CONFIG FILE INCLUDES
-#------------------------------------------------------------------------------
-
-# These options allow settings to be loaded from files other than the
-# default postgresql.conf.
-
-#include_dir = 'conf.d' # include files ending in '.conf' from
- # directory 'conf.d'
-#include_if_exists = 'exists.conf' # include file only if it exists
-#include = 'special.conf' # include file
-
-
-#------------------------------------------------------------------------------
# CUSTOMIZED OPTIONS
#------------------------------------------------------------------------------
-# Add settings for extensions here
+#custom_variable_classes = '' # list of custom variable class names
- change mode from '0600' to '0644'
- restore selinux security context
* service[postgresql] action restart
- restart service service[postgresql]
* template[/var/opt/gitlab/postgresql/data/pg_hba.conf] action create
- update content in file /var/opt/gitlab/postgresql/data/pg_hba.conf from d7d331 to 40e348
--- /var/opt/gitlab/postgresql/data/pg_hba.conf 2017-07-17 19:06:34.907725963 +0900
+++ /var/opt/gitlab/postgresql/data/.chef-pg_hba.conf20170717-24218-24pl7z 2017-07-17 19:06:57.134337556 +0900
@@ -1,94 +1,74 @@
+# This file is managed by gitlab-ctl. Manual changes will be
+# erased! To change the contents below, edit /etc/gitlab/gitlab.rb
+# and run `sudo gitlab-ctl reconfigure`.
+
# PostgreSQL Client Authentication Configuration File
# ===================================================
#
-# Refer to the "Client Authentication" section in the PostgreSQL
-# documentation for a complete description of this file. A short
-# synopsis follows.
+# Refer to the "Client Authentication" section in the
+# PostgreSQL documentation for a complete description
+# of this file. A short synopsis follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access. Records take one of these forms:
#
-# local DATABASE USER METHOD [OPTIONS]
-# host DATABASE USER ADDRESS METHOD [OPTIONS]
-# hostssl DATABASE USER ADDRESS METHOD [OPTIONS]
-# hostnossl DATABASE USER ADDRESS METHOD [OPTIONS]
+# local DATABASE USER METHOD [OPTION]
+# host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
+# hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
+# hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
#
# (The uppercase items must be replaced by actual values.)
#
-# The first field is the connection type: "local" is a Unix-domain
-# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
-# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
-# plain TCP/IP socket.
+# The first field is the connection type: "local" is a Unix-domain socket,
+# "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an
+# SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.
#
-# DATABASE can be "all", "sameuser", "samerole", "replication", a
-# database name, or a comma-separated list thereof. The "all"
-# keyword does not match "replication". Access to replication
-# must be enabled in a separate record (see example below).
+# DATABASE can be "all", "sameuser", "samerole", a database name, or
+# a comma-separated list thereof.
#
-# USER can be "all", a user name, a group name prefixed with "+", or a
-# comma-separated list thereof. In both the DATABASE and USER fields
-# you can also write a file name prefixed with "@" to include names
-# from a separate file.
+# USER can be "all", a user name, a group name prefixed with "+", or
+# a comma-separated list thereof. In both the DATABASE and USER fields
+# you can also write a file name prefixed with "@" to include names from
+# a separate file.
#
-# ADDRESS specifies the set of hosts the record matches. It can be a
-# host name, or it is made up of an IP address and a CIDR mask that is
-# an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
-# specifies the number of significant bits in the mask. A host name
-# that starts with a dot (.) matches a suffix of the actual host name.
-# Alternatively, you can write an IP address and netmask in separate
-# columns to specify the set of hosts. Instead of a CIDR-address, you
-# can write "samehost" to match any of the server's own IP addresses,
-# or "samenet" to match any address in any subnet that the server is
-# directly connected to.
+# CIDR-ADDRESS specifies the set of hosts the record matches.
+# It is made up of an IP address and a CIDR mask that is an integer
+# (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
+# the number of significant bits in the mask. Alternatively, you can write
+# an IP address and netmask in separate columns to specify the set of hosts.
#
-# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
-# "ident", "peer", "pam", "ldap", "radius" or "cert". Note that
-# "password" sends passwords in clear text; "md5" is preferred since
-# it sends encrypted passwords.
+# METHOD can be "trust", "reject", "md5", "crypt", "password", "gss", "sspi",
+# "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords
+# in clear text; "md5" is preferred since it sends encrypted passwords.
#
-# OPTIONS are a set of options for the authentication in the format
-# NAME=VALUE. The available options depend on the different
-# authentication methods -- refer to the "Client Authentication"
-# section in the documentation for a list of which options are
-# available for which authentication methods.
+# OPTION is the ident map or the name of the PAM service, depending on METHOD.
#
-# Database and user names containing spaces, commas, quotes and other
-# special characters must be quoted. Quoting one of the keywords
-# "all", "sameuser", "samerole" or "replication" makes the name lose
-# its special character, and just match a database or username with
-# that name.
+# Database and user names containing spaces, commas, quotes and other special
+# characters must be quoted. Quoting one of the keywords "all", "sameuser" or
+# "samerole" makes the name lose its special character, and just match a
+# database or username with that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal. If you edit the file on a running system, you have
-# to SIGHUP the postmaster for the changes to take effect. You can
-# use "pg_ctl reload" to do that.
+# to SIGHUP the postmaster for the changes to take effect. You can use
+# "pg_ctl reload" to do that.
# Put your actual configuration here
# ----------------------------------
#
# If you want to allow non-local connections, you need to add more
-# "host" records. In that case you will also need to make PostgreSQL
-# listen on a non-local interface via the listen_addresses
-# configuration parameter, or via the -i or -h command line switches.
+# "host" records. In that case you will also need to make PostgreSQL listen
+# on a non-local interface via the listen_addresses configuration parameter,
+# or via the -i or -h command line switches.
+#
-# CAUTION: Configuring the system for local "trust" authentication
-# allows any local user to connect as any PostgreSQL user, including
-# the database superuser. If you do not trust all your local users,
-# use another authentication method.
+# TYPE DATABASE USER CIDR-ADDRESS METHOD
-# TYPE DATABASE USER ADDRESS METHOD
-
# "local" is for Unix domain socket connections only
-local all all trust
-# IPv4 local connections:
-host all all 127.0.0.1/32 trust
-# IPv6 local connections:
-host all all ::1/128 trust
-# Allow replication connections from localhost, by a user with the
-# replication privilege.
-#local replication gitlab-psql trust
-#host replication gitlab-psql 127.0.0.1/32 trust
-#host replication gitlab-psql ::1/128 trust
+local all all peer map=gitlab
+
+
+
- change mode from '0600' to '0644'
- restore selinux security context
* service[postgresql] action restart
- restart service service[postgresql]
* template[/var/opt/gitlab/postgresql/data/pg_ident.conf] action create
- update content in file /var/opt/gitlab/postgresql/data/pg_ident.conf from 297f46 to da3268
--- /var/opt/gitlab/postgresql/data/pg_ident.conf 2017-07-17 19:06:34.907725963 +0900
+++ /var/opt/gitlab/postgresql/data/.chef-pg_ident.conf20170717-24218-1ageinf 2017-07-17 19:06:58.449306378 +0900
@@ -40,4 +40,9 @@
# ----------------------------------
# MAPNAME SYSTEM-USERNAME PG-USERNAME
+gitlab git gitlab
+gitlab gitlab-ci gitlab_ci
+gitlab mattermost gitlab_mattermost
+# Default to a 1-1 mapping between system usernames and Postgres usernames
+gitlab /^(.*)$ \1
- change mode from '0600' to '0644'
- restore selinux security context
* service[postgresql] action restart
- restart service service[postgresql]
* directory[/opt/gitlab/sv/postgresql] action create (up to date)
* directory[/opt/gitlab/sv/postgresql/log] action create (up to date)
* directory[/opt/gitlab/sv/postgresql/log/main] action create (up to date)
* template[/opt/gitlab/sv/postgresql/run] action create (up to date)
* template[/opt/gitlab/sv/postgresql/log/run] action create (up to date)
* template[/var/log/gitlab/postgresql/config] action create (up to date)
* ruby_block[reload postgresql svlogd configuration] action nothing (skipped due to action :nothing)
* file[/opt/gitlab/sv/postgresql/down] action delete (up to date)
* directory[/opt/gitlab/sv/postgresql/control] action create (up to date)
* template[/opt/gitlab/sv/postgresql/control/t] action create (up to date)
* link[/opt/gitlab/init/postgresql] action create (up to date)
* link[/opt/gitlab/service/postgresql] action create (up to date)
* ruby_block[supervise_postgresql_sleep] action run (skipped due to not_if)
* service[postgresql] action nothing (skipped due to action :nothing)
Recipe: gitlab::postgresql-bin
* ruby_block[Link postgresql bin files to the correct version] action run (skipped due to only_if)
Recipe: gitlab::postgresql
* template[/opt/gitlab/etc/gitlab-psql-rc] action create (up to date)
* execute[create gitlab database user] action run
[execute] psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/opt/gitlab/postgresql/.s.PGSQL.5432"?
(skipped due to not_if)
* execute[create gitlabhq_production database] action run (skipped due to not_if)
* execute[create gitlab_replicator replication user] action run (skipped due to not_if)
* execute[enable pg_trgm extension] action nothing (skipped due to action :nothing)
Recipe: gitlab::database_migrations
* bash[migrate gitlab-rails database] action run (skipped due to not_if)
* bash[migrate gitlab-rails database] action run (skipped due to not_if)
Recipe: gitlab::logrotate_folders_and_configs
* directory[/var/opt/gitlab/logrotate] action create (up to date)
* directory[/var/opt/gitlab/logrotate/logrotate.d] action create (up to date)
* directory[/var/log/gitlab/logrotate] action create (up to date)
* template[/var/opt/gitlab/logrotate/logrotate.conf] action create (up to date)
* template[/var/opt/gitlab/logrotate/logrotate.d/nginx] action create (up to date)
* template[/var/opt/gitlab/logrotate/logrotate.d/unicorn] action create (up to date)
* template[/var/opt/gitlab/logrotate/logrotate.d/gitlab-rails] action create (up to date)
* template[/var/opt/gitlab/logrotate/logrotate.d/gitlab-shell] action create (up to date)
* template[/var/opt/gitlab/logrotate/logrotate.d/gitlab-workhorse] action create (up to date)
* template[/var/opt/gitlab/logrotate/logrotate.d/gitlab-pages] action create (up to date)
Recipe: gitlab::unicorn
* directory[/var/log/gitlab/unicorn] action create (up to date)
* directory[/opt/gitlab/var/unicorn] action create (up to date)
* directory[/var/opt/gitlab/gitlab-rails/sockets] action create (up to date)
* directory[/var/opt/gitlab/gitlab-rails/etc] action create (up to date)
* template[/var/opt/gitlab/gitlab-rails/etc/unicorn.rb] action create (up to date)
* directory[/opt/gitlab/sv/unicorn] action create (up to date)
* directory[/opt/gitlab/sv/unicorn/log] action create (up to date)
* directory[/opt/gitlab/sv/unicorn/log/main] action create (up to date)
* template[/opt/gitlab/sv/unicorn/run] action create (up to date)
* template[/opt/gitlab/sv/unicorn/log/run] action create (up to date)
* template[/var/log/gitlab/unicorn/config] action create (up to date)
* ruby_block[reload unicorn svlogd configuration] action nothing (skipped due to action :nothing)
* file[/opt/gitlab/sv/unicorn/down] action delete (up to date)
* directory[/opt/gitlab/sv/unicorn/control] action create (up to date)
* template[/opt/gitlab/sv/unicorn/control/t] action create (up to date)
* link[/opt/gitlab/init/unicorn] action create (up to date)
* link[/opt/gitlab/service/unicorn] action create (up to date)
* ruby_block[supervise_unicorn_sleep] action run (skipped due to not_if)
* service[unicorn] action nothing (skipped due to action :nothing)
* directory[create /etc/sysctl.d for net.core.somaxconn] action create (up to date)
* file[create /opt/gitlab/embedded/etc/90-omnibus-gitlab-net.core.somaxconn.conf net.core.somaxconn] action create (up to date)
* link[/etc/sysctl.d/90-omnibus-gitlab-net.core.somaxconn.conf] action create (up to date)
* file[delete /etc/sysctl.d/90-postgresql.conf net.core.somaxconn] action delete (skipped due to only_if)
* file[delete /etc/sysctl.d/90-unicorn.conf net.core.somaxconn] action delete (skipped due to only_if)
* file[delete /opt/gitlab/embedded/etc/90-omnibus-gitlab.conf net.core.somaxconn] action delete (skipped due to only_if)
* file[delete /etc/sysctl.d/90-omnibus-gitlab.conf net.core.somaxconn] action delete (skipped due to only_if)
* execute[load sysctl conf net.core.somaxconn] action nothing (skipped due to action :nothing)
Recipe: gitlab::sidekiq
* directory[/var/log/gitlab/sidekiq] action create (up to date)
* directory[/opt/gitlab/sv/sidekiq] action create (up to date)
* directory[/opt/gitlab/sv/sidekiq/log] action create (up to date)
* directory[/opt/gitlab/sv/sidekiq/log/main] action create (up to date)
* template[/opt/gitlab/sv/sidekiq/run] action create (up to date)
* template[/opt/gitlab/sv/sidekiq/log/run] action create (up to date)
* template[/var/log/gitlab/sidekiq/config] action create (up to date)
* ruby_block[reload sidekiq svlogd configuration] action nothing (skipped due to action :nothing)
* file[/opt/gitlab/sv/sidekiq/down] action delete (up to date)
* link[/opt/gitlab/init/sidekiq] action create (up to date)
* link[/opt/gitlab/service/sidekiq] action create (up to date)
* ruby_block[supervise_sidekiq_sleep] action run (skipped due to not_if)
* service[sidekiq] action nothing (skipped due to action :nothing)
Recipe: gitlab::gitaly_disable
* link[/opt/gitlab/service/gitaly] action delete (up to date)
* directory[/opt/gitlab/sv/gitaly] action delete (up to date)
Recipe: gitlab::gitlab-workhorse
* directory[/var/opt/gitlab/gitlab-workhorse] action create (up to date)
* directory[/var/log/gitlab/gitlab-workhorse] action create (up to date)
* directory[/opt/gitlab/etc/gitlab-workhorse] action create (up to date)
* directory[/opt/gitlab/etc/gitlab-workhorse/env] action create (up to date)
* file[/opt/gitlab/etc/gitlab-workhorse/env/PATH] action create (up to date)
* file[/opt/gitlab/etc/gitlab-workhorse/env/HOME] action create (up to date)
* directory[/opt/gitlab/sv/gitlab-workhorse] action create (up to date)
* directory[/opt/gitlab/sv/gitlab-workhorse/log] action create (up to date)
* directory[/opt/gitlab/sv/gitlab-workhorse/log/main] action create (up to date)
* template[/opt/gitlab/sv/gitlab-workhorse/run] action create (up to date)
* template[/opt/gitlab/sv/gitlab-workhorse/log/run] action create (up to date)
* template[/var/log/gitlab/gitlab-workhorse/config] action create (up to date)
* ruby_block[reload gitlab-workhorse svlogd configuration] action nothing (skipped due to action :nothing)
* file[/opt/gitlab/sv/gitlab-workhorse/down] action delete (up to date)
* link[/opt/gitlab/init/gitlab-workhorse] action create (up to date)
* link[/opt/gitlab/service/gitlab-workhorse] action create (up to date)
* ruby_block[supervise_gitlab-workhorse_sleep] action run (skipped due to not_if)
* service[gitlab-workhorse] action nothing (skipped due to action :nothing)
* file[/var/opt/gitlab/gitlab-workhorse/VERSION] action create (up to date)
Recipe: gitlab::mailroom_disable
* link[/opt/gitlab/service/mailroom] action delete (up to date)
* directory[/opt/gitlab/sv/mailroom] action delete (up to date)
Recipe: gitlab::nginx
* directory[/var/opt/gitlab/nginx] action create (up to date)
* directory[/var/opt/gitlab/nginx/conf] action create (up to date)
* directory[/var/log/gitlab/nginx] action create (up to date)
* link[/var/opt/gitlab/nginx/logs] action create (up to date)
* template[/var/opt/gitlab/nginx/conf/gitlab-http.conf] action create (up to date)
* template[/var/opt/gitlab/nginx/conf/gitlab-pages.conf] action delete (up to date)
* template[/var/opt/gitlab/nginx/conf/gitlab-registry.conf] action delete (up to date)
* template[/var/opt/gitlab/nginx/conf/gitlab-mattermost-http.conf] action delete (up to date)
* template[/var/opt/gitlab/nginx/conf/nginx-status.conf] action create (up to date)
* template[/var/opt/gitlab/nginx/conf/nginx.conf] action create (up to date)
* directory[/opt/gitlab/sv/nginx] action create (up to date)
* directory[/opt/gitlab/sv/nginx/log] action create (up to date)
* directory[/opt/gitlab/sv/nginx/log/main] action create (up to date)
* template[/opt/gitlab/sv/nginx/run] action create (up to date)
* template[/opt/gitlab/sv/nginx/log/run] action create (up to date)
* template[/var/log/gitlab/nginx/config] action create (up to date)
* ruby_block[reload nginx svlogd configuration] action nothing (skipped due to action :nothing)
* file[/opt/gitlab/sv/nginx/down] action delete (up to date)
* link[/opt/gitlab/init/nginx] action create (up to date)
* link[/opt/gitlab/service/nginx] action create (up to date)
* ruby_block[supervise_nginx_sleep] action run (skipped due to not_if)
* service[nginx] action nothing (skipped due to action :nothing)
Recipe: gitlab::remote-syslog_disable
* link[/opt/gitlab/service/remote-syslog] action delete (up to date)
* directory[/opt/gitlab/sv/remote-syslog] action delete (up to date)
Recipe: gitlab::logrotate
* directory[/opt/gitlab/sv/logrotate] action create (up to date)
* directory[/opt/gitlab/sv/logrotate/log] action create (up to date)
* directory[/opt/gitlab/sv/logrotate/log/main] action create (up to date)
* template[/opt/gitlab/sv/logrotate/run] action create (up to date)
* template[/opt/gitlab/sv/logrotate/log/run] action create (up to date)
* template[/var/log/gitlab/logrotate/config] action create (up to date)
* ruby_block[reload logrotate svlogd configuration] action nothing (skipped due to action :nothing)
* file[/opt/gitlab/sv/logrotate/down] action delete (up to date)
* directory[/opt/gitlab/sv/logrotate/control] action create (up to date)
* template[/opt/gitlab/sv/logrotate/control/t] action create (up to date)
* link[/opt/gitlab/init/logrotate] action create (up to date)
* link[/opt/gitlab/service/logrotate] action create (up to date)
* ruby_block[supervise_logrotate_sleep] action run (skipped due to not_if)
* service[logrotate] action nothing (skipped due to action :nothing)
Recipe: gitlab::mattermost_disable
* link[/opt/gitlab/service/mattermost] action delete (up to date)
* directory[/opt/gitlab/sv/mattermost] action delete (up to date)
Recipe: gitlab::gitlab-pages_disable
* link[/opt/gitlab/service/gitlab-pages] action delete (up to date)
* directory[/opt/gitlab/sv/gitlab-pages] action delete (up to date)
Recipe: gitlab::registry_disable
* link[/opt/gitlab/service/registry] action delete (up to date)
* directory[/opt/gitlab/sv/registry] action delete (up to date)
Recipe: gitlab::prometheus_disable
* link[/opt/gitlab/service/prometheus] action delete (up to date)
* directory[/opt/gitlab/sv/prometheus] action delete (up to date)
Recipe: gitlab::node-exporter_disable
* link[/opt/gitlab/service/node-exporter] action delete (up to date)
* directory[/opt/gitlab/sv/node-exporter] action delete (up to date)
Recipe: gitlab::default
* link[/opt/gitlab/service/gitlab-git-http-server] action delete (up to date)
* directory[/opt/gitlab/sv/gitlab-git-http-server] action delete (up to date)
Running handlers:
Running handlers complete
Chef Client finished, 9/311 resources updated in 13 seconds
Running reconfigure: OK
Database upgrade is complete, running analyze_new_cluster.sh
==== Upgrade has completed ====
Please verify everything is working and run the following if so
rm -rf /var/opt/gitlab/postgresql/data.9.2.18
Toggling deploy page:rm -f /opt/gitlab/embedded/service/gitlab-rails/public/index.html
Toggling deploy page: OK
Toggling services:ok: run: logrotate: (pid 24849) 0s
ok: run: sidekiq: (pid 24855) 1s
Toggling services: OK
8.16.9 -> 8.17.6
$ sudo yum update gitlab-ce-8.17.6-ce.0.el7.x86_64.rpm
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
gitlab-ce-8.17.6-ce.0.el7.x86_64.rpm を調べています: gitlab-ce-8.17.6-ce.0.el7.x86_64
次のリポジトリーへの更新として gitlab-ce-8.17.6-ce.0.el7.x86_64.rpm を設定します: gitlab-ce-8.16.9-ce.0.el7.x86_64
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:8.16.9-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:8.17.6-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
依存性を解決しました
=======================================================================================================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
=======================================================================================================================================================================================================
更新します:
gitlab-ce x86_64 8.17.6-ce.0.el7 /gitlab-ce-8.17.6-ce.0.el7.x86_64 798 M
トランザクションの要約
=======================================================================================================================================================================================================
更新 1 パッケージ
合計容量: 798 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1500290428_2017_07_17_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-8.17.6-ce.0.el7.x86_64 1/2
*. *.
*** ***
***** *****
.****** *******
******** ********
,,,,,,,,***********,,,,,,,,,
,,,,,,,,,,*********,,,,,,,,,,,
.,,,,,,,,,,,*******,,,,,,,,,,,,
,,,,,,,,*****,,,,,,,,,.
,,,,,,****,,,,,,
.,,,***,,,,
*,.
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ `/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
gitlab: Thank you for installing GitLab!
gitlab: To configure and start GitLab, RUN THE FOLLOWING COMMAND:
sudo gitlab-ctl reconfigure
gitlab: GitLab should be reachable at http://hogehoge:10080
gitlab: Otherwise configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
gitlab: And running reconfigure again.
gitlab:
gitlab: For a comprehensive list of configuration options please see the Omnibus GitLab readme
gitlab: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
gitlab:
整理中 : gitlab-ce-8.16.9-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitlab-workhorse: 1s, normally up
ok: down: logrotate: 0s, normally up
ok: down: nginx: 1s, normally up
ok: down: postgresql: 0s, normally up
ok: down: redis: 0s, normally up
ok: down: sidekiq: 1s, normally up
ok: down: unicorn: 0s, normally up
ok: run: postgresql: (pid 31011) 1s
ok: run: redis: (pid 31019) 0s
run: postgresql: (pid 31011) 1s; run: log: (pid 745) 3135061s
run: redis: (pid 31019) 0s; run: log: (pid 756) 3135061s
Reconfiguring GitLab to apply migrations
/sbin/init: オプション '--version' を認識できません
-.mount loaded active mounted /
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Restarting previously running GitLab services
ok: run: gitlab-workhorse: (pid 31680) 0s
ok: run: logrotate: (pid 31687) 0s
ok: run: nginx: (pid 31689) 0s
ok: run: postgresql: (pid 31541) 38s
ok: run: redis: (pid 31019) 49s
ok: run: sidekiq: (pid 31672) 1s
ok: run: unicorn: (pid 31695) 0s
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else. If you need to roll back to the previous version you can
use the database backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-8.17.6-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-8.16.9-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:8.17.6-ce.0.el7
完了しました!
8.17.6 -> 9.0.10
$ sudo yum update gitlab-ce-9.0.10-ce.0.el7.x86_64.rpm
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
gitlab-ce-9.0.10-ce.0.el7.x86_64.rpm を調べています: gitlab-ce-9.0.10-ce.0.el7.x86_64
次のリポジトリーへの更新として gitlab-ce-9.0.10-ce.0.el7.x86_64.rpm を設定します: gitlab-ce-8.17.6-ce.0.el7.x86_64
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:8.17.6-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:9.0.10-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
依存性を解決しました
=======================================================================================================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
=======================================================================================================================================================================================================
更新します:
gitlab-ce x86_64 9.0.10-ce.0.el7 /gitlab-ce-9.0.10-ce.0.el7.x86_64 852 M
トランザクションの要約
=======================================================================================================================================================================================================
更新 1 パッケージ
合計容量: 852 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1500291776_2017_07_17_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-9.0.10-ce.0.el7.x86_64 1/2
*. *.
*** ***
***** *****
.****** *******
******** ********
,,,,,,,,***********,,,,,,,,,
,,,,,,,,,,*********,,,,,,,,,,,
.,,,,,,,,,,,*******,,,,,,,,,,,,
,,,,,,,,*****,,,,,,,,,.
,,,,,,****,,,,,,
.,,,***,,,,
*,.
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ `/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
gitlab: Thank you for installing GitLab!
gitlab: To configure and start GitLab, RUN THE FOLLOWING COMMAND:
sudo gitlab-ctl reconfigure
gitlab: GitLab should be reachable at http://hogehoge:10080
gitlab: Otherwise configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
gitlab: And running reconfigure again.
gitlab:
gitlab: For a comprehensive list of configuration options please see the Omnibus GitLab readme
gitlab: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
gitlab:
整理中 : gitlab-ce-8.17.6-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitlab-workhorse: 1s, normally up
ok: down: logrotate: 0s, normally up
ok: down: nginx: 1s, normally up
ok: down: postgresql: 0s, normally up
ok: down: redis: 0s, normally up
ok: down: sidekiq: 1s, normally up
ok: down: unicorn: 0s, normally up
ok: run: postgresql: (pid 1462) 1s
ok: run: redis: (pid 1470) 0s
run: postgresql: (pid 1462) 1s; run: log: (pid 745) 3136413s
run: redis: (pid 1470) 0s; run: log: (pid 756) 3136413s
Reconfiguring GitLab to apply migrations
/sbin/init: オプション '--version' を認識できません
-.mount loaded active mounted /
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Ensuring PostgreSQL is updated:The latest version 9.6.1 is already running, nothing to do
Checking for an omnibus managed postgresql: OK
Checking if we already upgraded: OK
Ensuring PostgreSQL is updated: OK
Restarting previously running GitLab services
ok: run: gitlab-workhorse: (pid 2475) 1s
ok: run: logrotate: (pid 2538) 0s
ok: run: nginx: (pid 2487) 1s
ok: run: postgresql: (pid 2030) 69s
ok: run: redis: (pid 1470) 90s
ok: run: sidekiq: (pid 2431) 15s
ok: run: unicorn: (pid 2544) 0s
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else. If you need to roll back to the previous version you can
use the database backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-9.0.10-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-8.17.6-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:9.0.10-ce.0.el7
完了しました!
9.0.10 -> 9.1.7
$ sudo yum update gitlab-ce-9.1.7-ce.0.el7.x86_64.rpm
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
gitlab-ce-9.1.7-ce.0.el7.x86_64.rpm を調べています: gitlab-ce-9.1.7-ce.0.el7.x86_64
次のリポジトリーへの更新として gitlab-ce-9.1.7-ce.0.el7.x86_64.rpm を設定します: gitlab-ce-9.0.10-ce.0.el7.x86_64
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:9.0.10-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:9.1.7-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
依存性を解決しました
=======================================================================================================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
=======================================================================================================================================================================================================
更新します:
gitlab-ce x86_64 9.1.7-ce.0.el7 /gitlab-ce-9.1.7-ce.0.el7.x86_64 847 M
トランザクションの要約
=======================================================================================================================================================================================================
更新 1 パッケージ
合計容量: 847 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1500293395_2017_07_17_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-9.1.7-ce.0.el7.x86_64 1/2
*. *.
*** ***
***** *****
.****** *******
******** ********
,,,,,,,,***********,,,,,,,,,
,,,,,,,,,,*********,,,,,,,,,,,
.,,,,,,,,,,,*******,,,,,,,,,,,,
,,,,,,,,*****,,,,,,,,,.
,,,,,,****,,,,,,
.,,,***,,,,
*,.
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ `/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
gitlab: Thank you for installing GitLab!
gitlab: To configure and start GitLab, RUN THE FOLLOWING COMMAND:
sudo gitlab-ctl reconfigure
gitlab: GitLab should be reachable at http://hogehoge:10080
gitlab: Otherwise configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
gitlab: And running reconfigure again.
gitlab:
gitlab: For a comprehensive list of configuration options please see the Omnibus GitLab readme
gitlab: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
gitlab:
整理中 : gitlab-ce-9.0.10-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitaly: 1s, normally up
ok: down: gitlab-monitor: 0s, normally up
ok: down: gitlab-workhorse: 0s, normally up
ok: down: logrotate: 1s, normally up
ok: down: nginx: 0s, normally up
ok: down: node-exporter: 1s, normally up
ok: down: postgres-exporter: 0s, normally up
ok: down: postgresql: 1s, normally up
ok: down: prometheus: 0s, normally up
ok: down: redis: 0s, normally up
ok: down: redis-exporter: 1s, normally up
ok: down: sidekiq: 1s, normally up
ok: down: unicorn: 0s, normally up
ok: run: postgresql: (pid 5799) 1s
ok: run: redis: (pid 5807) 0s
run: postgresql: (pid 5799) 1s; run: log: (pid 745) 3138037s
run: redis: (pid 5807) 0s; run: log: (pid 756) 3138037s
Reconfiguring GitLab to apply migrations
/sbin/init: オプション '--version' を認識できません
-.mount loaded active mounted /
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Ensuring PostgreSQL is updated:The latest version 9.6.1 is already running, nothing to do
Checking for an omnibus managed postgresql: OK
Checking if we already upgraded: OK
Ensuring PostgreSQL is updated: OK
Restarting previously running GitLab services
ok: run: gitaly: (pid 6458) 2s
ok: run: gitlab-monitor: (pid 6497) 0s
ok: run: gitlab-workhorse: (pid 6468) 1s
ok: run: logrotate: (pid 6501) 1s
ok: run: nginx: (pid 6507) 0s
ok: run: node-exporter: (pid 6513) 1s
ok: run: postgres-exporter: (pid 6518) 0s
ok: run: postgresql: (pid 6346) 43s
ok: run: prometheus: (pid 6482) 3s
ok: run: redis: (pid 5807) 55s
ok: run: redis-exporter: (pid 6528) 1s
ok: run: sidekiq: (pid 6533) 0s
ok: run: unicorn: (pid 6536) 0s
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else. If you need to roll back to the previous version you can
use the database backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-9.1.7-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-9.0.10-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:9.1.7-ce.0.el7
完了しました!
9.1.7 -> 9.2.7
2017.7.17
$ sudo yum update gitlab-ce-9.2.7-ce.0.el7.x86_64.rpm
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
gitlab-ce-9.2.7-ce.0.el7.x86_64.rpm を調べています: gitlab-ce-9.2.7-ce.0.el7.x86_64
次のリポジトリーへの更新として gitlab-ce-9.2.7-ce.0.el7.x86_64.rpm を設定します: gitlab-ce-9.1.7-ce.0.el7.x86_64
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:9.1.7-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:9.2.7-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
依存性を解決しました
=======================================================================================================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
=======================================================================================================================================================================================================
更新します:
gitlab-ce x86_64 9.2.7-ce.0.el7 /gitlab-ce-9.2.7-ce.0.el7.x86_64 910 M
トランザクションの要約
=======================================================================================================================================================================================================
更新 1 パッケージ
合計容量: 910 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1500295195_2017_07_17_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-9.2.7-ce.0.el7.x86_64 1/2
*. *.
*** ***
***** *****
.****** *******
******** ********
,,,,,,,,***********,,,,,,,,,
,,,,,,,,,,*********,,,,,,,,,,,
.,,,,,,,,,,,*******,,,,,,,,,,,,
,,,,,,,,*****,,,,,,,,,.
,,,,,,****,,,,,,
.,,,***,,,,
*,.
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ `/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
gitlab: Thank you for installing GitLab!
gitlab: To configure and start GitLab, RUN THE FOLLOWING COMMAND:
sudo gitlab-ctl reconfigure
gitlab: GitLab should be reachable at http://hogehoge:10080
gitlab: Otherwise configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
gitlab: And running reconfigure again.
gitlab:
gitlab: For a comprehensive list of configuration options please see the Omnibus GitLab readme
gitlab: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
gitlab:
整理中 : gitlab-ce-9.1.7-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitaly: 1s, normally up
ok: down: gitlab-monitor: 0s, normally up
ok: down: gitlab-workhorse: 1s, normally up
ok: down: logrotate: 0s, normally up
ok: down: nginx: 0s, normally up
ok: down: node-exporter: 1s, normally up
ok: down: postgres-exporter: 0s, normally up
ok: down: postgresql: 1s, normally up
ok: down: prometheus: 0s, normally up
ok: down: redis: 0s, normally up
ok: down: redis-exporter: 1s, normally up
ok: down: sidekiq: 1s, normally up
ok: down: unicorn: 0s, normally up
ok: run: postgresql: (pid 10203) 1s
ok: run: redis: (pid 10211) 0s
run: postgresql: (pid 10203) 1s; run: log: (pid 745) 3139840s
run: redis: (pid 10211) 0s; run: log: (pid 756) 3139840s
Reconfiguring GitLab to apply migrations
/sbin/init: オプション '--version' を認識できません
-.mount loaded active mounted /
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Ensuring PostgreSQL is updated:The latest version 9.6.1 is already running, nothing to do
Checking for an omnibus managed postgresql: OK
Checking if we already upgraded: OK
Ensuring PostgreSQL is updated: OK
Restarting previously running GitLab services
ok: run: gitaly: (pid 10907) 0s
ok: run: gitlab-monitor: (pid 10898) 1s
ok: run: gitlab-workhorse: (pid 10872) 2s
ok: run: logrotate: (pid 10914) 1s
ok: run: nginx: (pid 10920) 0s
ok: run: node-exporter: (pid 10926) 0s
ok: run: postgres-exporter: (pid 10931) 1s
ok: run: postgresql: (pid 10203) 58s
ok: run: prometheus: (pid 10885) 3s
ok: run: redis: (pid 10211) 57s
ok: run: redis-exporter: (pid 10940) 0s
ok: run: sidekiq: (pid 10946) 1s
ok: run: unicorn: (pid 10949) 0s
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else. If you need to roll back to the previous version you can
use the database backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-9.2.7-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-9.1.7-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:9.2.7-ce.0.el7
完了しました!
9.2.7 -> 9.3.11
2017.9.8
$ sudo yum update gitlab-ce-9.3.11-ce.0.el7.x86_64.rpm
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
gitlab-ce-9.3.11-ce.0.el7.x86_64.rpm を調べています: gitlab-ce-9.3.11-ce.0.el7.x86_64
次のリポジトリーへの更新として gitlab-ce-9.3.11-ce.0.el7.x86_64.rpm を設定します: gitlab-ce-9.2.7-ce.0.el7.x86_64
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:9.2.7-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:9.3.11-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
adobe-linux-x86_64 | 2.9 kB 00:00:00
base/7/x86_64 | 3.6 kB 00:00:00
epel/x86_64/metalink | 5.5 kB 00:00:00
epel/x86_64/updateinfo | 817 kB 00:00:02
epel/x86_64/primary_db | 4.8 MB 00:00:18
extras/7/x86_64 | 3.4 kB 00:00:00
gitlab_gitlab-ce/x86_64/signature | 836 B 00:00:00
gitlab_gitlab-ce/x86_64/signature | 1.0 kB 00:00:00 !!!
https://packages.gitlab.com/gitlab/gitlab-ce/el/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for gitlab_gitlab-ce
他のミラーを試します。
gitlab_gitlab-ce-source/signature | 836 B 00:00:00
gitlab_gitlab-ce-source/signature | 951 B 00:00:00 !!!
https://packages.gitlab.com/gitlab/gitlab-ce/el/7/SRPMS/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for gitlab_gitlab-ce-source
他のミラーを試します。
google-chrome | 951 B 00:00:00
google-chrome/primary | 1.9 kB 00:00:00
updates/7/x86_64 | 3.4 kB 00:00:00
依存性を解決しました
===================================================================================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
===================================================================================================================================================================================
更新します:
gitlab-ce x86_64 9.3.11-ce.0.el7 /gitlab-ce-9.3.11-ce.0.el7.x86_64 1.0 G
トランザクションの要約
===================================================================================================================================================================================
更新 1 パッケージ
合計容量: 1.0 G
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1504875602_2017_09_08_9.2.7_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-9.3.11-ce.0.el7.x86_64 1/2
*. *.
*** ***
***** *****
.****** *******
******** ********
,,,,,,,,***********,,,,,,,,,
,,,,,,,,,,*********,,,,,,,,,,,
.,,,,,,,,,,,*******,,,,,,,,,,,,
,,,,,,,,*****,,,,,,,,,.
,,,,,,****,,,,,,
.,,,***,,,,
*,.
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ `/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
gitlab: Thank you for installing GitLab!
gitlab: To configure and start GitLab, RUN THE FOLLOWING COMMAND:
sudo gitlab-ctl reconfigure
gitlab: GitLab should be reachable at http://hogehoge:10080
gitlab: Otherwise configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
gitlab: And running reconfigure again.
gitlab:
gitlab: For a comprehensive list of configuration options please see the Omnibus GitLab readme
gitlab: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
gitlab:
整理中 : gitlab-ce-9.2.7-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitaly: 0s, normally up
ok: down: gitlab-monitor: 0s, normally up
ok: down: gitlab-workhorse: 1s, normally up
ok: down: logrotate: 0s, normally up
ok: down: nginx: 1s, normally up
ok: down: node-exporter: 0s, normally up
ok: down: postgres-exporter: 1s, normally up
ok: down: postgresql: 0s, normally up
ok: down: prometheus: 0s, normally up
ok: down: redis: 0s, normally up
ok: down: redis-exporter: 0s, normally up
ok: down: sidekiq: 0s, normally up
ok: down: unicorn: 1s, normally up
ok: run: postgresql: (pid 26701) 0s
ok: run: redis: (pid 26709) 0s
run: postgresql: (pid 26701) 0s; run: log: (pid 745) 7720253s
run: redis: (pid 26709) 0s; run: log: (pid 756) 7720253s
Reconfiguring GitLab to apply migrations
/sbin/init: オプション '--version' を認識できません
-.mount loaded active mounted /
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Ensuring PostgreSQL is updated:The latest version 9.6.3 is already running, nothing to do
Checking for an omnibus managed postgresql: OK
Checking if we already upgraded: OK
Ensuring PostgreSQL is updated: OK
Restarting previously running GitLab services
ok: run: gitaly: (pid 27459) 2s
ok: run: gitlab-monitor: (pid 27504) 1s
ok: run: gitlab-workhorse: (pid 27469) 2s
ok: run: logrotate: (pid 27516) 0s
ok: run: nginx: (pid 27522) 1s
ok: run: node-exporter: (pid 27528) 0s
ok: run: postgres-exporter: (pid 27533) 1s
ok: run: postgresql: (pid 26701) 60s
ok: run: prometheus: (pid 27482) 3s
ok: run: redis: (pid 26709) 60s
ok: run: redis-exporter: (pid 27542) 0s
ok: run: sidekiq: (pid 27548) 0s
ok: run: unicorn: (pid 27555) 0s
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else. If you need to roll back to the previous version you can
use the database backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-9.3.11-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-9.2.7-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:9.3.11-ce.0.el7
完了しました!
9.3.11 -> 9.4.6
2017.9.8
$ sudo yum update gitlab-ce-9.4.6-ce.0.el7.x86_64.rpm
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
gitlab-ce-9.4.6-ce.0.el7.x86_64.rpm を調べています: gitlab-ce-9.4.6-ce.0.el7.x86_64
次のリポジトリーへの更新として gitlab-ce-9.4.6-ce.0.el7.x86_64.rpm を設定します: gitlab-ce-9.3.11-ce.0.el7.x86_64
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:9.3.11-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:9.4.6-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
gitlab_gitlab-ce/x86_64/signature | 836 B 00:00:00
gitlab_gitlab-ce/x86_64/signature | 1.0 kB 00:00:00 !!!
https://packages.gitlab.com/gitlab/gitlab-ce/el/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for gitlab_gitlab-ce
他のミラーを試します。
gitlab_gitlab-ce-source/signature | 836 B 00:00:00
gitlab_gitlab-ce-source/signature | 951 B 00:00:00 !!!
https://packages.gitlab.com/gitlab/gitlab-ce/el/7/SRPMS/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for gitlab_gitlab-ce-source
他のミラーを試します。
依存性を解決しました
========================================================================================================================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
========================================================================================================================================================================================================================
更新します:
gitlab-ce x86_64 9.4.6-ce.0.el7 /gitlab-ce-9.4.6-ce.0.el7.x86_64 1.0 G
トランザクションの要約
========================================================================================================================================================================================================================
更新 1 パッケージ
合計容量: 1.0 G
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1504876371_2017_09_08_9.3.11_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-9.4.6-ce.0.el7.x86_64 1/2
*. *.
*** ***
***** *****
.****** *******
******** ********
,,,,,,,,***********,,,,,,,,,
,,,,,,,,,,*********,,,,,,,,,,,
.,,,,,,,,,,,*******,,,,,,,,,,,,
,,,,,,,,*****,,,,,,,,,.
,,,,,,****,,,,,,
.,,,***,,,,
*,.
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ `/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
gitlab: Thank you for installing GitLab!
gitlab: To configure and start GitLab, RUN THE FOLLOWING COMMAND:
sudo gitlab-ctl reconfigure
gitlab: GitLab should be reachable at http://hogehoge:10080
gitlab: Otherwise configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
gitlab: And running reconfigure again.
gitlab:
gitlab: For a comprehensive list of configuration options please see the Omnibus GitLab readme
gitlab: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
gitlab:
整理中 : gitlab-ce-9.3.11-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitaly: 1s, normally up
ok: down: gitlab-monitor: 0s, normally up
ok: down: gitlab-workhorse: 0s, normally up
ok: down: logrotate: 1s, normally up
ok: down: nginx: 0s, normally up
ok: down: node-exporter: 1s, normally up
ok: down: postgres-exporter: 0s, normally up
ok: down: postgresql: 1s, normally up
ok: down: prometheus: 0s, normally up
ok: down: redis: 0s, normally up
ok: down: redis-exporter: 1s, normally up
ok: down: sidekiq: 1s, normally up
ok: down: unicorn: 0s, normally up
ok: run: postgresql: (pid 29560) 1s
ok: run: redis: (pid 29568) 0s
run: postgresql: (pid 29560) 1s; run: log: (pid 745) 7721022s
run: redis: (pid 29568) 0s; run: log: (pid 756) 7721022s
Reconfiguring GitLab to apply migrations
/sbin/init: オプション '--version' を認識できません
-.mount loaded active mounted /
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Checking for an omnibus managed postgresql: OK
Checking if we already upgraded: OK
The latest version 9.6.3 is already running, nothing to do
Ensuring PostgreSQL is updated: OK
Restarting previously running GitLab services
ok: run: gitaly: (pid 30268) 2s
ok: run: gitlab-monitor: (pid 30310) 0s
ok: run: gitlab-workhorse: (pid 30279) 2s
ok: run: logrotate: (pid 30314) 1s
ok: run: nginx: (pid 30320) 0s
ok: run: node-exporter: (pid 30326) 0s
ok: run: postgres-exporter: (pid 30336) 1s
ok: run: postgresql: (pid 29560) 63s
ok: run: prometheus: (pid 30292) 3s
ok: run: redis: (pid 29568) 62s
ok: run: redis-exporter: (pid 30345) 0s
ok: run: sidekiq: (pid 30350) 1s
ok: run: unicorn: (pid 30358) 0s
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else. If you need to roll back to the previous version you can
use the database backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-9.4.6-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-9.3.11-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:9.4.6-ce.0.el7
完了しました!
9.4.6 -> 9.5.5
2017.9.23
$ sudo yum update gitlab-ce-9.5.5-ce.0.el7.x86_64.rpm
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
gitlab-ce-9.5.5-ce.0.el7.x86_64.rpm を調べています: gitlab-ce-9.5.5-ce.0.el7.x86_64
次のリポジトリーへの更新として gitlab-ce-9.5.5-ce.0.el7.x86_64.rpm を設定します: gitlab-ce-9.4.6-ce.0.el7.x86_64
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:9.4.6-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:9.5.5-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
adobe-linux-x86_64 | 2.9 kB 00:00:00
adobe-linux-x86_64/primary_db | 2.7 kB 00:00:00
base/7/x86_64 | 3.6 kB 00:00:00
base/7/x86_64/group_gz | 156 kB 00:00:00
base/7/x86_64/primary_db | 5.7 MB 00:00:02
epel/x86_64/metalink | 5.6 kB 00:00:00
epel/x86_64 | 4.3 kB 00:00:00
epel/x86_64/updateinfo | 830 kB 00:00:01
epel/x86_64/primary_db | 4.8 MB 00:00:07
extras/7/x86_64 | 3.4 kB 00:00:00
extras/7/x86_64/primary_db | 112 kB 00:00:00
gitlab_gitlab-ce/x86_64/signature | 836 B 00:00:00
gitlab_gitlab-ce/x86_64/signature | 1.0 kB 00:00:00 !!!
https://packages.gitlab.com/gitlab/gitlab-ce/el/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for gitlab_gitlab-ce
他のミラーを試します。
gitlab_gitlab-ce-source/signature | 836 B 00:00:00
gitlab_gitlab-ce-source/signature | 951 B 00:00:00 !!!
https://packages.gitlab.com/gitlab/gitlab-ce/el/7/SRPMS/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for gitlab_gitlab-ce-source
他のミラーを試します。
google-chrome | 951 B 00:00:00
google-chrome/primary | 2.1 kB 00:00:00
updates/7/x86_64 | 3.4 kB 00:00:00
updates/7/x86_64/primary_db | 2.9 MB 00:00:02
依存性を解決しました
==========================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
==========================================================================================================================
更新します:
gitlab-ce x86_64 9.5.5-ce.0.el7 /gitlab-ce-9.5.5-ce.0.el7.x86_64 1.1 G
トランザクションの要約
==========================================================================================================================
更新 1 パッケージ
合計容量: 1.1 G
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1506125953_2017_09_23_9.4.6_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-9.5.5-ce.0.el7.x86_64 1/2
*. *.
*** ***
***** *****
.****** *******
******** ********
,,,,,,,,***********,,,,,,,,,
,,,,,,,,,,*********,,,,,,,,,,,
.,,,,,,,,,,,*******,,,,,,,,,,,,
,,,,,,,,*****,,,,,,,,,.
,,,,,,****,,,,,,
.,,,***,,,,
*,.
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ `/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
gitlab: Thank you for installing GitLab!
gitlab: To configure and start GitLab, RUN THE FOLLOWING COMMAND:
sudo gitlab-ctl reconfigure
gitlab: GitLab should be reachable at http://hogehoge:10080
gitlab: Otherwise configure GitLab for your system by editing /etc/gitlab/gitlab.rb file
gitlab: And running reconfigure again.
gitlab:
gitlab: For a comprehensive list of configuration options please see the Omnibus GitLab readme
gitlab: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
gitlab:
整理中 : gitlab-ce-9.4.6-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitaly: 1s, normally up
ok: down: gitlab-monitor: 0s, normally up
ok: down: gitlab-workhorse: 0s, normally up
ok: down: logrotate: 1s, normally up
ok: down: nginx: 0s, normally up
ok: down: node-exporter: 1s, normally up
ok: down: postgres-exporter: 0s, normally up
ok: down: postgresql: 1s, normally up
ok: down: prometheus: 0s, normally up
ok: down: redis: 0s, normally up
ok: down: redis-exporter: 1s, normally up
ok: down: sidekiq: 1s, normally up
ok: down: unicorn: 0s, normally up
ok: run: postgresql: (pid 17716) 0s
ok: run: redis: (pid 17724) 1s
run: postgresql: (pid 17716) 1s; run: log: (pid 745) 8970611s
run: redis: (pid 17724) 1s; run: log: (pid 756) 8970611s
Reconfiguring GitLab to apply migrations
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Checking for an omnibus managed postgresql: OK
Checking if we already upgraded: OK
The latest version 9.6.3 is already running, nothing to do
Ensuring PostgreSQL is updated: OK
Restarting previously running GitLab services
ok: run: gitaly: (pid 18384) 2s
ok: run: gitlab-monitor: (pid 18417) 1s
ok: run: gitlab-workhorse: (pid 18405) 1s
ok: run: logrotate: (pid 18433) 0s
ok: run: nginx: (pid 18435) 0s
ok: run: node-exporter: (pid 18437) 0s
ok: run: postgres-exporter: (pid 18452) 0s
ok: run: postgresql: (pid 17716) 63s
ok: run: prometheus: (pid 18455) 0s
ok: run: redis: (pid 17724) 63s
ok: run: redis-exporter: (pid 18469) 1s
ok: run: sidekiq: (pid 18509) 0s
ok: run: unicorn: (pid 18516) 0s
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else. If you need to roll back to the previous version you can
use the database backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-9.5.5-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-9.4.6-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:9.5.5-ce.0.el7
完了しました!
9.5.5 -> 10.0.0
2017.9.23
$ sudo yum update gitlab-ce-10.0.0-ce.0.el7.x86_64.rpm
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
gitlab-ce-10.0.0-ce.0.el7.x86_64.rpm を調べています: gitlab-ce-10.0.0-ce.0.el7.x86_64
次のリポジトリーへの更新として gitlab-ce-10.0.0-ce.0.el7.x86_64.rpm を設定します: gitlab-ce-9.5.5-ce.0.el7.x86_64
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:9.5.5-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:10.0.0-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
gitlab_gitlab-ce/x86_64/signature | 836 B 00:00:00
gitlab_gitlab-ce/x86_64/signature | 1.0 kB 00:00:00 !!!
https://packages.gitlab.com/gitlab/gitlab-ce/el/7/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for gitlab_gitlab-ce
他のミラーを試します。
gitlab_gitlab-ce-source/signature | 836 B 00:00:00
gitlab_gitlab-ce-source/signature | 951 B 00:00:00 !!!
https://packages.gitlab.com/gitlab/gitlab-ce/el/7/SRPMS/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for gitlab_gitlab-ce-source
他のミラーを試します。
依存性を解決しました
==========================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
==========================================================================================================================
更新します:
gitlab-ce x86_64 10.0.0-ce.0.el7 /gitlab-ce-10.0.0-ce.0.el7.x86_64 1.0 G
トランザクションの要約
==========================================================================================================================
更新 1 パッケージ
合計容量: 1.0 G
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1506126257_2017_09_23_9.5.5_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-10.0.0-ce.0.el7.x86_64 1/2
整理中 : gitlab-ce-9.5.5-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitaly: 0s, normally up
ok: down: gitlab-monitor: 1s, normally up
ok: down: gitlab-workhorse: 0s, normally up
ok: down: logrotate: 0s, normally up
ok: down: nginx: 1s, normally up
ok: down: node-exporter: 0s, normally up
ok: down: postgres-exporter: 1s, normally up
ok: down: postgresql: 0s, normally up
ok: down: prometheus: 0s, normally up
ok: down: redis: 0s, normally up
ok: down: redis-exporter: 0s, normally up
ok: down: sidekiq: 0s, normally up
ok: down: unicorn: 1s, normally up
ok: run: postgresql: (pid 19364) 0s
ok: run: redis: (pid 19372) 0s
run: postgresql: (pid 19364) 0s; run: log: (pid 745) 8970909s
run: redis: (pid 19372) 0s; run: log: (pid 756) 8970909s
Reconfiguring GitLab to apply migrations
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Checking for an omnibus managed postgresql: OK
Checking if we already upgraded: NOT OK
Checking for a newer version of PostgreSQL to install: NOT OK
No new version of PostgreSQL installed, nothing to upgrade to
Ensuring PostgreSQL is updated: OK
Restarting previously running GitLab services
ok: run: gitaly: (pid 20041) 1s
ok: run: gitlab-monitor: (pid 20050) 0s
ok: run: gitlab-workhorse: (pid 20025) 2s
ok: run: logrotate: (pid 20053) 0s
ok: run: nginx: (pid 20055) 0s
ok: run: node-exporter: (pid 20059) 0s
ok: run: postgres-exporter: (pid 20063) 0s
ok: run: postgresql: (pid 19364) 65s
ok: run: prometheus: (pid 20075) 0s
ok: run: redis: (pid 19372) 65s
ok: run: redis-exporter: (pid 20080) 0s
ok: run: sidekiq: (pid 20082) 0s
ok: run: unicorn: (pid 20086) 0s
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ \`/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else.
If you need to roll back to the previous version you can use the database
backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-10.0.0-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-9.5.5-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:10.0.0-ce.0.el7
完了しました!
10.0.0 -> 10.0.2
2017.9.29
curl
$ curl -s https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh | sudo bash
update
$ sudo yum update gitlab-ce
$ sudo yum update gitlab-ce
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
Loading mirror speeds from cached hostfile
* base: ftp.iij.ad.jp
* epel: ftp.riken.jp
* extras: ftp.iij.ad.jp
* updates: ftp.iij.ad.jp
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:10.0.0-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:10.0.2-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
依存性を解決しました
==============================================================================================================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
==============================================================================================================================================================================================================
更新します:
gitlab-ce x86_64 10.0.2-ce.0.el7 gitlab_gitlab-ce 343 M
トランザクションの要約
==============================================================================================================================================================================================================
更新 1 パッケージ
総ダウンロード容量: 343 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for gitlab_gitlab-ce
警告: /var/cache/yum/x86_64/7/gitlab_gitlab-ce/packages/gitlab-ce-10.0.2-ce.0.el7.x86_64.rpm: ヘッダー V4 RSA/SHA1 Signature、鍵 ID f27eab47: NOKEY======================== ] 21 MB/s | 340 MB 00:00:00 ETA
gitlab-ce-10.0.2-ce.0.el7.x86_64.rpm の公開鍵がインストールされていません
gitlab-ce-10.0.2-ce.0.el7.x86_64.rpm | 343 MB 00:00:22
https://packages.gitlab.com/gitlab/gitlab-ce/gpgkey から鍵を取得中です。
Importing GPG key 0xE15E78F4:
Userid : "GitLab B.V. (package repository signing key) <packages@gitlab.com>"
Fingerprint: 1a4c 919d b987 d435 9396 38b9 1421 9a96 e15e 78f4
From : https://packages.gitlab.com/gitlab/gitlab-ce/gpgkey
上記の処理を行います。よろしいでしょうか？ [y/N]y
https://packages.gitlab.com/gitlab/gitlab-ce/gpgkey/gitlab-gitlab-ce-3D645A26AB9FBD22.pub.gpg から鍵を取得中です。
Importing GPG key 0xF27EAB47:
Userid : "GitLab, Inc. <support@gitlab.com>"
Fingerprint: dbef 8977 4ddb 9eb3 7d9f c3a0 3cfc f9ba f27e ab47
From : https://packages.gitlab.com/gitlab/gitlab-ce/gpgkey/gitlab-gitlab-ce-3D645A26AB9FBD22.pub.gpg
上記の処理を行います。よろしいでしょうか？ [y/N]y
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1506687616_2017_09_29_10.0.0_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-10.0.2-ce.0.el7.x86_64 1/2
整理中 : gitlab-ce-10.0.0-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitaly: 0s, normally up
ok: down: gitlab-monitor: 1s, normally up
ok: down: gitlab-workhorse: 0s, normally up
ok: down: logrotate: 1s, normally up
ok: down: nginx: 0s, normally up
ok: down: node-exporter: 0s, normally up
ok: down: postgres-exporter: 1s, normally up
ok: down: postgresql: 0s, normally up
ok: down: prometheus: 1s, normally up
ok: down: redis: 0s, normally up
ok: down: redis-exporter: 1s, normally up
ok: down: sidekiq: 0s, normally up
ok: down: unicorn: 1s, normally up
ok: run: postgresql: (pid 29628) 0s
ok: run: redis: (pid 29636) 1s
run: postgresql: (pid 29628) 1s; run: log: (pid 745) 9532270s
run: redis: (pid 29636) 1s; run: log: (pid 756) 9532270s
Reconfiguring GitLab to apply migrations
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Checking for an omnibus managed postgresql: OK
Checking for a newer version of PostgreSQL to install
No new version of PostgreSQL installed, nothing to upgrade to
Ensuring PostgreSQL is updated: OK
Restarting previously running GitLab services
ok: run: gitaly: (pid 30276) 0s
ok: run: gitlab-monitor: (pid 30285) 0s
ok: run: gitlab-workhorse: (pid 30259) 1s
ok: run: logrotate: (pid 30288) 0s
ok: run: nginx: (pid 30290) 1s
ok: run: node-exporter: (pid 30311) 0s
ok: run: postgres-exporter: (pid 30313) 0s
ok: run: postgresql: (pid 29628) 51s
ok: run: prometheus: (pid 30316) 0s
ok: run: redis: (pid 29636) 51s
ok: run: redis-exporter: (pid 30319) 0s
ok: run: sidekiq: (pid 30321) 0s
ok: run: unicorn: (pid 30345) 0s
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ \`/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else.
If you need to roll back to the previous version you can use the database
backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-10.0.2-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-10.0.0-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:10.0.2-ce.0.el7
完了しました!
10.0.2 -> 10.0.3
2017.10.11
$ sudo yum update gitlab-ce
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
adobe-linux-x86_64 | 2.9 kB 00:00:00
base | 3.6 kB 00:00:00
epel/x86_64/metalink | 6.5 kB 00:00:00
epel | 4.3 kB 00:00:00
extras | 3.4 kB 00:00:00
gitlab_gitlab-ce/x86_64/signature | 836 B 00:00:00
gitlab_gitlab-ce/x86_64/signature | 1.0 kB 00:00:00 !!!
gitlab_gitlab-ce-source/signature | 836 B 00:00:00
gitlab_gitlab-ce-source/signature | 951 B 00:00:00 !!!
google-chrome | 951 B 00:00:00
updates | 3.4 kB 00:00:00
(1/5): epel/x86_64/updateinfo | 834 kB 00:00:00
(2/5): epel/x86_64/primary_db | 4.8 MB 00:00:00
(3/5): adobe-linux-x86_64/primary_db | 2.7 kB 00:00:00
(4/5): extras/7/x86_64/primary_db | 110 kB 00:00:01
(5/5): updates/7/x86_64/primary_db | 2.7 MB 00:00:02
(1/2): google-chrome/primary | 2.1 kB 00:00:00
(2/2): gitlab_gitlab-ce/x86_64/primary | 943 kB 00:00:01
Determining fastest mirrors
* base: ftp.iij.ad.jp
* epel: ftp.riken.jp
* extras: ftp.iij.ad.jp
* updates: ftp.iij.ad.jp
gitlab_gitlab-ce 301/301
google-chrome 3/3
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:10.0.2-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:10.0.3-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
依存性を解決しました
==========================================================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
==========================================================================================================================================================
更新します:
gitlab-ce x86_64 10.0.3-ce.0.el7 gitlab_gitlab-ce 343 M
トランザクションの要約
==========================================================================================================================================================
更新 1 パッケージ
総ダウンロード容量: 343 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for gitlab_gitlab-ce
gitlab-ce-10.0.3-ce.0.el7.x86_64.rpm | 343 MB 00:00:19
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1507719174_2017_10_11_10.0.2_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-10.0.3-ce.0.el7.x86_64 1/2
整理中 : gitlab-ce-10.0.2-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitaly: 0s, normally up
ok: down: gitlab-monitor: 0s, normally up
ok: down: gitlab-workhorse: 1s, normally up
ok: down: logrotate: 0s, normally up
ok: down: nginx: 1s, normally up
ok: down: node-exporter: 0s, normally up
ok: down: postgres-exporter: 1s, normally up
ok: down: postgresql: 0s, normally up
ok: down: prometheus: 0s, normally up
ok: down: redis: 0s, normally up
ok: down: redis-exporter: 0s, normally up
ok: down: sidekiq: 0s, normally up
ok: down: unicorn: 1s, normally up
ok: run: postgresql: (pid 12898) 0s
ok: run: redis: (pid 12906) 0s
run: postgresql: (pid 12898) 0s; run: log: (pid 745) 10563827s
run: redis: (pid 12906) 0s; run: log: (pid 756) 10563827s
Reconfiguring GitLab to apply migrations
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Checking for an omnibus managed postgresql: OK
Checking for a newer version of PostgreSQL to install
No new version of PostgreSQL installed, nothing to upgrade to
Ensuring PostgreSQL is updated: OK
Restarting previously running GitLab services
ok: run: gitaly: (pid 13554) 0s
ok: run: gitlab-monitor: (pid 13563) 0s
ok: run: gitlab-workhorse: (pid 13538) 1s
ok: run: logrotate: (pid 13566) 0s
ok: run: nginx: (pid 13568) 0s
ok: run: node-exporter: (pid 13570) 0s
ok: run: postgres-exporter: (pid 13572) 0s
ok: run: postgresql: (pid 12898) 51s
ok: run: prometheus: (pid 13579) 1s
ok: run: redis: (pid 12906) 52s
ok: run: redis-exporter: (pid 13610) 0s
ok: run: sidekiq: (pid 13620) 0s
ok: run: unicorn: (pid 13662) 0s
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ \`/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else.
If you need to roll back to the previous version you can use the database
backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-10.0.3-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-10.0.2-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:10.0.3-ce.0.el7
完了しました!
10.0.3 -> 10.0.4
2017.10.21
$ sudo yum update gitlab-ce
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
adobe-linux-x86_64 | 2.9 kB 00:00:00
base | 3.6 kB 00:00:00
epel/x86_64/metalink | 7.5 kB 00:00:00
epel | 4.3 kB 00:00:00
extras | 3.4 kB 00:00:00
gitlab_gitlab-ce/x86_64/signature | 836 B 00:00:00
gitlab_gitlab-ce/x86_64/signature | 1.0 kB 00:00:00 !!!
gitlab_gitlab-ce-source/signature | 836 B 00:00:00
gitlab_gitlab-ce-source/signature | 951 B 00:00:00 !!!
google-chrome | 951 B 00:00:00
updates | 3.4 kB 00:00:00
(1/4): epel/x86_64/updateinfo | 839 kB 00:00:00
(2/4): epel/x86_64/primary_db | 4.8 MB 00:00:00
(3/4): adobe-linux-x86_64/primary_db | 2.7 kB 00:00:00
(4/4): updates/7/x86_64/primary_db | 2.9 MB 00:00:17
(1/2): google-chrome/primary | 2.0 kB 00:00:00
(2/2): gitlab_gitlab-ce/x86_64/primary | 956 kB 00:00:02
Loading mirror speeds from cached hostfile
* base: ftp.iij.ad.jp
* epel: ftp.riken.jp
* extras: ftp.iij.ad.jp
* updates: ftp.iij.ad.jp
gitlab_gitlab-ce 304/304
google-chrome 3/3
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:10.0.3-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:10.0.4-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
依存性を解決しました
=======================================================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
=======================================================================================================================================================
更新します:
gitlab-ce x86_64 10.0.4-ce.0.el7 gitlab_gitlab-ce 343 M
トランザクションの要約
=======================================================================================================================================================
更新 1 パッケージ
総ダウンロード容量: 343 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for gitlab_gitlab-ce
gitlab-ce-10.0.4-ce.0.el7.x86_64.rpm | 343 MB 00:00:20
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1508573876_2017_10_21_10.0.3_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-10.0.4-ce.0.el7.x86_64 1/2
整理中 : gitlab-ce-10.0.3-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitaly: 1s, normally up
ok: down: gitlab-monitor: 0s, normally up
ok: down: gitlab-workhorse: 1s, normally up
ok: down: logrotate: 0s, normally up
ok: down: nginx: 0s, normally up
ok: down: node-exporter: 0s, normally up
ok: down: postgres-exporter: 0s, normally up
ok: down: postgresql: 1s, normally up
ok: down: prometheus: 0s, normally up
ok: down: redis: 1s, normally up
ok: down: redis-exporter: 0s, normally up
ok: down: sidekiq: 0s, normally up
ok: down: unicorn: 0s, normally up
ok: run: postgresql: (pid 9643) 0s
ok: run: redis: (pid 9645) 0s
run: postgresql: (pid 9643) 0s; run: log: (pid 745) 11418535s
run: redis: (pid 9645) 0s; run: log: (pid 756) 11418535s
Reconfiguring GitLab to apply migrations
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Checking for an omnibus managed postgresql: OK
Checking for a newer version of PostgreSQL to install
No new version of PostgreSQL installed, nothing to upgrade to
Ensuring PostgreSQL is updated: OK
Restarting previously running GitLab services
ok: run: gitaly: (pid 10329) 0s
ok: run: gitlab-monitor: (pid 10338) 0s
ok: run: gitlab-workhorse: (pid 10313) 1s
ok: run: logrotate: (pid 10341) 0s
ok: run: nginx: (pid 10344) 0s
ok: run: node-exporter: (pid 10348) 1s
ok: run: postgres-exporter: (pid 10368) 0s
ok: run: postgresql: (pid 9643) 54s
ok: run: prometheus: (pid 10371) 0s
ok: run: redis: (pid 9645) 54s
ok: run: redis-exporter: (pid 10374) 0s
ok: run: sidekiq: (pid 10392) 0s
ok: run: unicorn: (pid 10395) 0s
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ \`/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else.
If you need to roll back to the previous version you can use the database
backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-10.0.4-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-10.0.3-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:10.0.4-ce.0.el7
完了しました!
10.0.4 -> 10.1.0
2017.10.25
$ sudo yum update gitlab-ce-10.1.0
読み込んだプラグイン:fastestmirror, langpacks
Repository google-chrome is listed more than once in the configuration
adobe-linux-x86_64 | 2.9 kB 00:00:00
base | 3.6 kB 00:00:00
epel/x86_64/metalink | 6.9 kB 00:00:00
epel | 4.3 kB 00:00:00
extras | 3.4 kB 00:00:00
gitlab_gitlab-ce/x86_64/signature | 836 B 00:00:00
gitlab_gitlab-ce/x86_64/signature | 1.0 kB 00:00:00 !!!
gitlab_gitlab-ce-source/signature | 836 B 00:00:00
gitlab_gitlab-ce-source/signature | 951 B 00:00:00 !!!
google-chrome | 951 B 00:00:00
updates | 3.4 kB 00:00:00
(1/5): epel/x86_64/updateinfo | 843 kB 00:00:00
(2/5): epel/x86_64/primary_db | 4.8 MB 00:00:00
(3/5): adobe-linux-x86_64/primary_db | 2.7 kB 00:00:00
(4/5): extras/7/x86_64/primary_db | 128 kB 00:00:07
(5/5): updates/7/x86_64/primary_db | 3.6 MB 00:00:19
gitlab_gitlab-ce/x86_64/primary | 961 kB 00:00:02
Determining fastest mirrors
* base: ftp.tsukuba.wide.ad.jp
* epel: ftp.riken.jp
* extras: ftp.tsukuba.wide.ad.jp
* updates: ftp.tsukuba.wide.ad.jp
gitlab_gitlab-ce 305/305
依存性の解決をしています
--> トランザクションの確認を実行しています。
---> パッケージ gitlab-ce.x86_64 0:10.0.4-ce.0.el7 を 更新
---> パッケージ gitlab-ce.x86_64 0:10.1.0-ce.0.el7 を アップデート
--> 依存性解決を終了しました。
依存性を解決しました
======================================================================================================================================================
Package アーキテクチャー バージョン リポジトリー 容量
======================================================================================================================================================
更新します:
gitlab-ce x86_64 10.1.0-ce.0.el7 gitlab_gitlab-ce 353 M
トランザクションの要約
======================================================================================================================================================
更新 1 パッケージ
総ダウンロード容量: 353 M
Is this ok [y/d/N]: y
Downloading packages:
No Presto metadata available for gitlab_gitlab-ce
gitlab-ce-10.1.0-ce.0.el7.x86_64.rpm | 353 MB 00:00:20
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
gitlab preinstall: Automatically backing up only the GitLab SQL database (excluding everything else!)
Dumping database ...
Dumping PostgreSQL database gitlabhq_production ... [DONE]
done
Dumping repositories ...
[SKIPPED]
Dumping uploads ...
[SKIPPED]
Dumping builds ...
[SKIPPED]
Dumping artifacts ...
[SKIPPED]
Dumping pages ...
[SKIPPED]
Dumping lfs objects ...
[SKIPPED]
Dumping container registry images ...
[DISABLED]
Creating backup archive: 1508935770_2017_10_25_10.0.4_gitlab_backup.tar ... done
Uploading backup archive to remote storage ... skipped
Deleting tmp directories ... done
done
Deleting old backups ... skipping
更新します : gitlab-ce-10.1.0-ce.0.el7.x86_64 1/2
整理中 : gitlab-ce-10.0.4-ce.0.el7.x86_64 2/2
Checking PostgreSQL executables: OK
Shutting down all GitLab services except those needed for migrations
ok: down: gitaly: 0s, normally up
ok: down: gitlab-monitor: 0s, normally up
ok: down: gitlab-workhorse: 1s, normally up
ok: down: logrotate: 0s, normally up
ok: down: nginx: 1s, normally up
ok: down: node-exporter: 0s, normally up
ok: down: postgres-exporter: 0s, normally up
ok: down: postgresql: 0s, normally up
ok: down: prometheus: 0s, normally up
ok: down: redis: 1s, normally up
ok: down: redis-exporter: 0s, normally up
ok: down: sidekiq: 0s, normally up
ok: down: unicorn: 0s, normally up
ok: run: postgresql: (pid 32652) 1s
ok: run: redis: (pid 32660) 0s
run: postgresql: (pid 32652) 1s; run: log: (pid 745) 11780426s
run: redis: (pid 32660) 0s; run: log: (pid 756) 11780426s
Reconfiguring GitLab to apply migrations
* Moving existing certificates found in /opt/gitlab/embedded/ssl/certs
* Symlinking existing certificates found in /etc/gitlab/trusted-certs
gitlab Reconfigured!
Checking for an omnibus managed postgresql: OK
Checking for a newer version of PostgreSQL to install
No new version of PostgreSQL installed, nothing to upgrade to
Ensuring PostgreSQL is updated: OK
Restarting previously running GitLab services
ok: run: gitaly: (pid 971) 0s
ok: run: gitlab-monitor: (pid 981) 0s
ok: run: gitlab-workhorse: (pid 945) 2s
ok: run: logrotate: (pid 994) 0s
ok: run: nginx: (pid 996) 0s
ok: run: node-exporter: (pid 998) 0s
ok: run: postgres-exporter: (pid 956) 1s
ok: run: postgresql: (pid 32652) 68s
ok: run: prometheus: (pid 1002) 0s
ok: run: redis: (pid 32660) 67s
ok: run: redis-exporter: (pid 1009) 1s
ok: run: sidekiq: (pid 1027) 0s
ok: run: unicorn: (pid 1029) 0s
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ \`/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else.
If you need to roll back to the previous version you can use the database
backup made during the upgrade (scroll up for the filename).
検証中 : gitlab-ce-10.1.0-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-10.0.4-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:10.1.0-ce.0.el7
完了しました!
13.0.14 -> 13.1.11
$ sudo yum update gitlab-ce-13.1.11 読み込んだプラグイン:fastestmirror, langpacks Repository google-chrome is listed more than once in the configuration Loading mirror speeds from cached hostfile * base: ftp.iij.ad.jp * epel: d2lzkl7pfhq30w.cloudfront.net * extras: ftp.iij.ad.jp * updates: mirror01.idc.hinet.net gitlab_gitlab-ce/x86_64/signature | 862 B 00:00:00 gitlab_gitlab-ce/x86_64/signature | 1.0 kB 00:00:00 !!! gitlab_gitlab-ce-source/signature | 862 B 00:00:00 gitlab_gitlab-ce-source/signature | 951 B 00:00:00 !!! runner_gitlab-runner/x86_64/signature | 862 B 00:00:00 runner_gitlab-runner/x86_64/signature | 1.0 kB 00:00:00 !!! runner_gitlab-runner-source/signature | 862 B 00:00:00 runner_gitlab-runner-source/signature | 951 B 00:00:00 !!! 依存性の解決をしています --> トランザクションの確認を実行しています。 ---> パッケージ gitlab-ce.x86_64 0:13.0.14-ce.0.el7 を 更新 ---> パッケージ gitlab-ce.x86_64 0:13.1.11-ce.0.el7 を アップデート --> 依存性解決を終了しました。 依存性を解決しました ======================================================================================================================================================== Package アーキテクチャー バージョン リポジトリー 容量 ======================================================================================================================================================== 更新します: gitlab-ce x86_64 13.1.11-ce.0.el7 gitlab_gitlab-ce 703 M トランザクションの要約 ======================================================================================================================================================== 更新 1 パッケージ 総ダウンロード容量: 703 M Is this ok [y/d/N]:
上手くいった。
Running handlers:
Running handlers complete
Chef Client finished, 112/1188 resources updated in 02 minutes 01 seconds
gitlab Reconfigured!
Restarting previously running GitLab services
ok: run: alertmanager: (pid 14696) 0s
ok: run: gitaly: (pid 3044) 632s
ok: run: gitlab-exporter: (pid 14699) 0s
ok: run: gitlab-pages: (pid 14704) 0s
ok: run: gitlab-workhorse: (pid 14670) 1s
ok: run: grafana: (pid 14711) 0s
ok: run: logrotate: (pid 14716) 0s
ok: run: nginx: (pid 14719) 0s
ok: run: node-exporter: (pid 14721) 0s
ok: run: postgres-exporter: (pid 14728) 0s
ok: run: postgresql: (pid 3197) 629s
ok: run: prometheus: (pid 14736) 0s
ok: run: puma: (pid 14744) 0s
ok: run: redis: (pid 3241) 628s
ok: run: redis-exporter: (pid 14758) 1s
ok: run: sidekiq: (pid 14813) 0s
_______ __ __ __
/ ____(_) /_/ / ____ _/ /_
/ / __/ / __/ / / __ `/ __ \
/ /_/ / / /_/ /___/ /_/ / /_/ /
\____/_/\__/_____/\__,_/_.___/
Upgrade complete! If your GitLab server is misbehaving try running
sudo gitlab-ctl restart
before anything else.
The automatic database backup was skipped as requested.
You may enable it again anytime by running the following command:
sudo rm /etc/gitlab/skip-auto-backup
検証中 : gitlab-ce-13.1.11-ce.0.el7.x86_64 1/2
検証中 : gitlab-ce-13.0.14-ce.0.el7.x86_64 2/2
更新:
gitlab-ce.x86_64 0:13.1.11-ce.0.el7
完了しました!