Hi ToddM (and everyone else!) On 8/13/25 15:53, Todd L Miller via HTCondor-users wrote:
ÂÂÂÂHTCondor doesn't record its own address(es) in hard (on-disk) state, but -- my impression is -- a lot of the associated "soft" state can only be reset by restarting the daemon(s).
yeah, that seems to be right as a full service restart always seems to fix this issue.
ÂÂÂÂIt sounds like you intend for this installation be rootly; if is, you should never have a reason to specify :0 anywhere, or indeed, any port number at all; HTCondor will assume 9618. This may be a consequence of starting HTCondor before the config management system is done (that is, it may not be in your config at all); if so, that may be another reason to delay start-up until the configuration is complete.I've worked around this issue now by systemd-masking the condor service before its first install and only unmask it once our configuration is present.
Thanks a lot for the feedback (and for the now released Debian trixie 24LTS packages!)
Cheers CarstenPS: Probably unnecessary as hardly anyone seems to use saltstack for config management, but for us, it looks somewhat shortened like this:
condor packages: pkg.installed: - pkgs: - condorcondor service masked before first start-up: service.masked: - name: condor # kind of wonky test if we are already configured - unless: grep -q Atlas /etc/condor/condor_config - require_in:- pkg: condor packages[...setting up all of our configuration bits and pieces...]
condor-base-install: service.running: - name: condor - enable: True - reload: True - unmask: True - unmask_runtime: True - watch: - file: /etc/condor/condor_config -- Dr. Carsten Aulbert, Max Planck Institute for Gravitational Physics, CallinstraÃe 38, 30167 Hannover, Germany, Phone +49 511 762 17185
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature