Re: [HTCondor-users] ShadowLog not accessible for Shadows, jobs not starting/not ending up in the right slot for their Shadow

[Michael Pelletier <michael.v.pelletier@xxxxxxxxxxxx>]

The RAM disk workaround, I remembered yesterday, was tied to messages in the audit event log, not in ShadowLog. Hopefully one of the experts can suss out the root cause of this issue.

Michael V. Pelletier
Information Technology
Digital Transformation & Innovation
Integrated Defense Systems
Raytheon Company


-----Original Message-----
From: Thomas Hartmann <thomas.hartmann@xxxxxxx> 
Sent: Wednesday, February 5, 2020 4:55 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Cc: Michael Pelletier <michael.v.pelletier@xxxxxxxxxxxx>
Subject: [External] Re: [HTCondor-users] ShadowLog not accessible for Shadows, jobs not starting/not ending up in the right slot for their Shadow

Hi Michael,

thanks for the hints.

Unfortunately, the log dir and logs all belong to condor:condor.

But interestingly, the message still pops up endlessly, when moving the
ShadowLog to the ram disk [1]?!

Cheers,
  Thomas


[1]
root@grid-arcce1: [~] tail -F /dev/shm/ShadowLog
02/05/20 10:25:10 (20489576.0) (3710922): File transfer completed
successfully.
02/05/20 10:25:10 (20489576.0) (3710922): WriteUserLog checking for
event log rotation, but no lock
02/05/20 10:25:10 (20489576.0) (3710922): WriteUserLog checking for
event log rotation, but no lock