CAUAJM_E_18200 Error Interfacing with PostgreSQL

Products

• Autosys Workload Automation

Issue/Introduction

You observe frequent error messages in your AutoSys Application Server (as_server) and Event Server (event_demon) logs indicating problems with the PostgreSQL database connection. These messages often include:

• CAUAJM_E_18200 An error has occurred while interfacing with POSTGRESQL.
• CAUAJM_E_18201 Function <do_PQSendQueryPrepared> invoked from <executeQuery> failed at <786>
• CAUAJM_E_18205 Event Server: <db_server:db:schema> Failed Query:
• CAUAJM_E_18211 server closed the connection unexpectedly
• CAUAJM_W_10900 The database monitoring system has detected a potential problem with the database.
• CAUAJM_I_10901 The database monitoring system is beginning validation of database connections.

These errors indicate that AutoSys experienced a temporary loss of connection to the PostgreSQL database, but the system's built-in retry logic successfully re-established the connection without requiring manual intervention.

 

Environment

Product: AutoSys Workload Automation

Version: 24.0.01-1346

Database: PostgreSQL v14 (remote)

Operating System: Linux

 

Cause

The primary cause of these messages is an intermittent loss of network connectivity between the AutoSys Application/Event Server and the PostgreSQL database. While disruptive, AutoSys has robust retry mechanisms designed to re-establish these connections automatically. Additionally, an improperly configured max_connections setting in your PostgreSQL database could contribute to connection-related issues.

 

Resolution

These specific CAUAJM_E_182xx errors, especially when followed by CAUAJM_W_10631, CAUAJM_W_10632, CAUAJM_I_10633, CAUAJM_I_10902, CAUAJM_I_10903, and CAUAJM_I_10165, indicate that AutoSys encountered a database connection issue, paused activity, validated the database health, and then successfully reconnected and resumed operations. This behavior is by design and demonstrates the system's self-healing capabilities.

To minimize the frequency of these connection drops, or to address situations where reconnections are not consistently successful, ensure your PostgreSQL database is optimally configured:

1. Review PostgreSQL max_connections: You must verify that the max_connections parameter in your PostgreSQL configuration file (postgresql.conf) is set to an appropriate value for your environment. An insufficient number of allowed connections can cause database-side disconnections.

   • For detailed guidance on this and other database considerations, consult the "Installation Consideration for PostgreSQL" section in your official AutoSys Workload Automation product documentation.

2. Monitor Network Stability: While AutoSys can recover from intermittent connection loss, persistent errors suggest underlying network instability between your AutoSys servers and the database. Work with your network administrators to ensure stable and reliable network connectivity to your PostgreSQL database.

Additional Information
Messages like the following confirm the system's successful retry and recovery:

[08/11/2025 12:14:52]       CAUAJM_W_10631 Error with database <db_server,db_port:db_name:db_schema>. Checking connection.
[08/11/2025 12:14:52]       CAUAJM_W_10632 Attempting to reconnect to database <db_server,db_port:db_name:db_schema>. Attempt number [1].
[08/11/25 12:14:52]       CAUAJM_I_10633 Reconnection attempt for database <db_server,db_port:db_name:db_schema> succeeded.
[08/11/2025 12:14:52]       CAUAJM_I_10902 The database monitoring system has completed validation of database connections.
[08/11/2025 12:15:02]       CAUAJM_I_10165 The previously failed query below succeeded after 2 attempt(s):

These messages indicate that the system has successfully handled the connection interruption and restored full functionality.