On 07/09/2014 03:25 PM, Lou DeGenaro wrote:
Upon re-start (presuming you
used the default warm start) all previous running jobs are marked as
Completed. If the the job itself is Completed yet the job-processes
continue to show an active state then this is erroneous information..
Dear Lou,
The
The facts are:
1. The job is not really running. In reality there are *no* active
job-processes.
2. The information on the Job Details page is wrong. It reports
job-processes as running when in reality there are none. For example, can
you find the PID for the supposedly running job-process on
Reshu,
If this is the same issue you mentioned in the Jira it's possible
that the Agent isn't able to properly shutdown. You can get around this
by issuing
check_ducc -k
after
stop_ducc -a
As a rule of thumb, I like to stop ducc by issuing check_ducc -k a
few times
Hi,
I have faced a problem in DUCC after continuous processing in DUCC, the
job initialization or ending processing go in to infinite loop. So, a
new job can not be started even after restarting of DUCC and job is
showing end of job status internally initialization waiting time is
