6 Replies Latest reply on Aug 23, 2019 1:33 PM by Rajesh Raghavan

    Control-M v9.0.19 slow

    Rajesh Raghavan
      Share This:

      We recently upgraded our Control-M infrastructure from v9.0 to Control-M v9.0.19. Some of our OS jobs are running slow,I mean the OS jobs get completed soon within 2 minutes, however the response coming back to EM and reflecting the completed status in the client takes about 15 minutes. Has anybody experienced this issue in v9.0.19?



        • 1. Re: Control-M v9.0.19 slow
          Jesse Richardson

          Successfully moved to Control-M so community product experts can help

          • 2. Re: Control-M v9.0.19 slow
            Paul Robins

            If it takes 15 minutes for a job status to update, it would seem that the Control-M Agent is getting blocked sending updates back to the Control-M Server when the job is complete. The job is only updated when the Control-M/Server queries the Agent every 15 minutes.

            Check that your firewall is allowing comms from the Agents to Server on port 7005.

            1 of 1 people found this helpful
            • 3. Re: Control-M v9.0.19 slow
              Rajesh Raghavan

              Thanks Paul. Here is the output snippet of ag_diag_comm:

              Server-to-Agent Port Number    : 7006

              Agent-to-Server Port Number    : 7005

              Server-Agent Protocol Version  : 12

              Server-Agent Comm. Protocol    : TCP

              Server-Agent Connection mode   : Transient

              Unix Ping to Server Platform   : Succeeded

              Agent Ping to Control-M/Server : Failed

              Agent processes status


              Agent Listener                 : Running as svc_inf+ (13195)

              Agent Tracker                  : Running as svc_inf+ (13248)

              Agent Tracker-Worker           : Running as svc_inf+ (2985)


              Warning!!! agent processes ownership doesn't match configuration value 'svc_infa'


              Two things stand out:


              < Agent Ping to Control-M/Server : Failed> - The agent is on AWS EC2 and all the outbound traffic is unrestricted. So I am not sure Agent ping is failing on port 7005.


              < Warning!!! agent processes ownership doesn't match configuration> - Not sure what this means.

              1 of 1 people found this helpful
              • 4. Re: Control-M v9.0.19 slow
                Paul Robins

                The outbound traffic from the agent might be unrestricted, but the inbound traffic to your Control-M/Server may be restricted, especially if it's not in cloud with the agent.

                I don't think the process ownership is part of the issue but definitely something you might want to investigate.

                1 of 1 people found this helpful
                • 5. Re: Control-M v9.0.19 slow
                  PIETER JURESSEN

                  Those 15 minutes is a timeout value for control-m agents. Verify if port 7006 is open from agent to server.

                  3 of 3 people found this helpful
                  • 6. Re: Control-M v9.0.19 slow
                    Rajesh Raghavan

                    The issue is fixed. Root-cause was the agent on EC2 was unable to communicate on port 7005 for some reason even though there were no firewall restrictions for outbound requests from EC2. As soon as I changed the "Agent-to-Server" port to 7007, everything started working as expected.

                    Thank you so much Pieter and Paul for pointing out that the agent is timing out after 15 minutes. That was really a crucial piece of information to solve this problem.

                    1 of 1 people found this helpful