This appears to be a logic error in the condor_schedd. Itâs attempting to create two data structures for a single parallel job in a table that should only have one entry per job. To complicate matters, I see thereâs a bug in one of the log messages that we
could use to figure out whatâs going wrong.
My quick inspection of the code didnât turn up any obvious ways to trigger the double-entry problem.
This is happening while the condor_schedd is attempting to reconnect to running parallel jobs after a restart. Are you seeing this happen more than once?
- Jaime
|