[torqueusers] Job stdout/stderr file empty after transfer

Jan Ploski Jan.Ploski at offis.de
Mon Apr 16 10:25:14 MDT 2007

torqueusers-bounces at supercluster.org schrieb am 04/13/2007 03:22:45 PM:

> Hello,
> I am using TORQUE 2.1.6, trying to transfer stdout of a job using the -o 

> option of qsub. Unfortunately, no matter whether I transfer via scp or 
> up $usecp, the transferred file is created with size 0 (zero). When I 
> the option "-k oe" instead, the file remains in $HOME on the execute 
> machine and contains the expected output. Can anyone please explain this 

> or give a tip which log file to inspect or what experiments to perform 
> gather more information?

Solved. The disk with /var/spool/torque on the execute machine was full.

I'd classify it as an error handling bug in TORQUE. We had to strace the 
child process to debug it - shouldn't be necessary.

Best regards -
Jan Ploski

Dipl.-Inform. (FH) Jan Ploski
Betriebliches Informationsmanagement
Escherweg 2  - 26121 Oldenburg - Germany
Fon: +49 441 9722 - 184 Fax: +49 441 9722 - 202
E-Mail: Jan.Ploski at offis.de - URL: http://www.offis.de

More information about the torqueusers mailing list