Ok. Check the job manager's log file and see if there are any clues inside.
http://toolkit.globus.org/toolkit/docs/latest-stable/gram5/admin/#idp34869296
<http://toolkit.globus.org/toolkit/docs/latest-stable/gram5/admin/#idp34869296>
> On Nov 3, 2015, at 3:34 PM, Irena Johnson <[email protected]> wrote:
>
> Hi Stu,
>
> Thanks for your feedback. I confirm that the local user's home directory
> exists and is not full.
>
> Regards,
> Irena
>
>
>
> On Tue, Nov 3, 2015 at 4:30 PM, Stuart Martin <[email protected]
> <mailto:[email protected]>> wrote:
> Hi Irena,
>
> Here, it says to check that the local user’s home directory is writable and
> not full. Either of those issues could prevent the job manager process from
> creating files in the mapped user’s home dir and cause this problem.
> http://toolkit.globus.org/toolkit/docs/latest-stable/gram5/user/#gram5-error-codes
>
> <http://toolkit.globus.org/toolkit/docs/latest-stable/gram5/user/#gram5-error-codes>
>
> Cheers,
> Stu
>
>> On Nov 3, 2015, at 2:44 PM, Irena Johnson <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Dear Globus Support,
>>
>> I have installed globus toolkit v. 6 (6.0.1443479657) from source on our
>> RHEL 5.10 system.
>>
>> I have configured different ports for gsiftp and gsigatekeeper (gsiftp6
>> 2194/tcp and
>> gsigatekeeper6 2196/tcp).
>>
>> I am able to run globus-url-copy successfully.
>>
>> I can also run "globusrun -a -r globusserver.pppl.gov:2196
>> <http://globusserver.pppl.gov:2196/>"
>>
>> However, I am getting an error when running:
>>
>> globus-job-run globusserver:2196/jobmanager-fork /bin/date
>> GRAM Job submission failed because the job manager failed to create an
>> internal script argument file (error code 22)
>>
>> I googled this error and found a claim that it occurs when the user does not
>> have a home directory on the gatekeeper.
>>
>> However, this is not the case. Please see below the log:
>>
>> Nov 3 15:40:25 transpgrid1 xinetd[1157]: START: gsigatekeeper6 pid=32725
>> from=192.55.106.70
>> Nov 3 15:40:25 transpgrid1 GRAM-gatekeeper[32725]: globus-gatekeeper
>> pid=32725 starting at Tue Nov 3 15:40:25 2015
>> Nov 3 15:40:25 transpgrid1 GRAM-gatekeeper[32725]: Got connection
>> 192.55.106.70 at Tue Nov 3 15:40:25 2015
>> Nov 3 15:40:25 transpgrid1 GRAM-gatekeeper[32725]: Authenticated globus
>> user: /DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=People/CN=Irena
>> Johnson 1116
>> Nov 3 15:40:25 transpgrid1 GRAM-gatekeeper[32725]: Requested service:
>> jobmanager-fork
>> Nov 3 15:40:25 transpgrid1 GRAM-gatekeeper[32725]: Authorized as local
>> user: tr_ijohnson
>> Nov 3 15:40:25 transpgrid1 GRAM-gatekeeper[32725]: Authorized as local uid:
>> 40491
>> Nov 3 15:40:25 transpgrid1 GRAM-gatekeeper[32725]: and local gid:
>> 28017
>> Nov 3 15:40:25 transpgrid1 xinetd[1157]: EXIT: gsigatekeeper6 status=0
>> pid=32725 duration=0(sec)
>>
>>
>> Could you please advise. Is this a bug? Is there a workaround? Thank you,
>>
>>
>> Irena Johnson
>
>
>
>
>
