Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- root@localhost:/vagrant# dpkg -i puppetdb_3.0.0-1puppetlabs1_all.deb
- (Reading database ... 50968 files and directories currently installed.)
- Preparing to replace puppetdb 2.3.5-1puppetlabs1 (using puppetdb_3.0.0-1puppetlabs1_all.deb) ...
- usermod: no changes
- Unpacking replacement puppetdb ...
- dpkg: warning: unable to delete old directory '/etc/puppetdb/conf.d': Directory not empty
- dpkg: warning: unable to delete old directory '/etc/puppetdb': Directory not empty
- dpkg: warning: unable to delete old directory '/var/log/puppetdb': Directory not empty
- dpkg: warning: unable to delete old directory '/var/lib/puppetdb/mq': Directory not empty
- dpkg: warning: unable to delete old directory '/var/lib/puppetdb/db': Directory not empty
- dpkg: warning: unable to delete old directory '/var/lib/puppetdb': Directory not empty
- Setting up puppetdb (3.0.0-1puppetlabs1) ...
- Installing new version of config file /etc/default/puppetdb ...
- Installing new version of config file /etc/logrotate.d/puppetdb ...
- Installing new version of config file /etc/init.d/puppetdb ...
- Migrating configuration files /tmp/puppetdb-orig-configs/jetty.ini /tmp/puppetdb-orig-configs/database.ini /tmp/puppetdb-orig-configs/config.ini to /etc/puppetlabs/puppetdb/conf.d
- Replacing: /etc/puppetlabs/puppetdb/conf.d/jetty.ini with /tmp/puppetdb-orig-configs/jetty.ini
- Replacing: /etc/puppetlabs/puppetdb/conf.d/database.ini with /tmp/puppetdb-orig-configs/database.ini
- Replacing: /etc/puppetlabs/puppetdb/conf.d/config.ini with /tmp/puppetdb-orig-configs/config.ini
- Checking to see if we need to update default settings
- Backing up /etc/puppetlabs/puppetdb/conf.d/config.ini to /etc/puppetlabs/puppetdb/conf.d/config.ini.bak.1436403369 before making changes
- Updated setting vardir in /etc/puppetlabs/puppetdb/conf.d/config.ini.
- Replacing: /opt/puppetlabs/server/data/puppetdb with /var/lib/puppetdb
- Updated setting logging-config in /etc/puppetlabs/puppetdb/conf.d/config.ini.
- Backing up /etc/puppetlabs/puppetdb/conf.d/jetty.ini to /etc/puppetlabs/puppetdb/conf.d/jetty.ini.bak.1436403369 before making changes
- Updated setting ssl-key in /etc/puppetlabs/puppetdb/conf.d/jetty.ini.
- Copying: /etc/puppetdb/ssl/private.pem to /etc/puppetlabs/puppetdb/ssl/private.pem
- Updated setting ssl-cert in /etc/puppetlabs/puppetdb/conf.d/jetty.ini.
- Copying: /etc/puppetdb/ssl/public.pem to /etc/puppetlabs/puppetdb/ssl/public.pem
- Updated setting ssl-ca-cert in /etc/puppetlabs/puppetdb/conf.d/jetty.ini.
- Copying: /etc/puppetdb/ssl/ca.pem to /etc/puppetlabs/puppetdb/ssl/ca.pem
- Backing up /etc/puppetlabs/puppetdb/conf.d/database.ini to /etc/puppetlabs/puppetdb/conf.d/database.ini.bak.1436403369 before making changes
- Updated setting subname in /etc/puppetlabs/puppetdb/conf.d/database.ini.
- Copying over the contents of /var/lib/puppetdb/db to /opt/puppetlabs/server/data/puppetdb/db
- Warning: Unable to find the path to copy
- This tool requires the following to exist:
- * /var/lib/puppetdb/db
- Re-run this tool then restart PuppetDB to complete the config
- setup:
- puppetdb config-migration
- cleaning up old config files
- Removing /etc/puppetdb/conf.d/jetty.ini
- Removing /etc/puppetdb/conf.d/database.ini
- Removing /etc/puppetdb/conf.d/config.ini
- Modifications may have been made to PuppetDB config files. To ensure these changes have been picked up, please do the following:
- 1) upgrade the puppetdb-termini package
- 2) restart the puppetdb service
- 3) restart the puppetserver service
- PEM files in /etc/puppetlabs/puppetdb/ssl already exists, checking integrity.
- Setting ssl-host in /etc/puppetlabs/puppetdb/conf.d/jetty.ini already correct.
- Setting ssl-port in /etc/puppetlabs/puppetdb/conf.d/jetty.ini already correct.
- Setting ssl-key in /etc/puppetlabs/puppetdb/conf.d/jetty.ini already correct.
- Setting ssl-cert in /etc/puppetlabs/puppetdb/conf.d/jetty.ini already correct.
- Setting ssl-ca-cert in /etc/puppetlabs/puppetdb/conf.d/jetty.ini already correct.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement