AutoSys Workload Automation

 View Only
  • 1.  Autoping Failing - cybermation.library.communications.CybConversationException

    Posted Feb 28, 2018 01:22 PM

    Anybody faced similar errors with a new install? How to resolve this? Any ideas please?

    610 AIX ORA 11.3.5 INCR4_CUM_SEP2016 is trying to autoping agent 11.3.7 Maintenance Level 0, Build 979

     

    Telnet is fine for 7520, 7507, 7163, as per transmitter.log

     

    02/28/2018 13:05:56.177 EST-0500 5 TCP/IP Controller Plugin.Transmitter pool thread <Slow:1>.CybTargetHandlerChannel.call[:746] - Attempting to send: 20180228 12151215+0500 PR1_APP_xyz AGENT . CONTROL ACTIVE OSText(AIX for ppc64) ByUser(root) AgentRelease(11.3) AgentBuild(979, Service Pack 7, Maintenance Level 0) User(AGENT) Host(agent server name)
    02/28/2018 13:05:56.177 EST-0500 5 TCP/IP Controller Plugin.Transmitter pool thread <Slow:1>.CybTargetHandlerChannelLogHelper.logConnectionAttempt[:75] - Attempting to open conversation to PR1_APP_scheduler@scheduler dns name:7500 using plain socket
    02/28/2018 13:05:56.190 EST-0500 5 TCP/IP Controller Plugin.Transmitter pool thread <Slow:1>.CybTargetHandlerChannelLogHelper.logConnectionInfo[:109] - Opened conversation to PR1_APP_scheduler name@scheduler DNS name:7500 with partner at 10.63.114.165:7500 with timeout of 80000 from 10.105.0.7:35083
    02/28/2018 13:07:11.505 EST-0500 1 TCP/IP Controller Plugin.Transmitter pool thread <Slow:1>.CybTargetHandlerChannel.sendMessage[:627] - Error sending message to PR1_APP_scheduler name:
    cybermation.library.communications.CybConversationException: A system call received a parameter that is not valid. (Read failed)
    at cybermation.library.communications.protocol.CybCommunicationProtocolRevisionTwo.receiveData(CybCommunicationProtocolRevisionTwo.java:681)
    at cybermation.library.communications.protocol.CybCommunicationProtocolRevisionTwo.receiveAck(CybCommunicationProtocolRevisionTwo.java:299)
    at cybermation.library.communications.protocol.CybCommunicationProtocolRevisionTwo.sendMessage(CybCommunicationProtocolRevisionTwo.java:899)
    at cybermation.library.communications.CybConversation.sendMessage(CybConversation.java:595)
    at cybermation.commplugins.tcpip.handler.CybTargetHandlerChannel.sendMessage(CybTargetHandlerChannel.java:599)
    at cybermation.commplugins.tcpip.handler.CybTargetHandlerChannel.call(CybTargetHandlerChannel.java:773)
    at cybermation.commplugins.tcpip.handler.CybTargetHandlerChannel.call(CybTargetHandlerChannel.java:83)
    at cybermation.commplugins.tcpip.handler.CybTransmitterScheduler$CallableWrapper.call(CybTransmitterScheduler$CallableWrapper.java:397)
    at cybermation.commplugins.tcpip.handler.CybTransmitterScheduler$CallableWrapper.call(CybTransmitterScheduler$CallableWrapper.java:361)
    at java.util.concurrent.FutureTask.run(FutureTask.java:277)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.lang.Thread.run(Thread.java:785)
    Caused by: java.net.SocketException: A system call received a parameter that is not valid. (Read failed)
    at java.net.SocketInputStream.socketRead(SocketInputStream.java:127)
    at java.net.SocketInputStream.read(SocketInputStream.java:181)
    at java.net.SocketInputStream.read(SocketInputStream.java:152)
    at cybermation.library.communications.protocol.CybCommunicationProtocol.receiveLength(CybCommunicationProtocol.java:410)
    at cybermation.library.communications.protocol.CybCommunicationProtocolRevisionTwo.receiveData(CybCommunicationProtocolRevisionTwo.java:501)
    at cybermation.library.communications.protocol.CybCommunicationProtocolRevisionTwo.receiveAck(CybCommunicationProtocolRevisionTwo.java:299)
    at cybermation.library.communications.protocol.CybCommunicationProtocolRevisionTwo.sendMessage(CybCommunicationProtocolRevisionTwo.java:899)
    at cybermation.library.communications.CybConversation.sendMessage(CybConversation.java:595)
    at cybermation.commplugins.tcpip.handler.CybTargetHandlerChannel.sendMessage(CybTargetHandlerChannel.java:599)
    at cybermation.commplugins.tcpip.handler.CybTargetHandlerChannel.call(CybTargetHandlerChannel.java:773)
    at cybermation.commplugins.tcpip.handler.CybTargetHandlerChannel.call(CybTargetHandlerChannel.java:83)
    at cybermation.commplugins.tcpip.handler.CybTransmitterScheduler$CallableWrapper.call(CybTransmitterScheduler$CallableWrapper.java:397)
    at cybermation.commplugins.tcpip.handler.CybTransmitterScheduler$CallableWrapper.call(CybTransmitterScheduler$CallableWrapper.java:361)
    at java.util.concurrent.FutureTask.run(FutureTask.java:277)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1153)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.lang.Thread.run(Thread.java:785)

    02/28/2018 13:07:11.505 EST-0500 5 TCP/IP Controller Plugin.Transmitter pool thread <Slow:1>.CybTargetHandlerChannelLogHelper.logConnectionClose[:133] - Conversation with PR1_APP_LAQ9SCHPR02 closed



  • 2.  Re: Autoping Failing - cybermation.library.communications.CybConversationException

    Posted Feb 28, 2018 01:29 PM

    you should open a CA trouble ticket. 



  • 3.  Re: Autoping Failing - cybermation.library.communications.CybConversationException

    Posted Feb 28, 2018 07:51 PM

    The agent is apparently failing to connect with the AE application server (PR1_APP_), not the Scheduler. Did you do an autoping -S ?

    The agent is 64bit? That might explain the failure to talk to the App server. Anyhow, failure to talk to the App server should affect the jobs running.

     

    If you see same message when connecting to the Scheduler (PR1_SCH), then try these:

     

    • Increase paging memory

    • Increase file descriptors

     

    Cheers,

    Chandru

     

    Get Outlook for Android<https://aka.ms/ghei36>



  • 4.  Re: Autoping Failing - cybermation.library.communications.CybConversationException

    Posted Feb 28, 2018 09:55 PM

    Sorry, I meant "Anyhow, failure to talk to the App server should NOT affect the jobs running.".



  • 5.  Re: Autoping Failing - cybermation.library.communications.CybConversationException

    Posted Mar 01, 2018 08:10 AM

    # autoping -m New_machine


    CAUAJM_I_50023 AutoPinging Machine [New_machine]
    CAUAJM_W_10496 Agent on [New_machine] has not responded in a timely fashion. Try again later. [CA WAAE Autoping]
    CAUAJM_E_50281 AutoPing from the Scheduler WAS NOT SUCCESSFUL.

    CAUAJM_I_50282 AutoPing from the Application Server WAS SUCCESSFUL.

    CAUAJM_E_50026 ERROR: AutoPing WAS NOT SUCCESSFUL.



  • 6.  Re: Autoping Failing - cybermation.library.communications.CybConversationException

    Posted Mar 01, 2018 08:13 AM

     $ ./cybAgent -vv

    CA Workload Automation Agent for:
    AIX ppc 64-bit
    11.3, Service Pack 7, Maintenance Level 0, Build 979
    Log file can not be opened: [The file access permissions do not allow the specified action.]. The message is: <Jars found: jars/config.jar:jars/core.jar:jars/filebrowser.jar:jars/filemon.jar:jars/ftp.jar:jars/installer.jar:jars/jmxconnector.jar:jars/js.jar:jars/library.jar:jars/management.jar:jars/objmon.jar:jars/plugin_installer.jar:jars/pluginlib.jar:jars/router.jar:jars/runner.jar:jars/snmp.jar:jars/snmpagent.jar:jars/snmpconnector.jar:jars/tcpip.jar:jars/utility.jar:jars/ext/axis-ant.jar:jars/ext/axis-schema.jar:jars/ext/axis.jar:jars/ext/commons-codec.jar:jars/ext/commons-discovery.jar:jars/ext/commons-httpclient.jar:jars/ext/commons-logging.jar:jars/ext/jaxrpc.jar:jars/ext/jsafeJCEFIPS.jar:jars/ext/saaj.jar:jars/ext/sinetfactory.jar:>
    Log file can not be opened: [The file access permissions do not allow the specified action.]. The message is: <Calling cybermation.agent.CybAgentDriver.main>



  • 7.  Re: Autoping Failing - cybermation.library.communications.CybConversationException
    Best Answer

    Posted Mar 03, 2018 08:26 PM

    On Aix the Agent uses the OS (native) Java. It might be worth to try upgrading the Java (from IBM) to the latest.