Hello!
Thank you, Martin!
It worked. Changing the config file solved the problem.
aus...@zone2:~ $ globusrun-ws -submit -f echo_job.xml
Submitting job...Done.
Job ID: uuid:c0983efa-6635-11df-bc78-010000003910
Termination time: 05/23/3010 06:38 GMT
Current job state: Active
Current job state: CleanUp
Current job state: Done
Destroying job...Done.
As I read '...something went wrong during the installation...' I
remembered a warning generated by 'make install':
[...]
Reading gatekeeper configuration file...
Warning: Host cert file: /etc/grid-security/hostcert.pem not found. Re-run
setup-globus-gram-job-manager after installing host cert file.
Determining system information...
Creating job manager configuration file...
Done
..Done
I thought, this might be the problem with the not fully generated config
file. But rerunning setup-globus-gram-job-manager unfortunally did not
solve the problem.
But as it works now, I am happy. I am going to spend a little time later
- perhaps I am going to find the problem ... ;)
Thanks again :)
Joerg
On 22.05.2010 15:10 , Martin Feller wrote:
> Hi,
>
>
>> I didn't touch the file after building and installing Globus from
>> source. GridFTP itself works fine.
>>
> The GridFTP server does not use this file.
>
>
>> As far as I understood it, this file
>> is used for staging but staging isn't (explicitly) used in my job
>> definition. Is there an implicit staging regarding stdout and stderr?
>>
> It is also used to determine paths for files specified in <stdout> and
> <stderr> elements of your job descriptrion.
> It's quite a while ago that I worked on ws-gram and I actually never
> touched this aspect, so please don't ask me 'Why?'...
>
>
>> I followed the posted link about GRAM4 and GridFTP file system mapping.
>> My $GLOBUS_LOCATION/etc/globus_wsrf_gram/globus_gram_fs_map_config.xml
>> exists but looks quite different than the mentioned default entry:
>>
>> aus...@zone2:/usr/local/globus-4.2.1/etc/globus_wsrf_gram $ cat
>> globus_gram_fs_map_config.xml
>> <?xml version="1.0" encoding="UTF-8"?>
>> <fileSystemMaps
>> targetNamespace="http://www.globus.org/namespaces/2008/03/gram/job";>
>> </fileSystemMaps>
>>
> Hm, something went wrong during the installation, i think.
> Looks like the file wasn't generated properly in the post-install phase,
> fileSystemMaps shouldn't be empty. In any case it shouldn't be required
> to generate the mappings yourself after an installation.
>
> But...
>
>
>> I changed it to:
>> aus...@zone2:/usr/local/globus-4.2.1/etc/globus_wsrf_gram $ cat
>> globus_gram_fs_map_config.xml
>> <?xml version="1.0" encoding="UTF-8"?>
>> <fileSystemMaps
>> targetNamespace="http://www.globus.org/namespaces/2008/03/gram/job";>
>> </fileSystemMaps>
>> <map>
>> <scheduler>Fork</scheduler>
>> <ftpServer>
>> <protocol>gsiftp</protocol>
>> <host>zone2.all</host>
>> <port>2811</port>
>> </ftpServer>
>> <mapping>
>> <jobPath>/</jobPath>
>> <ftpPath>/</ftpPath>
>> </mapping>
>> </map>
>>
>>
> I get the same error like you with your file. The reason is that it's not
> schema-compliant xml: The map element must be wrapped by the fileSystemMaps
> element, like
>
> <?xml version="1.0" encoding="UTF-8"?>
> <fileSystemMaps
> targetNamespace="http://www.globus.org/namespaces/2008/03/gram/job";>
> <map>
> <scheduler>Fork</scheduler>
> <ftpServer>
> <protocol>gsiftp</protocol>
> <host>zone2.all</host>
> <port>2811</port>
> </ftpServer>
> <mapping>
> <jobPath>/</jobPath>
> <ftpPath>/</ftpPath>
> </mapping>
> </map>
> </fileSystemMaps>
>
> Try this and it *should* work.
>
> Martin
>
>
>> Unfortunally that did not solve the problem. Same error about "invalid
>> stdout element".
>>
>> Joerg
>>
>> On 22.05.2010 5:26 , Martin Feller wrote:
>>
>>> Hi,
>>>
>>> Very probably something is wrong with your file system mapping file.
>>>
>>> Some information about the file system mapping:
>>> http://www.globus.org/toolkit/docs/4.2/4.2.1/execution/gram4/admin/#gram4-Interface_Config_Frag-filesysmap
>>>
>>> Does $GLOBUS_LOCATION/etc/globus_wsrf_gram/globus_gram_fs_map_config.xml
>>> exist?
>>> Did you modify it and it's maybe broken?
>>>
>>> Martin
>>>
>>> Jörg Lenhardt wrote:
>>>
>>>
>>>> Hello!
>>>>
>>>> I build Globus TK 4.2.1 on Solaris 10 (SPARC) and till now everything
>>>> worked fine. But if I try to submit a WS GRAM job using a job definition
>>>> file, the execution fails with the error message: "Invalid stdout
>>>> element. File map initialization failed."
>>>>
>>>> Job definition:
>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>> <job>
>>>> <executable>/bin/echo</executable>
>>>> <argument>Output</argument>
>>>> <stdout>${GLOBUS_USER_HOME}/stdout</stdout>
>>>> <stderr>${GLOBUS_USER_HOME}/stderr</stderr>
>>>> </job>
>>>>
>>>> Job execution:
>>>> aus...@zone2:~ $ globusrun-ws -submit -f echo_job.xml
>>>> Submitting job...Done.
>>>> Job ID: uuid:4a9df2dc-6444-11df-ac26-010000006cc8
>>>> Termination time: 05/20/3010 19:17 GMT
>>>> Current job state: Failed
>>>> Destroying job...Done.
>>>> globusrun-ws: Job failed: Invalid stdout element. File map
>>>> initialization failed.
>>>>
>>>> Globus container output:
>>>> 2010-05-20T21:17:12.237+02:00 INFO
>>>> PersistentManagedExecutableJobResource.4aca2640-6444-11df-80ff-8db553e71ea8
>>>> [ServiceThread-58,start:761] Job 4aca2640-6444-11df-80ff-8db553e71ea8
>>>> with client submission-id 4a9df2dc-6444-11df-ac26-010000006cc8 accepted
>>>> for local user 'auser1'
>>>> 2010-05-20T21:17:13.752+02:00 INFO handler.SubmitStateHandler
>>>> [pool-1-thread-5,process:172] Job 4aca2640-6444-11df-80ff-8db553e71ea8
>>>> submitted with local job ID '4bd68876-6444-11df-bc23-010000007edd:6912'
>>>> 2010-05-20T21:17:17.191+02:00 INFO
>>>> handler.FinalizeTerminationStateHandler
>>>> [pool-1-thread-3,handleFailedState:100] Job
>>>> 4aca2640-6444-11df-80ff-8db553e71ea8 failed. Fault #1: Description:
>>>> Invalid stdout element. File map initialization failed. Cause:
>>>> org.globus.exec.generated.ServiceLevelAgreementFaultType: Invalid stdout
>>>> element. File map initialization failed. caused by [0:
>>>> org.oasis.wsrf.faults.BaseFaultType: File map initialization failed. ]
>>>>
>>>> The files stdout and stderr ARE created and stdout contains "Output".
>>>>
>>>> The following works fine without an error.
>>>> aus...@zone2:~ $ globusrun-ws -submit -c /bin/touch /tmp/file
>>>>
>>>> I really do not know what's wrong.
>>>>
>>>> Some information about the environment:
>>>>
>>>> - Using a Solaris Zone for Globus
>>>> - perl is installed in /usr/local/ with XML::Parser
>>>> - PATH is set to search /usr/local/bin before any other path (global in
>>>> /etc/profile)
>>>> - sudo is configured
>>>> globus ALL=(auser1) NOPASSWD:
>>>> /usr/local/globus-4.2.1/libexec/globus-gridmap-and-execute -g
>>>> /etc/grid-security/grid-mapfile
>>>> /usr/local/globus-4.2.1/libexec/globus-job-manager-script.pl *
>>>> globus ALL=(auser1) NOPASSWD:
>>>> /usr/local/globus-4.2.1/libexec/globus-gridmap-and-execute -g
>>>> /etc/grid-security/grid-mapfile
>>>> /usr/local/globus-4.2.1/libexec/globus-gram-local-proxy-tool *
>>>>
>>>> Hope anyone could guide me out of the darkness ... ;)
>>>>
>>>> Joerg Lenhardt
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>
