Anyone seen this before ?
yes. the job is already running. is it actually running ?
The 1st instance when it failed was on 5th Feb & this is what we have in the BL logs. - Didn't find any target servers for job ''XXXXXX"
ok, so the Deploy job failed on 05-FEB because the job didn't have any targets.
and the same deploy job is not shown in 'tasks in progress' right now (meaning there is not another run happening) ?
and you run the job and get the 'job is already running' message ?
The Job had been running fine till 5th Feb, the missing targets is something we need to find out. (why did it alert that) there is no run happening as of now. But when it was executed manually later on, it worked fine.
But when it was executed manually later on, it worked fine.
ok, so the job is running fine now ?
Yes Bill. Thanks for all your help.
I am having this issue right now. We have a deploy job to install Patrol. We started 2 builds. The first one is working fine and the second works fine until it gets to the patrol deploy job. We get the error below. I tried going to the source deploy job and manually executing against the target. The job pops up in tasks in progress and immediately goes away. There is no job log for the manual attempt. I think tried adding the target directly to the job and executing. Same result with no job history. I havent tried other deploy jobs yet. That will be my next test.
[12 Mar 2018 20:23:43,285] [Job-Execution-2] [INFO] [user:role] [Batch] __JobRun-2905370,5-6895063__ Started running member job Patrol-9.6.00.04 Install --Linux Non-SAP -- Deploy
[12 Mar 2018 20:23:43,291] [Job-Execution-1] [ERROR] [user:role] [Deploy] Job 'Patrol-9.6.00.04 Install --Linux Non-SAP -- Deploy' is already running
com.bladelogic.om.infra.mfw.util.BlException: Job 'Patrol-9.6.00.04 Install --Linux Non-SAP -- Deploy' is already running
[12 Mar 2018 20:23:43,294] [Job-Execution-9] [ERROR] [user:role] [Batch] __JobRun-2905370,5-6895063__ Job Patrol-9.6.00.04 Install --Linux Non-SAP -- Deploy Could not be executed. Possible reasons could be:
- Incorrect authorizations.
- Job Patrol-9.6.00.04 Install --Linux Non-SAP -- Deploy is already running.
1 of 1 people found this helpful
is this an adv deploy job or basic ? i believe the adv deploy will not let you have multiple instances of it running.
You nailed it Bill. The execution of my deploy job comes by execute against a batch job that contains the deploy job. The source deploy job was set to advanced. When the batch job would start, the other components run just fine but would give the error if the source deploy job was already running from a different run of that batch job.
I set the deploy job back to basic and we are now able to run the batch job multiple times.