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

Re: [Condor-users] Condor-C on Windows problem

Re the below -

For something as simple as the scenario you describe, perhaps Condor-C is more than you need?  One idea is your laptop users could submit their jobs with the "-s" (spool) option to condor_submit, and then use the condor_transfer_data (no options needed) command the next day to pull back the results of any of their completed jobs.

Of course, we will still investigate the story with Condor-C on windows, which should work for you...

Todd Tannenbaum
Dept of Computer Sciences
University of Wisconsin-Madison
<-- Sent from a Palm Treo 680 -->

-----Original Message-----

From:  <Greg.Hitchen@xxxxxxxx>
Subj:  [Condor-users] Condor-C on Windows problem
Date:  Tue Jan 30, 2007 8:28 pm
Size:  1K
To:  <condor-users@xxxxxxxxxxx>

We have a working setup of a couple of pools with a few hundred windows
machines with linux Central Managers and linux CondorView Server.

The system is being used OK with users submitting from their own

Thought I'd have a fiddle with Condor-C, primarily for any laptop users
that want to submit jobs to run overnight, so that they can submit, take
their laptop home, and come in the next day to reconnect and collect

My first try reports errors in the submitting PCs SchedLog like:

1/31 11:07:11 Sent ad to central manager for xxxxxx@xxxxxxxx
1/31 11:07:11 Sent ad to 1 collectors for xxxxxx@xxxxxxxx
1/31 11:07:11 ERROR - gridmanager way too old!

and the jobs never get to the remote machines queue.

I have tried using both a linux and windows machine for the remote
queue with the same error on the submitting PC for either case.

Windows running 6.8.3 and linux 6.8.0

Any pointers before I start spending too much time chasing this down?




Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at either