FAQ
From FarmShare
Contents |
Frequently Asked Questions
tset: standard error: Invalid argument
In your job script, you probably don't explicitly specify which shell to use. Probably your default shell is csh and your csh startup scripts are getting loaded and something there is generating that error because the job is not run under an interactive session. So the solution is to either specify a shell on the first line of your job script in the usual Unix way e.g.
#!/bin/bash
or else use the -S flag to qsub, e.g.
# get rid of spurious messages about tty/terminal types #$ -S /bin/sh
tty errors
You may see things like
tset: standard error: Invalid argument Undefined tty stdin: is not a tty
or
Warning: no access to tty (Bad file descriptor). Thus no job control in this shell.
See the question above, and specify a shell. See the 'shell_start_mode' section of 'man sge_conf' for more info.
error: can't open output file "/afs/ir/users/c/h/chekh/YYY.oXXXX"
Check that you have your Kerberos credentials and AFS tokens per AFS
glusterfs: Transport endpoint not connected
"/mnt/glusterfs: Transport endpoint is not connected." This indicates a network or connection problem for the shared filesystem, please report this to the barley-alpha list or via HelpSU.
