After some research, and comparing with the
installation of HTCondor on another VM, I think I got the
explanation. I installed v8.2.3 on this VM box directly by using
'sudo apt-get condor', before setting up the UW repo and
installing v8.6.1. Looks like this file (00debconf) is from that
installation. However, the behavior reflects v8.6.1, so I guess I
am good.
Looks like 'sudo apt-get remove condor' did not clean up these
files from v8.2.3.
Thanks.
-Samik
On 09-Apr-17 4:29 PM, Samik
Raychaudhuri wrote:
Hi,
I recently tried installing HTCondor on a debian VM in google
cloud compute using the UW debian repo. The v8.6.1 installed
fine without any issues. However when I tried starting condor
after installing, it would only start the master daemon and
nothing else. Investigating this further, I found a file
/etc/condor/config.d/00debconf, which has a bunch of
configurations that were trumping the configurations in
/etc/condor/condor_config.
Now, I have installed HTCondor v8.6.1 before from UW debian repo on a
debian VM (running on Virtualbox), and have not noticed this
file. Question: how/when does this show up?
Next, I also noticed a stub /etc/condor/condor_config.local
file, which I haven't seen before. The file has the following
line: "Note that DebConf-generated configuration will overwrite
settings in this file." However, in practice, when I put my
intended configurations in this file, things happily run,
without being overridden by /etc/condor/config.d/00debconf. This is
also evident from the order shown in the MasterLog:
04/09/17 10:47:11 Using config source: /etc/condor/condor_config
04/09/17 10:47:11 Using local config sources:
04/09/17 10:47:11ÂÂÂ /etc/condor/config.d/00debconf
04/09/17 10:47:11ÂÂÂ /etc/condor/condor_config.local
04/09/17 10:47:11 config Macros = 62, Sorted = 62, StringBytes =
1777, TablesBytes = 2288
What gives? Things are running now, but looks puzzling to me.
Regards,
-Samik
|