While installing the PEM server on RHEL 8, if you see this error:
python3-mod_wsgi package first:
Try installing the PEM server again.
After installing the PEM server on RHEL 7 ppc64le, you might see the following cipher error in the worker log file:
To resolve this error, if you intend to stay on PostgreSQL version 12, upgrade to the latest available version. Then, restart the PEM agent.
In some situations, you might need to uninstall the PEM server, reinstall it, and then configure the server again. To do so:
Remove the PEM server configuration and uninstall:
Remove the PEM packages:
Move the certificates from
/root/.pem/to another location:
/usr/edb/pem/agent/etc/agent.cfgto another location:
Then, configure the PEM server again:
If the PEM web client isn't loading, check the HTTPD log in the
If you see the following message in the log:
Add the following statement at the bottom of the Apache
httpd.conf file located in the
Restart the HTTPD server after adding the statement:
When connecting to a PostgreSQL server, you might get one of these error messages. Review the message carefully. Each error message attempts to incorporate the information you need to resolve the problem.
Connection to the server has been lost: This error message indicates that the connection attempt took longer than the specified threshold. There might be a problem with the connection properties provided on the Server dialog box, network connectivity issues, or the server might not be running.
Could not connect to Server: Connection refused: There are two possible reasons for this error:
The database server isn't running. Start the server.
The server isn't configured to accept TCP/IP requests on the address shown.
For security reasons, a PostgreSQL server "out of the box" doesn't listen on TCP/IP ports. Instead, you must enable it to listen for TCP/IP requests. Add
tcpip = trueto the
postgresql.conffile for Versions 7.3.x and 7.4.x. Add
listen_addresses='*'for Version 8.0.x and above. These additions make the server accept connections on any IP interface.
For more information, refer to the PostgreSQL documentation about runtime configuration.
FATAL: no pg_hba.conf entry: If PEM displays this message when connecting, your server can be contacted correctly over the network, but it isn't configured to accept your connection. Your client wasn't detected as a legal user for the database.
To connect to a server, configure the
pg_hba.conffile on the database server to accept connections from the host of the PEM client. Modify the
pg_hba.conffile on the database server host, and add an entry in the form:
host template1 postgres 192.168.0.0/24 md5for an IPV4 network
host template1 postgres ::ffff:192.168.0.0/120 md5for an IPV6 network
For more information, see the PostgreSQL documentation about client authentication.
FATAL: password authentication failed: The
password authentication failed for usererror message indicates there might be a problem with the password you entered. Retry the password to confirm you entered it correctly. If the error message returns, make sure that you have the correct password, that you are authorized to access the server, and that the access was correctly configured in the server's
Run this command to check whether the PEM webserver is up and running:
SERVER_ADDR is the IP address of your PEM server. The output
PING confirms the PEM web server is up and running.