In the Puppet Enterprise (PE) console, you see the error:
An error occurred loading this page: There was an error connecting to PuppetDB: Connection refused. PuppetDB might be unreachable in the console if:
- PuppetDB is out of memory
- PuppetDB is unreachable
- The PuppetDB port is being used by another service
Version and installation information
PE version: All supported
Out of memory
If PuppetDB memory usage exceeds the Java heap size, it crashes, causing errors in
puppetdb: # java.lang.OutOfMemoryError: Java heap space puppetdb: # -XX:OnOutOfMemoryError="kill -9 %p" puppetdb: # Executing /bin/sh -c "kill -9 8353"... pe-puppetdb.service: main process exited, code=killed, status=9/KILL Unit pe-puppetdb.service entered failed state. systemd: pe-puppetdb.service failed. pe-puppetdb.service holdoff time over, scheduling restart. Starting pe-puppetdb Service…
You can fix the errors by increasing the Java heap size so that the
pe-puppetdb service has enough memory.
PuppetDB is unreachable
If PuppetDB is not running or is unreachable, you get a 500 error during Puppet runs.
# puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Error: Could not retrieve catalog from remote server: Error 500 on SERVER:
For more information on troubleshooting this issue, read Troubleshoot PuppetDB (pe-puppetdb) in Puppet Enterprise.
The PuppetDB port is being used by another service
By default, PuppetDB communicates over port 8081. In some cases, this might conflict with other services, such as McAfee ePolicy Orchestrator. If there is an
Address already in use error, when
pe-puppetdb service is started, another service is using the port. Learn more about how to fix this error.