8.3. Analyzing Log Files of the Postgres ProGate Management Service #
To get the log files of the Postgres ProGate management service, run the journalctl -u progate.service command.
When analyzing log files, make sure they contain no errors. If the management service is launched correctly, the log records look like these:
10:08AM INF goose: successfully migrated database to version: 20260310150000 0:08AM INF pprof handlers registered 10:08AM INF pprof handlers registered 10:08AM INF static files handler registered 10:08AM INF app starts with version version=1.1.0 date_build=2026-03-16:13:07:07 branch=HEAD hash=b318e80c 10:08AM INF server started port=8081 10:08AM INF process monitor started 10:08AM INF notifier service started 10:08AM INF password expiration reporter started 10:08AM INF transfer scheduler started
In case of errors during the management service launch or operation, the log provides diagnostics information described in Table 8.1.
Table 8.1. Main Errors of the Postgres ProGate Management Service
| Error | Description | How to Fix |
|---|---|---|
10:11AM ERR failed to notify error="notifier: notify: notifier: process new security events: txman: begin tx: failed to connect to user=masked database=progate: 172.18.0.1:5450 (172.18.0.1): dial error: dial tcp 172.18.0.1:5450: connect: connection refused" service=notifier | Connection to the supporting database was lost during the management service operation. | Check the operability and accessibility of the supporting database. The management service restores the connection automatically when the database gets accessible again. |
10:17AM ERR Failed to initialize app err="app: init app: provide db: failed to connect to user=masked database=dbaas: 172.18.0.1:5450 (172.18.0.1): dial error: dial tcp 172.18.0.1:5450: connect: connection refused" | An error occurred while connecting to the supporting database during the management service launch. | Check the connection parameters in the management service configuration and the accessibility of the supporting database. Restart of the service is required to restore the operability. |
10:20AM ERR Failed to initialize app err="(SQLSTATE: 28000): invalid credentials" | Incorrect credentials for connection to the supporting database are specified. | Check the user name and password for connection to the supporting database. |
2026/04/08 10:36:06 ERROR Failed to initialize app err="app: init app: provide config: config validation failed: config: validate: Key: 'Config.Fields.Auth.AccessTokenSecret' Error:Field validation for 'AccessTokenSecret' failed on the 'min' tag: Key: 'Config.Fields.Auth.AccessTokenSecret' Error:Field validation for 'AccessTokenSecret' failed on the 'min' tag" | Configuration parameter validation error. | Correct the configuration of the management service. In this example, the value of AccessTokenSecret is less than the minimum required. Refer to Table 3.1 for details. |