Re: [HTCondor-users] Windows Server 2016 Node claim/held Jobs

[John M Knoeller <johnkn@xxxxxxxxxxx>]

So the jobs failed on Windows server.   This is a problem with the job.  I suspect that a necessary DLL is missing.

You should try using Remote desktop to login to the Windows server box and run the jobs’s program interactively.

That will probably give you some more details about what the problem is.

 

-tj

 

 

From: SCHAPIRA Fernando <fernando.schapira@xxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, April 25, 2019 10:49 AM
To: John M Knoeller <johnkn@xxxxxxxxxxx>; HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: Re: Windows Server 2016 Node claim/held Jobs

 

Lists lots of jobs telling “The job attribute OnExitHold _expression_ ‘exit code!=0”

Total for query 260 jobs 0 comp, 0 rem, 0 idle, 260 held, 0 suspended

 

Thanks,

Fernando

 

Get Outlook for iOS

 

---

From: John M Knoeller <johnkn@xxxxxxxxxxx>
Sent: Thursday, April 25, 2019 17:30
To: HTCondor-Users Mail List
Cc: SCHAPIRA Fernando
Subject: RE: Windows Server 2016 Node claim/held Jobs

 

what does

 

   condor_q -hold

 

return?

 

 

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of SCHAPIRA Fernando via HTCondor-users
Sent: Thursday, April 25, 2019 6:34 AM
To: htcondor-users@xxxxxxxxxxx
Cc: SCHAPIRA Fernando <fernando.schapira@xxxxxxxxxxxxxxxxxxxx>
Subject: [HTCondor-users] Windows Server 2016 Node claim/held Jobs

 

Hi Team,

In a mixed pool configuration > 3 Nodes on Windows 10 and 1 Node on Windows Server 2016 Standard submitted Jobs are nicely claimed on all 4 Nodes.

However Jobs on the Server Node are immediately “held” and won’t run.

 

Kind Regards,
Fernando M. Schapira