Hi John, the bug was within a variable for accounting subgroups [1] where I forgot one closing bracket. So in principle, the config should have been not properly closed regarding brackets?? Cheers, Thomas [1] DESYAcctSubGroup = ifThenElse(regexp("desyplt",Owner), "desyplt", \ ifThenElse(regexp("desyprd",Owner), "desyprd", \ ifThenElse(regexp("desysgm",Owner), "desysgm", \ ifThenElse(regexp("desyusr",Owner), "desyusr", \ ifThenElse(regexp("atlas",Owner) && RequestCpus > 1, "atlas_multicore", \ ifThenElse(regexp("cms",Owner) && RequestCpus > 1, "cms_multicore", \ ifThenElse(regexp("lhcb",Owner) && RequestCpus > 1, "lhcb_multicore", \ "other" ))))))) On 2016-06-07 15:47, John M Knoeller wrote: > Condor in general will abort when there is a malformed configuration file. But validation of configuration *values* depends on which daemon looks at them and when. > > Was this a job router configuration value? > > -----Original Message----- > From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Thomas Hartmann > Sent: Tuesday, June 7, 2016 7:18 AM > To: htcondor-users@xxxxxxxxxxx > Subject: Re: [HTCondor-users] Log messages for malformed config files? > > Hi Iain, > > there should be no specific log level set for any of the daemons/subsytems, so in principle default. > > Restarting the condor services in general threw no error messages, so I assumed that the daemons were all up as expected. > > Cheers, > Thomas > > On 2016-06-07 14:03, Iain Bradford Steers wrote: >> Hi Thomas, >> >> Usually, in my experience condor_reconfig has barfed and complained very loudly whenever I've called it with a malformed config file in config.d/. >> >> What's your debug level for MASTER_DEBUG? >> >> Cheers, Iain >> ________________________________________ >> From: HTCondor-users [htcondor-users-bounces@xxxxxxxxxxx] on behalf of >> Thomas Hartmann [thomas.hartmann@xxxxxxx] >> Sent: 07 June 2016 13:54 >> To: HTCondor-Users Mail List >> Subject: [HTCondor-users] Log messages for malformed config files? >> >> Hi all, >> >> I have just stumbled over a malformed config file, that caused >> submitted jobs not to get onto any resources. I.e., I forgot a closing >> bracket in a series of brackets ~~> '... \ "other" ))))))' >> >> I have been looking for log messages, that one could use the next time >> to identify broken configs. However, I have found no error message >> related to the config (or the affected ClassAd) yet. >> >> So, my current guess is that condor daemons skip silently over >> malformed config files? Or maybe some higher log-level is necessary (DEBUG?)? >> >> Cheers, >> Thomas >> >> _______________________________________________ >> 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/ >> > > _______________________________________________ > 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