Re: [HTCondor-users] Write errors on secondary disk

["Hughes, Zachary" <zdhughes@xxxxxxxxx>]

Update: It was evil, evil SELinux. Disabled with edit to /etc/sysconfig/selinux.

---

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of htcondor-users-request@xxxxxxxxxxx <htcondor-users-request@xxxxxxxxxxx>
Sent: Monday, September 12, 2016 6:01 PM
To: htcondor-users@xxxxxxxxxxx
Subject: HTCondor-users Digest, Vol 34, Issue 12

 

Message: 5
Date: Mon, 12 Sep 2016 23:00:54 +0000
From: "Hughes, Zachary" <zdhughes@xxxxxxxxx>
To: "htcondor-users@xxxxxxxxxxx" <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] Write errors on secondary disk
Message-ID:
        <MWHPR02MB2239EC1975432CAAAFF638D8D3FF0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
       
Content-Type: text/plain; charset="us-ascii"

Update with some more information:


So, I can submit jobs from herc1 and starscream and they write correctly and without issue. The only discernible difference I can see is that the UID:GID for the condor accounts are unique on herc1/starscream, but on herc0 the group ID was assigned to an existing group:


$ id condor

uid=987(condor) gid=987(chrony) groups=987(chrony)


I did groupmod -g 982 condor and usermod -g 982 condor to give the condor account a new gid:


$ id condor
uid=987(condor) gid=982(condor) groups=982(condor),1000(labuser)


and updated condor_config:


CONDOR_IDS = 987.982


but I'm still getting the same error. Is there some other permission that I'm missing or is this a red herring?


Thanks,


Zach