| T O P I C R E V I E W |
| clithero |
Posted - Nov 15 2007 : 10:29:11 AM
Some of my scripts are not working and the bugs are eluding me. Is there some reason not all of my scripts are outputting log files?
Thanks,
John |
| 10 L A T E S T R E P L I E S (Newest First) |
| syam.gadde |
Posted - Jan 07 2008 : 12:44:09 PM
Just to clarify Dharol's observation. It's not only that -v is necessary for scripts that access data on BIAC file servers -- it's that if you are specifying a variable to qsub (like EXPERIMENT=Dummy.01), you do that on the command line by using -v, so
in:
qsub -v EXPERIMENT=Dummy.01 ...
-v must be right before EXPERIMENT=Dummy.01 |
| tankersley |
Posted - Jan 07 2008 : 12:29:55 PM
FYI, the problem appears to have been that the flag -v is required to run any script.
dharol |
| dvsmith |
Posted - Jan 04 2008 : 4:38:03 PM
I was having exit code "1" pop up when node6 wasn't working earlier today, but I thought that was fixed. If your jobs are going to node6 (should be able tell from the email) and you're not getting a log file, try a different node.
qsub -l hostname=node7 -v EXPERIMENT=whateverexp whateverscript.sh |
| tankersley |
Posted - Jan 04 2008 : 3:50:18 PM
I am trying to get my first cluster script running. I have run sh -n script.sh on it and do not get any error messages.
I've also inserted the echo "GOT HERE" command as the first line in USER SCRIPT, but the job never gets to this portion of the script.
Also, the job keeps exiting with exit code "1", which means(?) that I'm misusing a built-in shell command.
Any help appreciated.
Thanks,
Dharol |
| josh.bizzell |
Posted - Nov 29 2007 : 09:55:28 AM
We did not update FSL to 4.0.2 on the cluster just yet; we're waiting to make sure it is completely bug-free before doing that.
This error seems to have been caused by a change in the configuration we made to the grid engine late yesterday. We've reverted back to the original setting and now it seems to work.
-Josh |
| Carpenter |
Posted - Nov 28 2007 : 5:49:31 PM
I just got the same error... |
| wang |
Posted - Nov 28 2007 : 5:38:41 PM
Does anyone have problem with running scripts in the Cluster now? A script that worked previously does not work now. Here is the error message for the Log file:
Tcl_InitNotifier: unable to start notifier thread
Have we already upgraged fsl to 4.0.2? Thanks. |
| deshmukh |
Posted - Nov 15 2007 : 11:55:58 AM
I was able to submit a job to the cluster without problems so the cluster is accepting jobs. The node7 problem was related to experiment access and is fixed now. |
| clithero |
Posted - Nov 15 2007 : 11:37:00 AM
Thanks, I will use that check.
However, it appears that the cluster may not be accepting new jobs. Multiple people have tried running scipts that worked fine before, but now are not running. Node 7 in particular. The jobs seem to run for about 5 minutes and then quit without error. The scripts themselves are (as far as I can tell) bug free. |
| deshmukh |
Posted - Nov 15 2007 : 10:49:45 AM
Are you having problems with multiple jobs using the same script i.e. some of the jobs using the script run ok but others fail or are these different scripts ?
You might want to do a basic syntax check on scripts by running
sh -n script
If the script passes that test without errors, then check to see if all the data is in the expected location. This tends to be the most common issue.
The job level log files are generated on job completion. If the job dies due to command errors (usually generated by incorrect paths) then these files are never generated. You can however debug scripts by adding your own debug messages in the "USER SCRIPT" section to a specific file in your Experiment folder. For eg. here is the most common debug message,
echo "GOT HERE" >> $EXPERIMENT/Analysis/Logs/debug.txt
You can always add your own tags to messages so you can identify which job generated a particular message eg:
echo " $EXAM_NUMBER : Running feat" >> $EXPERIMENT/Analysis/Logs/debug.txt
|
