Release Automation

Expand all | Collapse all

Deployer on Host not responding

  • 1.  Deployer on Host not responding

    Posted 03-11-2015 12:38 AM

    Earlier our deployment on same environment was working however now a days we get error that deployer is not responding.


    This error occur random interval and tried with various approach however still persist with no reason.


    Server XXXXXXXXXXX(XX.XX.XX.XX) error : Deployer on host XXXXXXXXXXX does not respond.


    It happens only for couple of server and not all, not sure whats wrong when earlier it was working as expected.



  • 2.  Re: Deployer on Host not responding

    Posted 03-31-2015 12:28 PM

    Any help for Mayank?

     

    Thanks

     

    Deployer on Host not responding

    This question is Not Answered.(Mark as assumed answered)

    Mayank SugandhiMember

    Earlier our deployment on same environment was working however now a days we get error that deployer is not responding.


    This error occur random interval and tried with various approach however still persist with no reason.


    Server XXXXXXXXXXX(XX.XX.XX.XX) error : Deployer on host XXXXXXXXXXX does not respond.


    It happens only for couple of server and not all, not sure whats wrong when earlier it was working as expected.



  • 3.  Re: Deployer on Host not responding

    Posted 03-31-2015 01:44 PM

    Hi Mayank

    This can be caused by several reasons (Simple reasons can caused by MAX agents per NES , duplication node id/ip , topology/firewall issues etc...)

    Best way to investigate is to check both agents and NES logs once its not working



  • 4.  Re: Deployer on Host not responding

    Posted 05-07-2015 04:45 AM

    Thanks,

     

    It was primary issue we identify and corrected however still there are issues on some servers.

     

    However these servers are our production and disaster recovery server can perform any debugging, is there any easy to identify possible other reasons. 



  • 5.  Re: Deployer on Host not responding

    Posted 06-05-2015 05:46 PM

    I just noticed you haven't gotten a reply yet -- I apologize for us not responding sooner.  Is this still an issue in your environment?

     

    If so, if you've exhausted investigating the above possible causes, such as network outages, firewall interference, etc., then it would probably be best to log a case through support.ca.com so we can collect your logs and thoroughly investigate the problem.