Difference between revisions of "Tools/Manuals/TS77"
< Tools
Jump to navigation
Jump to search
(Created page with '{{TOC_right}} Category:FAQ ------ Back to Troubleshooting Guide ------ = GRAM Job submission failed because the job manager failed to …') |
|||
Line 1: | Line 1: | ||
{{Template:Op menubar}} | |||
{{Template:Doc_menubar}} | |||
[[Category:Operations Manuals]] | |||
{{TOC_right}} | {{TOC_right}} | ||
------ | ------ | ||
Back to [[Tools/Manuals/SiteProblemsFollowUp|Troubleshooting Guide]] | Back to [[Tools/Manuals/SiteProblemsFollowUp|Troubleshooting Guide]] |
Latest revision as of 13:47, 23 November 2012
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
Back to Troubleshooting Guide
GRAM Job submission failed because the job manager failed to open stderr (error code 74)
Full message
$ globus-job-run some-CE.domain /bin/hostname GRAM Job submission failed because the job manager failed to open stderr (error code 74)
Diagnosis
The UI does not have inbound connectivity for the GLOBUS_TCP_PORT_RANGE as defined on the UI.
Note: globus-job-run should only be used for tests, because for each job it causes a process to run on the CE until the job has exited.
Solution
- Set GLOBUS_TCP_PORT_RANGE appropriately.
- Fix firewall(s).
- Define GLOBUS_HOSTNAME as the fully qualified external hostname in case the hostname command returns a short or local name for the host.