Mailing List ArchivesAuthenticated access |
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesAuthenticated access |
|
On Mar 30, 2012, at 1:21 PM, Spuds wrote: I inherited a cluster of condor machines. I don't know anything about condor and I have a mess on my hands. I think that's a hard question because each person has their own "no-nonsense" needs. The Condor manual is really more of a reference manual than an easy setup guide, that's for sure. You might find past tutorials to be helpful in getting you up to speed, though they aren't straightforward "easy setup guides". One example if our Condor administration tutorial. Last year's can be found at: Three years ago, we had a video made of the Condor administration tutorial. While that's out of date, the basics really haven't changed. If you prefer video to reading, you can check it out: We have 3 windows hosts and a linux host, and I'm having all kinds of issues. Some of them I have solved, others still exist. That sounds like Condor isn't running on that computer. How did you start up Condor? What do the following commands print? condor_config_val -v DAEMON_LIST ps faux | grep condor 2) Jobs get submitted to the cluster and then show up as "held" and never do anything. You can find out why the jobs are held, though it's harder than it should be to get reasons. On the computer from which you submitted the jobs: condor_q -hold JOB_ID condor_q -l JOB_ID | grep -i hold 3) I get all kinds of errors in the Collector Log on what is supposed to be the master: Something could be down. Try those commands I suggested above: condor_config_val -v DAEMON_LIST ps faux | grep condor But I have no problems joining other machines to the cluster. There are several. I'm aware of Cycle Computing: -alain |