It could be any number of things. Are other users able to run jobs on the cluster? When you started the cluster, did you boot the head node completely before booting the cluster nodes?
Other than that, it would probably be an issue with either your user permissions (can you ssh to a node without entering a password?) or your queue script. If you wanted to send your queue script it might help. On Mon, Mar 17, 2008 at 11:10 PM, Chunwei Han <[EMAIL PROTECTED]> wrote: > Hey guys > > Recently I take over the job as the cluster administrator. Unluckily > the former administrator did not leave any documents and I have no > experience at all. Right now the job can not be submitted. Here is > some debugger info: > > # qstat > Job id Name User Time Use S Queue > ---------------- ---------------- ------------------ -------- - ----- > 21205.parellel bdimer vuser 0 Q workq > 21207.parellel gram0 vuser 0 Q workq > > # tracejob -n 10 21205 > > Job: 21205.parellel > > 03/17/2008 22:23:13 S Job Queued at request of [EMAIL PROTECTED], > owner = [EMAIL PROTECTED], job name = bdimer, queue = workq > 03/17/2008 22:23:13 A queue=workq > > > So, how to make it run? > The version of OSCAR is 3.0 > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Oscar-users mailing list > Oscar-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oscar-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Oscar-users mailing list Oscar-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-users
