Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
The process might have been stuck on I/O as sigterm did not take it down. SIGKILL did it, and this allowed DUCC to spawn another JP and retry the 15 WI hung there.
The Job Details page correctly reflected the killed JP as Failed + Failed +SIGKILL(9).
The Jobs page has zeros for both Init and Run Fails. One of them should have been 1.