Release Automation

  • 1.  Flow Get Stuck in Execution Server Type

    Posted Oct 21, 2016 10:04 AM

    Hi Team,

    We have recently upgraded from 5.5 to 6.1 and then 6.2 , When we started testing our existing flows it doesn't work when execution server agents is running some process, It gets stuck at that point without going to that server type.

    We have NAC, NES and Agent all on one server (For information).

     

    I checked few logs but it doesn't give much information as flow get stuck at one point where execution server type agent doesn't do anything and no error is detected in logs.

    Similarly, If i try to copy using (Get file or folder from remote agent) action it fails saying "Failed to connect".

     

    Any idea whats going wrong here?

     

    Regards

    Abhi



  • 2.  Re: Flow Get Stuck in Execution Server Type

    Broadcom Employee
    Posted Oct 21, 2016 10:07 AM

    Hi,

     Can you please share logs like nolio_dm_all, and nimi and also agent logs if possible.

     

    Thanks,

    Saurabh



  • 3.  Re: Flow Get Stuck in Execution Server Type

    Posted Oct 21, 2016 10:29 AM

    Hi Saurabh,

     

    Please find attached logs.

     

     

    Thanks & Regards

    Abhishek Mandhyani

    Services Consultant

     

    CA Technologies | V Parku 2343/24 Chodov | Praha 4, 011 148 00

    Office: +26168 | Mobile: +420 778 475 621 | Abhishek.Mandhyani@ca.com

     

    <mailto:Abhishek.Mandhyani@ca.com>[CA_Cert_Pro_ProcessAutomation_r4x]

     

     

    Attachment(s)

    zip
    nolio_dm_all.log.zip   35 KB 1 version
    zip
    nimi.log.zip   182 KB 1 version


  • 4.  Re: Flow Get Stuck in Execution Server Type

    Broadcom Employee
    Posted Oct 24, 2016 05:03 AM

    Hi Abhishek,

     From the logs file nimi.log it looks like there is a problem in route discovery for the agent WIN-B4O6HKQBVUN. Currently I am not sure but I am hoping you are using this agent to run the action.

     

    There is a sort of loop in your routing which may be resulting in the above behavior.

    route contains a loop with this node [nid:WIN-B4O6HKQBVUN]

     

    From which are are you trying to run this process from Test, ASAP process RUN or release. Can you please correct this routing problem and if possible try to restart your agent clearing persistency folder content on agent and re-try.

     

    thanks,

    Saurabh



  • 5.  Re: Flow Get Stuck in Execution Server Type
    Best Answer

    Broadcom Employee
    Posted Oct 26, 2016 06:43 AM

    Hi Abhishek,

     We are marking this thread as answered as it translated into case where post assessment we find very specific case arise in your environment where path got corrupted.

     

    Thanks,

    Saurabh