[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] EVENT_LOG_JOB_AD_INFORMATION_ATTRS not being honored

Hi Dan,

I use single quotes to avoid escaping issues.

It's the job that DAGMan submits.  The MATCH_EXPRE_JOBGLIDEIN_Site is in the job classad correctly, but not written to the eventlog.  I've also noticed other issues with the EventLog.  For example, for shadow exception events, 
028 (75848.000.000) 07/12 12:10:15 Job ad information event triggered.
MyType = "ShadowExceptionEvent"
TargetType = ""
EventTime = "2010-07-12T12:10:15"
Cluster = 75848
Proc = 0
Subproc = 0
Message = "Can no longer talk to condor_starter <>"
SentBytes = 0.000000
ReceivedBytes = 0.000000
TriggerEventTypeNumber = 7
TriggerEventTypeName = "ULOG_SHADOW_EXCEPTION"
EventTypeNumber = 28

It doesn't output the Owner or the MATCH_EXPR_JOBGLIDEIN_Site.

After changing the JOBGLIDEIN_Site to a more reasonable value:
It seems to be placing the value inside the classads correctly, and in the EventLog for some events.

It all seems to work.  I suppose that means that the original expression was faulty?
JOBGLIDEIN_Site='$$([IfThenElse(IsUndefined(TARGET.GLIDEIN_Site), "Local Job", TARGET.GLIDEIN_Site)])'


On Jul 12, 2010, at 11:33 AM, Dan Bradley wrote:

> Hi Derek,
>> I have EVENT_LOG_JOB_AD_INFORMATION_ATTRS set to include an attributed defined in the condor_config.local: JOBGLIDEIN_Site='$$([IfThenElse(IsUndefined(TARGET.GLIDEIN_Site), "Local Job", TARGET.GLIDEIN_Site)])'
> Do you really have single quotes around the value of JOBGLIDEIN_Site?  I would have expected double quotes.
>> I then have it added to the submit:
>> Finally, I have it added to the event log:
>> EVENT_LOG_JOB_AD_INFORMATION_ATTRS=Owner,CurrentHosts,x509userproxysubject,AccountingGroup,GlobalJobId,QDate,JobStartDate,JobCurrentStartDate,JobFinishedHookDone,MATCH_EXP_JOBGLIDEIN_Site,RemoteHost
>> For 1 user on the system, this all just works, and the MATCH_EXP_JOBGLIDEIN_Site is added to the event log.  For another user, it doesn't include the MATCH_EXP_JOBGLIDEIN_Site, but it includes all other attributes.
>> The one user that it doesn't work for using DAGMAN.  He has no eventlog variables defined in the condor submit file.  condor_config_val -dump reports the eventlog lines above are set correctly, and that condor is reading from the correct config values.
> Is it the scheduler universe DAGMan job itself that lacks MATCH_EXP_JOBGLIDEIN_Site, or is it a job submitted by DAGMan that lacks it?
> I wouldn't expect any scheduler universe job to have MATCH_EXP_JOBGLIDEIN_Site, because no matchmaking takes place for such jobs.  On the other hand, I would expect it to be there for vanilla universe jobs submitted by the DAGMan.
> Also, if you look at the job with condor_history -long, do you see that it is missing both JOBGLIDEIN_Site and MATCH_EXP_JOBGLIDEIN_Site?  Or is it only missing the latter?
> --Dan
> _______________________________________________
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/condor-users/

Attachment: smime.p7s
Description: S/MIME cryptographic signature