Reports 1-1 of 1 Clear search Modify search
DetChar (General)
takahiro.yamamoto - 9:35 Tuesday 08 September 2026 (37468) Print this report
Segment generation failed because cache generation was put on hold
As the title says.

I released the held job and resumed cache generation.
After then, segment generation was also resumed.

$ condor_q
-- Schedd: kmst2-01 : <192.168.120.15:9618?... @ 09/08/26 09:22:45
ID OWNER SUBMITTED RUN_TIME ST PRI SIZE CMD
1928928.0 detchar 7/22 19:44 0+00:00:01 H 0 10.0 makeCache.sh -c Kashiwa -t full 0

$ condor_q -hold 1928928.0
-- Schedd: kmst2-01 : <192.168.120.15:9618?... @ 09/08/26 09:23:39
ID OWNER HELD_SINCE HOLD_REASON
1928928.0 detchar 9/8 07:00 Job missed deferred execution time

Total for query: 1 jobs; 0 completed, 0 removed, 0 idle, 0 running, 1 held, 0 suspended
Total for all users: 29 jobs; 0 completed, 4 removed, 1 idle, 21 running, 3 held, 0 suspended

$ condor_q -l 1928928.0 | grep -E 'HoldReason|HoldReasonCode|HoldReasonSubCode'
HoldReason = "Job missed deferred execution time"
HoldReasonCode = 20
LastHoldReason = "Job missed deferred execution time"
LastHoldReasonCode = 20
Comments to this report:
takahiro.yamamoto - 3:18 Friday 11 September 2026 (37480) Print this report
A same issue occurred again and a held job was released in order to resume all services.

A new script to automatically release held jobs due to the deferral time issue as ~detchar/.local/bin/release_held_jobs.sh.
When same issues will occur again, this script will be tested and after then this script will be launched as a resident service to monitor DetChar services.
Search Help
×

Warning

×