[torqueusers] Torque 1.1.0p6 failing with "Command not found"
weage98 at yahoo.com
Wed Feb 16 10:20:26 MST 2005
Thanks for the reply. Actually, I just solved the problem.
RHEL has a problem with the audit daemon filling up the local disk,
which is what just happened on my workstation. I'm not sure how that
resulted in a submitted, but empty, job script. Is there something
here that qsub should be checking for?
--- Garrick Staples <garrick at usc.edu> wrote:
> On Wed, Feb 16, 2005 at 08:49:26AM -0800, Joshua Weage alleged:
> > I've recently upgraded to 1.1.0p6, which solved a lot of problem I
> > experiencing with 1.1.0p2. However, torque has stopped working
> > completely today. I have restarted moms, server and scheduler and
> > still get the same error.
> > All of my torque jobs now fail with the following error in the
> > file:
> > /var/spool/torque/mom_priv/jobs/477.warlns2.SC: Command not found.
> Assuming the "#!" line is correct, you have DOS EOL characters in
> your job
> script. Something like 'dos2unix' can fix that up.
> Btw, the forthcoming 1.2.0p1 will translate DOS EOL characters
> Garrick Staples, Linux/HPCC Administrator
> University of Southern California
> ATTACHMENT part 1.2 application/pgp-signature
> torqueusers mailing list
> torqueusers at supercluster.org
Do you Yahoo!?
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
More information about the torqueusers