Hi all, just an update not to dangle the topic openWith intervention from the experts the issue got identified - it was apparently the way we set up our group/quotas. Our group quotas were set on the group level but we had configured additional subgroupings for users - so that the quotas could not properly matched as we had no quotas on the subgroup level :-[
Cheers, Thomas On 06/02/2020 19.47, Michael Pelletier via HTCondor-users wrote:
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 _______________________________________________ HTCondor-users mailing list To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a subject: Unsubscribe You can also unsubscribe by visiting https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users The archives can be found at: https://lists.cs.wisc.edu/archive/htcondor-users/
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature