1condor_advertise(1)         General Commands Manual        condor_advertise(1)
2
3
4

Name

6       condor_advertiseSend a ClassAd to the condor_collectordaemon
7

Synopsis

9       condor_advertise[-help | -version]
10
11       condor_advertise[-pool    centralmanagerhostname[:portname]]   [-debug]
12       [-tcp] [-udp] [-multiple] [update-command [classad-filename]]
13

Description

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
25       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
33       The update-commandmay be one of the following strings:
34
35       UPDATE_STARTD_AD
36
37
38
39
40
41       UPDATE_SCHEDD_AD
42
43
44
45
46
47       UPDATE_MASTER_AD
48
49
50
51
52
53       UPDATE_GATEWAY_AD
54
55
56
57
58
59       UPDATE_CKPT_SRVR_AD
60
61
62
63
64
65       UPDATE_NEGOTIATOR_AD
66
67
68
69
70
71       UPDATE_HAD_AD
72
73
74
75
76
77       UPDATE_AD_GENERIC
78
79
80
81
82
83       UPDATE_SUBMITTOR_AD
84
85
86
87
88
89       UPDATE_COLLECTOR_AD
90
91
92
93
94
95       UPDATE_LICENSE_AD
96
97
98
99
100
101       UPDATE_STORAGE_AD
102
103
104
105
106
107       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
111       INVALIDATE_STARTD_ADS
112
113
114
115
116
117       INVALIDATE_SCHEDD_ADS
118
119
120
121
122
123       INVALIDATE_MASTER_ADS
124
125
126
127
128
129       INVALIDATE_GATEWAY_ADS
130
131
132
133
134
135       INVALIDATE_CKPT_SRVR_ADS
136
137
138
139
140
141       INVALIDATE_NEGOTIATOR_ADS
142
143
144
145
146
147       INVALIDATE_HAD_ADS
148
149
150
151
152
153       INVALIDATE_ADS_GENERIC
154
155
156
157
158
159       INVALIDATE_SUBMITTOR_ADS
160
161
162
163
164
165       INVALIDATE_COLLECTOR_ADS
166
167
168
169
170
171       INVALIDATE_LICENSE_ADS
172
173
174
175
176
177       INVALIDATE_STORAGE_ADS
178
179
180
181
182
183       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
186       MyType = "Query"
187       TargetType = "Machine"
188       Requirements = Name == "condor.example.com"
189
190       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

Options

199       -help
200
201          Display usage information
202
203
204
205       -version
206
207          Display version information
208
209
210
211       -debug
212
213          Print debugging information as the command executes.
214
215
216
217       -multiple
218
219          Send  more  than one ClassAd, where the boundary between ClassAds is
220          one or more blank lines.
221
222
223
224       -pool centralmanagerhostname[:portname]
225
226          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
230
231
232       -tcp
233
234          Use  TCP  for  communication.  Used  by  default  if  UPDATE_COLLEC‐
235          TOR_WITH_TCPis true.
236
237
238
239       -udp
240
241          Use UDP for communication.
242
243
244

General Remarks

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
253       Attributes are defined in Appendix A of the HTCondor manual.
254
255       For those administrators who do need  condor_advertise,  the  following
256       attributes may be included:
257
258       DaemonStartTime
259
260
261
262
263
264       UpdateSequenceNumber
265
266
267
268
269
270       If  both  of the above are included, the condor_collectorwill automati‐
271       cally include the following attributes:
272
273       UpdatesTotal
274
275
276
277
278
279       UpdatesLost
280
281
282
283
284
285       UpdatesSequenced
286
287
288
289
290
291       UpdatesHistory
292
293          Affected by COLLECTOR_DAEMON_HISTORY_SIZE.
294
295
296

Examples

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
304       MyType = "Query"
305       TargetType = "Machine"
306       Requirements = Name == "condor.example.com"
307
308       This file is used with the command:
309
310       % condor_advertise INVALIDATE_STARTD_ADS remove_file
311

Exit Status

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

Author

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
328
329
330                                     date                  condor_advertise(1)
Impressum