[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] What's supposed to create /var/run/condor?
- Date: Thu, 22 Mar 2018 16:52:54 +0000
- From: Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>
- Subject: Re: [HTCondor-users] What's supposed to create /var/run/condor?
Fantastic, thanks for the tip! I hadn't noticed the tmpfiles config mechanism before. All this handy newfangled stuff is nice compared to when I started using Linux back in the 90's.
It turns out that the root cause of the problem was that the tmpfiles service was starting before the Centrify authentication service was fully ready, and as a result it couldn't find the "condor" account in the Active Directory server to assign ownership of the /var/run/condor directory. I'm fixing it by adding condor to /etc/passwd, and I'll update the install documentation for my administrators.
Interestingly, the /var/lock/condor directory seems to have worked okay, so apparently Centrify came online between the two entries in the condor-tmpfiles.conf.
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Ben Cotton
Sent: Thursday, March 22, 2018 12:36 PM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [External] Re: [HTCondor-users] What's supposed to create /var/run/condor?
The Fedora package installs a tmpfiles config file:
I think the UW package includes this, too, but you may want to check to make sure it's in the right location. That will cause systemd to create the directories at boot.