Automic Workload Automation

 View Only
  • 1.  v21.x Install problem - Failed to connect to aesvr:8443

    Posted May 23, 2022 12:19 PM
    Dear All,

    We are trying to do a fresh install of the latest build of AA 21.0.2 on a RHEL 8.x server. The install fails while trying to create Client 100. The install log shows messages like:

    May 23, 2022 9:14:31 PM com.automic.installer.api.ae.scripts.AbstractScript runWithUC4Jar
    INFO: Executing com.automic.installer.api.ae.scripts.CreateClientScript with file:/opt/CA/Automic/API/ApplicationInterface/uc4.jar
    May 23, 2022 9:14:31 PM com.automic.installer.api.actions.ae.CreateUserAndClient run
    WARNING: RunScript does not work because: Failed to connect to aesvr:8443
    May 23, 2022 9:14:32 PM com.automic.installer.api.ae.scripts.AbstractScript runWithUC4Jar
    INFO: Executing com.automic.installer.api.ae.scripts.CreateClientScript with file:/opt/CA/Automic/API/ApplicationInterface/uc4.jar
    May 23, 2022 9:14:32 PM com.automic.installer.api.actions.ae.CreateUserAndClient run
    WARNING: RunScript does not work because: Failed to connect to aesvr:8443

    Any thoughts on what could be going wrong here?

    Regards
    P Verghese


  • 2.  RE: v21.x Install problem - Failed to connect to aesvr:8443

    Posted May 24, 2022 01:21 AM
    Hi Pothen,

    This is only an abstract of the entire log file:
    • can you identify other error messages?
    • how about the AE - is it running?

    This failing step of the One.Installer only creates client 100 - and this can be done afterwards a manual installation. Important is to have AE v21 up and running.

    Does a "normal installation" using tar files work?

    regards,
    Peter


  • 3.  RE: v21.x Install problem - Failed to connect to aesvr:8443

    Posted May 24, 2022 10:06 AM
    Hi Peter,

    This is a ONE Automation full install using the GUI.  The install process make many attempts to install the client 100 and then times out with below message:

    WARNING: RunScript does not work because: Failed to connect to aesvr:8443
    May 19, 2022 5:35:06 PM com.automic.installer.api.common.Installer createInstallerException
    SEVERE: Check the installation log for more details. The installation log is located in /opt/CA/Automic/install.log
    java.lang.reflect.InvocationTargetException
    at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.automic.installer.api.ae.scripts.AbstractScript.runWithUC4Jar(AbstractScript.java:158)
    at com.automic.installer.api.ae.components.ApplicationInterface.runScript(ApplicationInterface.java:28)
    at com.automic.installer.api.actions.ae.CreateUserAndClient.run(CreateUserAndClient.java:43)
    at com.automic.installer.api.common.engine.InstallerAction.start(InstallerAction.java:44)
    at com.automic.installer.api.common.engine.InstallerEngine$2.run(InstallerEngine.java:97)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
    Caused by: java.io.IOException: Failed to connect to aesvr:8443
    at com.uc4.communication.WebSocketConnection.<init>(WebSocketConnection.java:237)
    at com.uc4.communication.Connection.<init>(Connection.java:52)
    at com.uc4.communication.Connection.open(Connection.java:160)
    at com.uc4.communication.Connection.open(Connection.java:136)
    at com.uc4.communication.Connection.open(Connection.java:113)
    at com.uc4.communication.Connection.open(Connection.java:91)
    at com.automic.installer.api.ae.scripts.AbstractScript.run(AbstractScript.java:132)
    ... 13 more
    Caused by: java.util.concurrent.ExecutionException: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
    at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1928)
    at com.uc4.communication.WebSocketConnection.<init>(WebSocketConnection.java:216)
    ... 19 more
    Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
    at sun.security.ssl.Alert.createSSLException(Alert.java:131)
    at sun.security.ssl.Alert.createSSLException(Alert.java:117)
    at sun.security.ssl.TransportContext.fatal(TransportContext.java:311)
    at sun.security.ssl.Alert$AlertConsumer.consume(Alert.java:293)
    at sun.security.ssl.TransportContext.dispatch(TransportContext.java:185)
    at sun.security.ssl.SSLTransport.decode(SSLTransport.java:149)
    at sun.security.ssl.SSLEngineImpl.decode(SSLEngineImpl.java:575)
    at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:531)
    at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:398)
    at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:377)
    at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:626)
    at org.eclipse.jetty.io.ssl.SslConnection.unwrap(SslConnection.java:414)
    at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:701)
    at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.process(HttpReceiverOverHTTP.java:164)
    at org.eclipse.jetty.client.http.HttpReceiverOverHTTP.receive(HttpReceiverOverHTTP.java:79)
    at org.eclipse.jetty.client.http.HttpChannelOverHTTP.receive(HttpChannelOverHTTP.java:131)
    at org.eclipse.jetty.client.http.HttpConnectionOverHTTP.onFillable(HttpConnectionOverHTTP.java:169)
    at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
    at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
    at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:540)
    at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:395)
    at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:161)
    at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
    at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:882)
    at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1036)
    ... 1 more

    May 19, 2022 5:35:06 PM com.automic.installer.api.ae.AEInstaller printTimeMap
    INFO: --- Execution Time Map ---

    We do see that CP1, WP1, JCP, JWP, REST and AWI are up and running.

    Regards
    P Verghese


  • 4.  RE: v21.x Install problem - Failed to connect to aesvr:8443

    Posted May 24, 2022 11:03 AM
    It seems this problem is caused if we change the default Keystore parameters under TLS settings. If we don't make changes to the default values, install goes through without any errors.

    This was not the case for the initail builds of v21. We had changed the password and alias values in the past and it did install fully.  This problem has creeped in from April build onwards.

    Regards
    P Verghese


  • 5.  RE: v21.x Install problem - Failed to connect to aesvr:8443

    Posted May 24, 2022 12:15 PM
    Hi Pothen,

    there are 4 typical reasons for the error message "java.util.concurrent.ExecutionException: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure":

    1. Un-synched same java version across all the servers/agents. You need to synched up the same java version across all the servers/agents.
    2. Incompatible cipher suites in use by the client and the server. This would require the client to use (or enable) a cipher suite that is supported by the server.
    3. Incompatible versions of SSL in use (the server might accept only TLS v1, while the client is capable of only using SSL v3). Again, you might have to ensure that it uses a compatible version of the SSL/TLS protocol.
    4. Incomplete trust path for the server certificate; the server's certificate is probably not trusted by the client. This would usually result in a more verbose error, but it is quite possible. Usually the fix is to import the server's CA certificate into the client's trust store.

    I don't think that 1, 2 and 3 do apply here, assume that (4) could be the reason.

    regards,
    Peter