ESP Workload Automation

Back to discussions
Expand all | Collapse all

Jobs running in ESP but not in Server

  • 1.  Jobs running in ESP but not in Server

    Posted Oct 22, 2013 03:39 PM
    Hi ,

    Job status showing as Executing in ESP but job is actually not running in the server. Please advice


  • 2.  RE: Jobs running in ESP but not in Server

    Posted Oct 22, 2013 03:47 PM
    Make sure the job actually ran on the sever. You could have a problem with your JTDT.

    HTH

    Allen


  • 3.  RE: Jobs running in ESP but not in Server

    Posted Oct 23, 2013 11:06 AM
    The job was running on the server for the past 2 years and we have an issue from yest


  • 4.  RE: Jobs running in ESP but not in Server

    Posted Oct 23, 2013 11:46 AM
    Did the job actually run on the server?


  • 5.  RE: Jobs running in ESP but not in Server

    Posted Oct 23, 2013 12:07 PM
    The job is showing as executing in ESP but it is not running on the server. not even creating any logs.Tried recycling the agent but no luck


  • 6.  RE: Jobs running in ESP but not in Server
    Best Answer

    Posted Oct 23, 2013 12:17 PM
    Ok, so you said ESP says it is executing.

    You could not find any logs for the job on the server.

    You restarted the ESP Agent on the server. If the job actually made it to the server, then when you restarted the ESP Agent, then you should have seen your job go into a failed status with a message (lost control).

    If this did not occur, then there may be more of an issue.

    Are other jobs running on this server too?

    If not, then maybe turn up the logging and try to recreate the problem with this job and capture all the ESP Agent logs and then open a ticket with CA.

    HTH

    Allen


  • 7.  RE: Jobs running in ESP but not in Server

    Posted Oct 23, 2013 12:20 PM
    Thanks Allen


  • 8.  RE: Jobs running in ESP but not in Server

    Posted Oct 23, 2013 02:09 PM
    Is this a Windows job on UNIX / Linux?

    Do you have access to the server?

    In CSF you can set up your presentation to display to display Job Number. Then logon to the server and check if the job is actually running.

    On UNIX / Linux:

    ps -ef | grep <Job Number>

    On Windows start Task Manager, select Process Tab, select View / Select Columns and verify PID is checked. Then sort on PID and look for Job Number.

    Have you checked the transmitter log for messages?

    A final thing to check is the agent parameter file for 'oscomponent.noexitcode=255' , or if it is coded to some other value.

    If that is set and the script exits with 255 or -1, the job will show in CSF as executing forever, or until someone manually intervenes.

    Then check the 'queue_communicator.log' for a message similar to 'State FAILED Cmpc(255) SetEnd CybInitiatorManagerNoPassaran'


  • 9.  RE: Jobs running in ESP but not in Server

    Posted Oct 23, 2013 02:25 PM
    Per an earlier post, he said the job was running on the server for the past 2 years and he had an issue from yesterday.


  • 10.  RE: Jobs running in ESP but not in Server

    Posted Oct 23, 2013 03:50 PM
    This may be the first time the script exited with exitstatus that is not defined as success..

    Can the ESP Job definition be posted?

    Has the agent parameter file been checked for ''oscomponent.noexitcode'?


  • 11.  Re: Jobs running in ESP but not in Server

    Posted Feb 21, 2017 12:28 PM

    Hi RickR using up this thread to followup on something you mentionned about 
    'State FAILED Cmpc(255) SetEnd CybInitiatorManagerNoPassaran'

    trying to find some information about this but comes out emtpy, what does it mean CybInitiatorManagerNoPassaran ? 



  • 12.  Re: Jobs running in ESP but not in Server

    Posted Feb 21, 2017 01:00 PM

    CA can probably provide a better answer but I have seen that message in the logs when the agent parameter file contains the line 'oscomponent.noexitcode=255' or the default is used.

     

    If a job runs and then completes with exit code 255 or -1 the ESP Agent will NOT send the AFM to the ESP Workload Manager.  Since the message is NOT sent the state will remain EXECUTING forever.

     

    I assume the message to mean the job has completed but the result is not passed back to ESP Workload Manager.

     

    Are you experiencing this behavior?

     

    What is the server OS?

     

    Is 'oscomponent.noexitcode=255' defined in the agent parameter file?

     

    If it is not present in the agent parameter file then the default values are used.

     

    oscomponent.noexitcode

    Specifies the exit code that tells the agent not to send a completion code to the scheduling manager host.

    Limits: 1-255

    Default: 255 for UNIX, 127 for Windows



  • 13.  Re: Jobs running in ESP but not in Server

    Posted Feb 21, 2017 01:08 PM

    Perfect that's exactly the answer I was looking for. I was seeing this message in our log and was not quite sure. changing the default value worked. thanks !



  • 14.  RE: Jobs running in ESP but not in Server

    Posted Oct 29, 2013 12:14 PM
    sivakumarv85:
    Hi , Job status showing as Executing in ESP but job is actually not running in the server. Please advice


    Do you have an update on this issue?

    If the issue has been resolved can you provide details on what the problem was?