1condor_advertise(1) General Commands Manual condor_advertise(1)
2
6 condor_advertiseSend a ClassAd to the condor_collectordaemon
7
9 condor_advertise[-help | -version]
10 condor_advertise[-pool centralmanagerhostname[:portname]] [-debug]
12 [-tcp] [-udp] [-multiple] [update-command [classad-filename]]
13
15 condor_advertisesends one or more ClassAds to the condor_collectordae‐
16 mon on the central manager machine. The optional argument update-com‐
17 mandsays what daemon type's ClassAd is to be updated; if it is absent,
18 it assumed to be the update command corresponding to the type of the
19 (first) ClassAd. The optional argument classad-filenameis the file from
20 which the ClassAd(s) should be read. If classad-filenameis omitted or
21 is the dash character ('-'), then the ClassAd(s) are read from standard
22 input. You must specify update-commandif you do not want to read from
23 standard input.
24 When -multipleis specified, multiple ClassAds may be published. Pub‐
26 lishing many ClassAds in a single invocation of condor_advertiseis more
27 efficient than invoking condor_advertiseonce per ClassAd. The ClassAds
28 are expected to be separated by one or more blank lines. When -multi‐
29 pleis not specified, blank lines are ignored (for backward compatibil‐
30 ity). It is best not to rely on blank lines being ignored, as this may
31 change in the future.
32 The update-commandmay be one of the following strings:
34 UPDATE_STARTD_AD
36 UPDATE_SCHEDD_AD
42 UPDATE_MASTER_AD
48 UPDATE_GATEWAY_AD
54 UPDATE_CKPT_SRVR_AD
60 UPDATE_NEGOTIATOR_AD
66 UPDATE_HAD_AD
72 UPDATE_AD_GENERIC
78 UPDATE_SUBMITTOR_AD
84 UPDATE_COLLECTOR_AD
90 UPDATE_LICENSE_AD
96 UPDATE_STORAGE_AD
102 condor_advertisecan also be used to invalidate and delete ClassAds cur‐
108 rently held by the condor_collectordaemon. In this case the update-com‐
109 mandwill be one of the following strings:
110 INVALIDATE_STARTD_ADS
112 INVALIDATE_SCHEDD_ADS
118 INVALIDATE_MASTER_ADS
124 INVALIDATE_GATEWAY_ADS
130 INVALIDATE_CKPT_SRVR_ADS
136 INVALIDATE_NEGOTIATOR_ADS
142 INVALIDATE_HAD_ADS
148 INVALIDATE_ADS_GENERIC
154 INVALIDATE_SUBMITTOR_ADS
160 INVALIDATE_COLLECTOR_ADS
166 INVALIDATE_LICENSE_ADS
172 INVALIDATE_STORAGE_ADS
178 For any of these INVALIDATE commands, the ClassAd in the required file
184 consists of three entries. The file contents will be similar to:
185 MyType = "Query"
187 TargetType = "Machine"
188 Requirements = Name == "condor.example.com"
189 The definition for MyTypeis always Query. TargetTypeis set to the
191 MyTypeof the ad to be deleted. This MyTypeis DaemonMasterfor the con‐
192 dor_masterClassAd, Machinefor the condor_startdClassAd, Schedulerfor
193 the condor_scheddClassAd, and Negotiatorfor the condor_negotiatorClas‐
194 sAd. Requirementsis an expression evaluated within the context of ads
195 of TargetType. When Requirementsevaluates to True, the matching ad is
196 invalidated. A full example is given below.
197
199 -help
200 Display usage information
202 -version
206 Display version information
208 -debug
212 Print debugging information as the command executes.
214 -multiple
218 Send more than one ClassAd, where the boundary between ClassAds is
220 one or more blank lines.
221 -pool centralmanagerhostname[:portname]
225 Specify a pool by giving the central manager's host name and an
227 optional port number. The default is the COLLECTOR_HOSTspecified in
228 the configuration file.
229 -tcp
233 Use TCP for communication. Used by default if UPDATE_COLLEC‐
235 TOR_WITH_TCPis true.
236 -udp
240 Use UDP for communication.
242
246 The job and machine ClassAds are regularly updated. Therefore, the
247 result of condor_advertiseis likely to be overwritten in a very short
248 time. It is unlikely that either HTCondor users (those who submit jobs)
249 or administrators will ever have a use for this command. If it is
250 desired to update or set a ClassAd attribute, the condor_config_valcom‐
251 mand is the proper command to use.
252 Attributes are defined in Appendix A of the HTCondor manual.
254 For those administrators who do need condor_advertise, the following
256 attributes may be included:
257 DaemonStartTime
259 UpdateSequenceNumber
265 If both of the above are included, the condor_collectorwill automati‐
271 cally include the following attributes:
272 UpdatesTotal
274 UpdatesLost
280 UpdatesSequenced
286 UpdatesHistory
292 Affected by COLLECTOR_DAEMON_HISTORY_SIZE.
294
298 Assume that a machine called condor.example.com is turned off, yet its
299 condor_startdClassAd does not expire for another 20 minutes. To avoid
300 this machine being matched, an administrator chooses to delete the
301 machine's condor_startdClassAd. Create a file (called remove_filein
302 this example) with the three required attributes:
303 MyType = "Query"
305 TargetType = "Machine"
306 Requirements = Name == "condor.example.com"
307 This file is used with the command:
309 % condor_advertise INVALIDATE_STARTD_ADS remove_file
311
313 condor_advertisewill exit with a status value of 0 (zero) upon success,
314 and it will exit with the value 1 (one) upon failure. Success means
315 that all ClassAds were successfully sent to all condor_collectordae‐
316 mons. When there are multiple ClassAds or multiple condor_collectordae‐
317 mons, it is possible that some but not all publications succeed; in
318 this case, the exit status is 1, indicating failure.
319
321 Center for High Throughput Computing, University of Wisconsin-Madison
322
324 Copyright (C) 1990-2019 Center for High Throughput Computing, Computer
325 Sciences Department, University of Wisconsin-Madison, Madison, WI. All
326 Rights Reserved. Licensed under the Apache License, Version 2.0.
327 date condor_advertise(1)