Hello, I’m reaching out about an issue related to PuppetDB. I am hoping that someone will be able to assist myself and my coworker in solving this problem.
When I take a look inside the puppetdb log file the error that I am seeing is `ERROR [p.p.config] No subname set in the "database" config`. Root to the log file is - /var/log/puppetlabs/puppetdb/puppetdb.log. If I try to start puppetdb service manually by running `systemctl start puppetdb` I then receive the following error message: `Job for puppetdb.service failed because the control process exited with error code. See "systemctl status puppetdb.service" and "journalctl -xe" for details.` Following this when looking at `journalctl -xe` I can see the error message: `-- The unit puppetdb.service has entered the 'failed' state with result 'exit-code' Oct 04 13:37:36 puppet systemd[1]: Failed to start puppetdb Service. -- Subject: A start job for unit puppetdb.service has failed.' I have also included in this the PuppetDB scripts and any related scripts. The following script is for puppet.conf location is /etc/puppetlabs/puppet/puppet.conf. # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available: # - https://puppet.com/docs/puppet/latest/config_important_settings.html # - https://puppet.com/docs/puppet/latest/config_about_settings.html # - https://puppet.com/docs/puppet/latest/config_file_main.html # - https://puppet.com/docs/puppet/latest/configuration.html [server] vardir = /opt/puppetlabs/server/data/puppetserver logdir = /var/log/puppetlabs/puppetserver rundir = /var/run/puppetlabs/puppetserver pidfile = /var/run/puppetlabs/puppetserver/puppetserver.pid codedir = /etc/puppetlabs/code [master] storeconfigs = true storeconfigs_backend = puppetdb reports = store, puppetdb [agent] noop = true The next script is from puppetdb.conf location is /etc/puppetlabs/puppet/puppetdb.conf [main] server_urls = https://puppetdb.company.com:8081 The puppetdb config.ini file (/etc/puppetlabs/puppetdb/conf.d/config.ini) is as follows: #logging-config = /etc/puppetlabs/puppetdb/logback.xml #[command-processing] # How many command-processing threads to use, defaults to (CPUs / 2) # threads = 4 # How many threads can write to disk at once, defaults to min(CPUs / 2, 4) # concurrent-writes = 4 [global] vardir = /var/lib/puppetdb logging-config = /var/lib/puppetdb/logback.xml [database] classname = org.postgresql.Driver subprotocol = postgresql subname = //localhost:8081/puppetdb [puppetdb] certificate-whitelist = /path/to/file/containing/certnames disable-update-checking = false The puppetdb jetty.ini file (/etc/puppetlabs/puppetdb/conf.d/jetty.ini) is as follows: [jetty] # IP address or hostname to listen for clear-text HTTP. To avoid resolution # issues, IP addresses are recommended over hostnames. # Default is `localhost`. # host = <host> # Port to listen on for clear-text HTTP. port = 8080 # The following are SSL specific settings. They can be configured # automatically with the tool `puppetdb ssl-setup`, which is normally # ran during package installation. # IP address to listen on for HTTPS connections. Hostnames can also be used # but are not recommended to avoid DNS resolution issues. To listen on all # interfaces, use `0.0.0.0`. ssl-host = 0.0.0.0 # The port to listen on for HTTPS connections ssl-port = 8081 # Private key path ssl-key = /etc/puppetlabs/puppetdb/ssl/private.pem # Public certificate path ssl-cert = /etc/puppetlabs/puppetdb/ssl/public.pem # Certificate authority path ssl-ca-cert = /etc/puppetlabs/puppetdb/ssl/ca.pem # Access logging configuration path. To turn off access logging # comment out the line with `access-log-config=...` access-log-config = /etc/puppetlabs/puppetdb/request-logging.xml client-auth = want The puppetdb auth.conf file (/etc/puppetlabs/puppetdb/conf.d/auth.conf) is as follows: authorization: { version: 1 rules: [ { # Allow unauthenticated access to the status service endpoint match-request: { path: "/status/v1/services" type: path method: get } allow-unauthenticated: true sort-order: 500 name: "puppetlabs status service - full" }, { match-request: { path: "/status/v1/simple" type: path method: get } allow-unauthenticated: true sort-order: 500 name: "puppetlabs status service - simple" }, { # Allow nodes to access the metrics service # for puppetdb, the metrics service is the only # service using the authentication service match-request: { path: "/metrics" type: path method: [get, post] } allow: "*" sort-order: 500 name: "puppetlabs puppetdb metrics" }, { # Deny everything else. This ACL is not strictly # necessary, but illustrates the default policy match-request: { path: "/" type: path } deny: "*" sort-order: 999 name: "puppetlabs deny all" } ] } I hope that I have provided enough information needed for this issue with puppetdb. If you would like any additional information to assist with being able to solve this please feel free to ask, and thank you in advance for your help on this issue -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/a106da8f-3946-42a3-9bc4-59b9643ff312n%40googlegroups.com.
