SGE default config redirects stdout,stderr to the same file twice
See original GitHub issueIt seems like the default configuration sends the stdout and stderr to the same filenames twice. In the config above, qsub is called with -o EG:
e1bd0801-52c1-445c-8513-72e9872a0c7d/call-thing/execution/stdout
In the script that will be executed on the node, there is some shenanigans:
(
cd .../e1bd0801-52c1-445c-8513-72e9872a0c7d/call-thing/execution
bla bla bla my command invocation
) > >(tee '.../e1bd0801-52c1-445c-8513-72e9872a0c7d/call-thing/execution/stdout') 2> >(tee '.../e1bd0801-52c1-445c-8513-72e9872a0c7d/call-thing/execution/stderr' >&2)
Those ‘tees’ are generated by cromwell somewhere, I do not know if the config has control of that. I don’t know the details of what will happen, but I do not think it will be healthy. I smell race conditions. I came across this trying to debug missing log data when SGE aborts a job.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Order of redirecting stderr and stdout to the same file
With yourcmd > file 2>&1 , the standard output is sent to file then stderr is redirected to what the standard output goes,...
Read more >sge_conf(5): Sun Grid Engine config files - Linux man page
sge_conf defines the global and local Sun Grid Engine configurations and can be shown/modified by qconf(1) using the -sconf/-mconf options.
Read more >Ubuntu Manpage: sge_conf - Grid Engine configuration files
The default location for the execution daemon spool directory is $SGE_ROOT/$SGE_CELL/spool. The global configuration entry for this value may be overwritten by ...
Read more >sge_conf.5.txt - HPC @ QMUL
The default location for the execution daemon spool directory is $SGE_ROOT/$SGE_CELL/spool. The global configuration entry for this value may be overwritten by ...
Read more >Sun™ ONE Grid Engine Administration and User's Guide
Installing a Default Sun Grid Engine System for Your Cluster 18 ... one file and the redirections can be specified on a per...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for reporting this, you’re right that those files should not have the same name. The files within the script are meant to capture the stdout and stderr of the user command only and are required for both WDL and CWL support. The files on the
qsub
command line are meant to capture all stdout and stderr including those log messages. The structure of the script has changed somewhat with Cromwell 32 but I suspect this problem still exists so we’ll look at making a fix.thanks guys