Troubleshooting common issues

This guide provides solutions for the most common issues encountered when using WarehousePG Enterprise Manager (WEM). If your issue persists after following these steps, please contact your system administrator.

Connectivity

Issue: Cannot connect to the database

If WEM is unable to reach the WarehousePG cluster, follow these diagnostic steps:

1. Ensure the database is active and accepting local connections:

   → WrapCopy

   psql -d postgres -c "SELECT version();"

2. Verify that the WEM connection strings are correctly set in the environment:

   → WrapCopy

   env | grep WHPG

3. Use the built-in WEM tool from the WEM host to validate the current configuration:

   → WrapCopy

    ./wem setup --verify

4. Test the credentials directly via the CLI using the same parameters defined in the WEM Settings tab within the Users panel.

   → WrapCopy

   PGHOST=localhost PGUSER=gpadmin psql -d postgres -c "SELECT current_database();"

Authentication and access

Message: "Session expired"

Cause: Your security token has timed out due to a period of inactivity.

Solution: Select Log In to return to the authentication screen and re-enter your credentials.

Note that any unsaved changes in forms or the query editor will be lost upon session expiration. To prevent this issue, save your configuration changes frequently and avoid long periods of idle time with the browser tab open.

Error: "Permission denied"

Cause: Your assigned role does not have the authorization required to perform the requested action.

Solution:

1. Verify your current role in the sidebar footer.
2. Review the Role permissions matrix to confirm if the action is permitted for your tier.
3. If you require elevated access, contact your WEM Administrator to request a role change.

Query editor restrictions

Issue: Query is blocked

Symptoms:

• "Query blocked" error messages.
• Inability to execute INSERT, UPDATE, or DELETE statements.
• DDL commands (e.g., CREATE, DROP) are rejected.

Cause: WEM enforces role-based SQL restrictions to prevent accidental data loss or unauthorized schema changes.

Observability and metrics

Issue: Charts are not displaying

Some tabs display the error Prometheus not configured. Set PROMETHEUS_URL to enable metrics charts (e.g., http://localhost:9090).

Cause: The connection to the Prometheus metrics server is either not correctly configured or down.

Solution:

1. Verify that Prometheus is running and reachable via the URL defined in the Settings tab within the Users panel.
2. Check network connectivity and firewall rules between the WEM server and the Prometheus endpoint.

Issue: Logs are not loading

The Loki Logs tab within the Logs panel reports the error: Loki integration is not configured.

Cause: The Loki log aggregation service is unavailable or the URL is incorrect.

Solution:

1. Ensure the Loki service is active.
2. Verify the Loki URL in the Settings tab within the Users panel.
3. Check server-side logs for "Connection Refused" errors.