Troubleshooting the databases
If you have issues with the databases that support the
console, make sure that the PostgreSQL database is not too
large or using too much memory, that you don't have port conflicts, and that puppet apply
is configured correctly.
PostgreSQL is taking up too much space
The PostgreSQL
autovacuum=on
setting prevents the database
from growing too large and unwieldy. Routine vacuuming is turned on by default.
autovacuum
is set to on
.
PostgreSQL buffer memory causes installation to fail
When installing PE on machines with large amounts of RAM, the PostgreSQL database might use more shared buffer memory than is available.
/var/log/pe-postgresql/pgstartup.log
shows the
error:FATAL: could not create shared memory segment: No space left on device
DETAIL: Failed system call was shmget(key=5432001, size=34427584512,03600).
The default port for PuppetDB conflicts with another service
By default, PuppetDB communicates over port 8081. In some cases, this might conflict with existing services, for example McAfee ePolicy Orchestrator.
pe.conf
that specifies a different
port using puppet_enterprise::puppetdb_port
.
puppet resource
generates Ruby errors after connecting puppet apply
to PuppetDB
If Puppet apply is configured incorrectly, for example
by modifying puppet.conf
to add the parameters storeconfigs_backend
= puppetdb
and storeconfigs = true
in both the main and
primary server sections, puppet resource
ceases to function and displays a
Ruby run error.
/etc/puppetlabs/puppet/routes.yaml
to correctly connect Puppet apply
without affecting other functions.