Automic Workload Automation

 View Only

  • 1.  AWI unable to connect to engines

    Posted Feb 24, 2025 08:23 PM

    Hello, we are running into the issue 

    Connection to the AE system not possible. No connection to the following CPs could be established: MYIP:6443 Please make sure that the system meets the minimum requirement for processes and that it uses WS.PORT to establish the connection.

    Our system was fine until last weekend, when we got the errors 

    U00003590 UCUDB - DB error: '28P01', 'FATAL: password authentication failed for user "automic_admin"', '0', 'org.postgresql.util.PSQLException'

    and

    U00000006 DEADLOCK or Connection to database lost - Rollback handling initiated. See previous messages

    while running a client copy. We assume it was due to a password reset for our DB user where we changed the password in the ucsrv.ini but did not restart the engines. After stopping the client copy and restarting the engines, we are now unable to connect the AWI to the engines at all and getting the error stated above. The JCPs, CPs, and WPs are all up and we don't see any errors in the logs either. We also did not change the .pem cert used for the TLS connection and made sure the port 6443 was included in the range specified in the ucsrv.ini for the WS.PORT. Has anyone else run into this issue before?



  • 2.  RE: AWI unable to connect to engines

    Posted Feb 26, 2025 11:52 AM

    Also had these messages in the AWI logs

    [TRACE] NOLOGIN/- NOUI   [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - WebSocketClient has no more active sessions and will shut down.
    [TRACE] NOLOGIN/- NOUI   [com.uc4.ecc.framework.core.aetracing.AutomationEngineTraceListener] - WebSocketClient stopped.




  • 3.  RE: AWI unable to connect to engines

    Posted Feb 26, 2025 02:19 PM

    Hi,

    did you check if there is anything running on port 6443, e.g. with

    # Linux
    telnet <server> 6443
    
    # Win (Powershell)
    test-netconnection <server> -port 6443

    also check your uc4config.xml 




  • 4.  RE: AWI unable to connect to engines

    Posted Feb 26, 2025 03:30 PM

    Hello Matthias,

    We ran both the ping and telnet commands to double check that the engine was listening on 6443 and we also made sure nothing else was already taking up the port.




  • 5.  RE: AWI unable to connect to engines

    Posted Feb 27, 2025 07:56 AM

    Hi,

    did you try to login to client 0 with the UC user and default password?

    https://docs.automic.com/documentation/webhelp/english/AA/21/DOCU/21/Automic%20Automation%20Guides/Content/_Common/Security/Security_PWManagement.htm?Highlight=uc%20default%20password

    Matthias