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

Re: [Condor-users] Args not found (condor-c)

It turns out that Ryan's problem is indeed an incompatibility between a Condor 6.7.18 schedd sending Condor-C jobs to a 6.7.14 and prior schedds, but only when the destination schedd is specified by IP:port instead of by name. This resulted in the sender not knowing the version of the receiver and doing the wrong thing. I hope to have this fixed in 6.7.20.


On May 4, 2006, at 2:51 AM, Ryan Garver wrote:

I am having trouble with backwards compatibility with JobAds being
forwarded through Condor-C.  When the job reaches the destination
startd and a starter is spawned to handle it the starter promptly
fails with the error:

5/4 00:45:56 Starting a VANILLA universe job with ID: 2419.0
5/4 00:45:56 Args not found in JobAd.  Aborting OsProc::StartJob.
5/4 00:45:56 Failed to start job, exiting
5/4 00:45:56 ShutdownFast all jobs.
5/4 00:45:56 **** condor_starter (condor_STARTER) EXITING WITH STATUS 0

The job is then marked back as idle and retried in the negotiation cycle.

The job looks like:
universe = grid
executable = pi-compute
arguments = 5000000
output = out.$(Process)
log = log.$(Process)
grid_resource = $$(Resource)
remote_grid_resource = $$(RemoteResource)
remote_universe = grid
+remote_remote_jobuniverse = 5
queue 1

In the first queue (6.7.18):
Args = "5000000"

To a 6.7.18 queue via condor-c:
Arguments = "5000000"
Environment = ""

Then on to 6.7.14 via condor-c:
Arguments = "5000000"
Environment = ""

Any help is appreciated.

Ryan Garver

Condor-users mailing list