[CIG-SHORT] stdout stderr of PBS parallel run

[Brad Aagaard]

Birendra,

The existence of torque/spool is specific to using TORQUE/MAUI as the 
PBS queue system. There are other versions of PBS. You should consult 
your system administrator and/or the PBS documentation for your queue 
system for details if you are not using TORQUE/MAUI.

If you are using TORQUE/MAUI, then I would expect you to be able to see 
the operating system files, such as /usr, on a compute node. The 
directory torque/spool could be in /usr/local or something like that 
depending on how your admin setup the system.

You could run "find / -name spool" on a compute node to find all the 
spool directories and see if any of them are associated with the PBS 
queue system.

Brad


On 3/17/13 1:19 PM, Birendra jha wrote:
> I guess we don't have that utility on our system:
>
> [bjha at login twowaycoupled]$ qpeek -o 65848
> qpeek: Command not found.
>
> Can I install it locally? Is there any other option?
> I also couldn't locate /opt/torque folder. The only folder I can see in the compute node is scratch/ which does not have stdout.
>
> Thanks
> Birendra
>
>
> --- On Sun, 3/17/13, Brad Aagaard <baagaard at usgs.gov> wrote:
>
>> From: Brad Aagaard <baagaard at usgs.gov>
>> Subject: Re: [CIG-SHORT] stdout stderr of PBS parallel run
>> To: cig-short at geodynamics.org
>> Date: Sunday, March 17, 2013, 11:49 PM
>> Yes, use qpeek as Surendra
>> suggested.
>>
>> The stdout and stderr files are usually stored locally on
>> the compute
>> node of process 0 in a directory like /opt/torque/spool.
>> They are copied
>> to the filenames specified in the job parameters when the
>> job completes.
>>
>> Brad
>>
>>
>> On 3/17/13 11:12 AM, surendra at caltech.edu
>> wrote:
>>>
>>> On Mar 17, 2013, at 11:08 AM, Birendra jha <bjha7333 at yahoo.com
>>> <mailto:bjha7333 at yahoo.com>>
>> wrote:
>>>
>>>> Hi
>>>> When I run pylith in parallel using PBS queue
>> system, the stdout.txt
>>>> and stderr.txt are created in the run folder AFTER
>> the run is over. I
>>>> want to see these files during the simulation,
>> especially stdout.txt.
>>>> What option should I use in the pylithapp.cfg?
>>>>
>>>
>>> You can use 'qpeek' to check .err and .out files before
>> the completion
>>> of a run.
>>>
>>>      qpeek -o <jobid>
>>>      qpeek -e <jobid>
>>>
>>>
>>> --Surendra
>>>
>>>
>>> _______________________________________________
>>> CIG-SHORT mailing list
>>> CIG-SHORT at geodynamics.org
>>> http://geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>>>
>>
>> _______________________________________________
>> CIG-SHORT mailing list
>> CIG-SHORT at geodynamics.org
>> http://geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>>
> _______________________________________________
> CIG-SHORT mailing list
> CIG-SHORT at geodynamics.org
> http://geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>