Release Automation

Expand all | Collapse all

Agent conection problem.

Jump to Best Answer
  • 1.  Agent conection problem.

    Posted 08-11-2017 08:29 PM
      |   view attached

    The agent was uninstalled and the re-installed in a hp-ux server, now the agent doesn’t connect with RA execution because a  failed handshake. How do I resolve this issue?


    This is from the nimi.log file. . ( I attached the complete log file if you want to read it)

    2017-08-11 16:14:21,723 [KeepAliveWorker-859] WARN  (com.nolio.nimi.comm.impl.NetworkConnectionManagerImpl:274) - could not create connection to [/10.75.248.65:6600] because of failed handshake

    2017-08-11 16:14:21,724 [KeepAliveWorker-859] INFO  (com.nolio.nimi.comm.impl.NetworkConnectionManagerImpl:207) - Failed to connect - no more retries. number-tries:2

    2017-08-11 16:14:21,724 [KeepAliveWorker-859] WARN  (com.nolio.nimi.comm.impl.OutboundConnectionsImpl:442) - could not establish connection to address [/10.75.248.65:6600], message [KEEP_ALIVE] is not sent.

    2017-08-11 16:14:21,724 [KeepAliveWorker-859] WARN  (com.nolio.nimi.keepalive.impl.KeepAliveClientWorker:147) - Could not connect to supernode on [/10.75.248.65:6600] - could not establish connection to address [/10.75.248.65:6600], message [KEEP_ALIVE] is not sent.

    2017-08-11 16:14:21,724 [KeepAliveWorker-859] DEBUG (com.nolio.nimi.keepalive.impl.KeepAliveClientWorker:149) - Exception caught:NimiCommException - could not establish connection to address [/10.75.248.65:6600], message [KEEP_ALIVE] is not sent.

    2017-08-11 16:14:21,724 [KeepAliveWorker-859] DEBUG (com.nolio.nimi.keepalive.impl.KeepAliveClientWorker:156) - Going to wait [60] seconds.

    2017-08-11 16:14:28,913 [PeriodicChecks] INFO  (com.nolio.nimi.appmsg.durability.PeriodicChecks:100) - There are 0 received shippings

    2017-08-11 16:14:28,913 [PeriodicChecks] INFO  (com.nolio.nimi.appmsg.durability.PeriodicChecks:121) - There are 0 shippings to send

    2017-08-11 16:14:28,914 [PeriodicChecks] INFO  (com.nolio.nimi.appmsg.durability.PeriodicChecks:77) - This node info : NodeInfo{nodeId=nid:ccollsms1, hostname='ccollsms1', addresses=[/10.75.128.128:6600, /192.168.82.33:6600], nodeType=NODE, version=6.2.0.3017}

    2017-08-11 16:14:28,914 [PeriodicChecks] INFO  (com.nolio.nimi.appmsg.durability.PeriodicChecks:79) - Connected supernodes (0) : []

    2017-08-11 16:15:21,733 [KeepAliveWorker-861] DEBUG (com.nolio.nimi.keepalive.impl.KeepAliveClientWorker:333) - Worker running, current state is [WAIT_FOR_RESPONSE]

    2017-08-11 16:15:21,733 [KeepAliveWorker-861] DEBUG (com.nolio.nimi.keepalive.impl.KeepAliveClientWorker:313) - Timed out waiting.

    2017-08-11 16:15:21,733 [KeepAliveWorker-861] DEBUG (com.nolio.nimi.keepalive.impl.KeepAliveClientWorker:333) - Worker running, current state is [SEEK_SUPERNODE]

    2017-08-11 16:15:21,733 [KeepAliveWorker-861] DEBUG (com.nolio.nimi.keepalive.impl.KeepAliveClientWorker:133) - Started seeking supernode.

    2017-08-11 16:15:21,734 [KeepAliveWorker-861] DEBUG (com.nolio.nimi.keepalive.impl.KeepAliveClientWorker:142) - Worker is trying to connect to [/10.75.248.65:6600].

    2017-08-11 16:15:21,734 [KeepAliveWorker-861] DEBUG (com.nolio.nimi.comm.impl.NetworkConnectionManagerImpl:240) - Actively connecting to node [null] at [/10.75.248.65:6600] try:1

    2017-08-11 16:15:21,736 [KeepAliveWorker-861] DEBUG (com.nolio.nimi.comm.impl.NetworkConnectionManagerImpl:245) - Waiting for chanel connection...

    2017-08-11 16:15:21,738 [KeepAliveWorker-861] DEBUG (com.nolio.nimi.comm.impl.NetworkConnectionManagerImpl:251) - Channel connected to [null].

    2017-08-11 16:15:21,738 [New I/O client worker #1-1] DEBUG (com.nolio.nimi.comm.impl.nettysupport.BasicHandler:89) - ActiveHandshakeHandler Connected CONNECTED /10.75.248.65:6600 opened the connection.

    2017-08-11 16:15:21,738 [New I/O client worker #1-1] INFO  (com.nolio.nimi.comm.impl.nettysupport.BasicHandler:76) - Created channel: [[id: 0x01dd1bd6, /10.75.128.128:56056 => /10.75.248.65:6600]]

    2017-08-11 16:15:21,747 [New I/O client worker #1-1] ERROR (com.nolio.nimi.comm.impl.nettysupport.BasicHandler:147) - Handshaking failed on channel [[id: 0x01dd1bd6, /10.75.128.128:56056 => /10.75.248.65:6600]], closing connection...

    2017-08-11 16:15:21,747 [New I/O client worker #1-1] DEBUG (com.nolio.nimi.comm.impl.nettysupport.BasicHandler:101) - ActiveHandshakeHandler disconnected CONNECTED /10.75.248.65:6600 closing the connection.

    2017-08-11 16:15:21,747 [New I/O client worker #1-1] INFO  (com.nolio.nimi.comm.impl.NimiConnectionImpl:133) - connection [NimiConnectionImpl{remoteAddress=null, localAddress=null, connectionID=null, channel=null, closed=true, lastAccessedTime=1502478921734}] is closed.

    2017-08-11 16:15:21,748 [New I/O client worker #1-1] ERROR (com.nolio.nimi.comm.impl.nettysupport.BasicHandler:57) - NimiConnectionImpl{remoteAddress=null, localAddress=null, connectionID=null, channel=null, closed=true, lastAccessedTime=1502478921734}:javax.net.ssl.SSLKeyException: RSA premaster secret error

    javax.net.ssl.SSLKeyException: RSA premaster secret error

                    at com.sun.net.ssl.internal.ssl.Handshaker.checkThrown(Handshaker.java:941)

                    at com.sun.net.ssl.internal.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:465)

                    at com.sun.net.ssl.internal.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:718)

                    at com.sun.net.ssl.internal.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:686)

                    at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:607)

                    at org.jboss.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:868)

                    at org.jboss.netty.handler.ssl.SslHandler.decode(SslHandler.java:605)

                    at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:282)

                    at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:216)

                    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)

                    at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)

                    at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349)

                    at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:281)

                    at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)

                    at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)

                    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

                    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

                    at java.lang.Thread.run(Thread.java:619)


    Attachment(s)

    zip
    nimi.zip   54K 1 version


  • 2.  Re: Agent conection problem.

    Posted 08-14-2017 09:47 AM

    Hi , 

     

    It looks like there is a problem with the SSL handshake between the nes and the agent. 

    If you use custom security certificates on the nes they may need to be reinstalled on the agent after the reinstallation of the agent . 

     

    Please see the following section in the RA documentation about configuring the agent for custom certificates 

    Security Configuration - CA Release Automation - 6.4 - CA Technologies Documentation 

     

    Regards

    Dirk



  • 3.  Re: Agent conection problem.

    Posted 08-14-2017 02:21 PM

    Dirk: What about this error:

     

    Caused by: java.security.NoSuchAlgorithmException: SunTlsRsaPremasterSecret KeyGenerator not available
    at javax.crypto.KeyGenerator.<init>(DashoA13*..)
    at javax.crypto.KeyGenerator.getInstance(DashoA13*..)
    at com.sun.net.ssl.internal.ssl.JsseJce.getKeyGenerator(JsseJce.java:223)
    at com.sun.net.ssl.internal.ssl.RSAClientKeyExchange.<init>(RSAClientKeyExchange.java:89)

     

    Is it possible that the agent user cannot access the java files?

     

    The agent points to:

     

    Agent:  ccollsms1

     

    Std out: lrwxr-x--x 1 x001285 relauto 23 Jul 3 22:45 /opt/RA/jre/bin/NolioAgent -> /opt/java6/jre/bin/java

     

    but I checked the  java process running on the server:

     

    root 17157 17145 0 Aug 8 ? 10:45 /opt/java6/jre/bin/IA64N/java -Djava.ext.dirs=./jre/lib/ext:./lib:./libNoUpgrade:./lib/ext:./lib/db -Duser.country=US -Duser.la



  • 4.  Re: Agent conection problem.

    Posted 08-15-2017 06:00 AM

    Hi 

     

    That error would indicate that the JRE runtime is missing some files or we cannot access them . 

    The NolioAgent is linked to the java jre which is supposed to run the agent java code.

    Did you also reinstall the java runtime as part of the agent reinstall 

     

    Dirk 



  • 5.  Re: Agent conection problem.

    Posted 08-15-2017 11:34 AM

    No, the JRE is being used by another applications in production. What files does the agent need to access?

     

    Thanks



  • 6.  Re: Agent conection problem.

    Posted 08-16-2017 10:37 AM

    Hi, 

     

    I think it would be better to raise a support case for this , so we can review the logs from the agent

    and see if we can find out what is missing here.

    The error indicates that we can not find or access one off the Java SSL related jars . 

     

    Regards

    Dirk 



  • 7.  Re: Agent conection problem.
    Best Answer

    Posted 08-16-2017 03:15 PM

    Hi: The main problem was tha java files were in read only mode for "others".

     

    lrwxr-x---   1 x001285    relauto         22 Aug 11 00:58 ext -> /opt/java6/jre/lib/ext

    ls -la /opt/java6/jre/lib/ext:

    drwxrwxr--   2 bin        bin           8192 Dec 10  2009 ext

    lrwxr-x--- 1 root accesstt 23 Jun 13 13:31 NolioAgent -> /opt/java6/jre/bin/java

    -rwxrwxr-- 1 bin bin 110264 Apr 28 2009 /opt/java6/jre/bin/java

     

    After applying execution permissions the agent became alive again.

     

     

    Thanks for your help on this.



  • 8.  Re: Agent conection problem.

    Posted 01-31-2019 06:37 AM

    hi JulioCesarDominguez, Yasuyuki_Miura

     

    I found the same error log for an issue and , I am thinking to adapt this solution, but there is not JavaX folder under/opt/ directory.

    I see /bin and /lib folders under opt/nolio/nolioagent directory.

     

    Can you confirm it is correct path to look at?

     

    Thanks & Regards,

    Vrunda



  • 9.  Re: Agent conection problem.

    Posted 01-31-2019 09:30 PM

    Hi,

     

    It seems the customer installed RA Agent on HP-UX. RA installer for HP-UX doesn't have JRE, so I suppose the customer installed JRE to /opt/java6 manually and linked from RA installation directory.

    System Requirements - CA Release Automation - 6.6 - CA Technologies Documentation 

     

    So, the path maybe different from yours.

    If you installed RA agent on Linux, please check the permission of <nolioagent> directory and sub directories like jre. I guess you started RA Agent using non-root user or impersonated to execute any actions.

    If so, please check and implement with this manual.

    Deploy Agents - CA Release Automation - 6.6 - CA Technologies Documentation 

    - Install Unix / Linux Agent to Run as Non-Root User

    - Run Processes Under Different Users – Unix/Linux

     

    Thanks

    Yas