[gridshib-user] Globusrun-ws Question

[Von Welch]

Addressing your second issue:

> makes an error complaining 'no passwd entry for user1' though it  
> works fine when
> a user 'vmware' is at the first line in the file like

Does 'user1' have an entry in /etc/passwd and /etc/shadow? I.e. you  
can log into the 'user1' account successfully outside of GT?

Von


On Feb 8, 2007, at 9:40 AM, Wonjun Lee wrote:

> Wow! it works fine! Great..
> Thank you Von.
>
> After deleting globus-gridmap-and-execute command from the sudoers  
> file, the
> gram job could be submitted from the client and the output was in  
> the gatekeeper
> server.
>
> By the way, only the first user in the attr-authz.xml file is  
> recognized, why
> not the others?
> I mean, in my attr-authz.xml file, the configuration
> ------------------------------------------
> <listOfUsername>
>     <username>user1</username>
>     <username>vmware</username>
>                   *
>                   *
> </listOfUsername>
> -------------------------------------------
> makes an error complaining 'no passwd entry for user1' though it  
> works fine when
> a user 'vmware' is at the first line in the file like
> --------------------------------------------
> <listOfUsername>
>     <username>vmware</username>
>     <username>user1</username>
>                   *
>                   *
> </listOfUsername>
> ----------------------------------------------
>
> Thank you,
> Wonjun
>
>
> 인용 Von Welch <vwelch at ncsa.uiuc.edu>:
>
>>
>> Wonjun,
>>
>>   For accounts that are authorized via attributes as opposed to grid-
>> mapfile, one needs to remove the globus-gridmap-and-execute command
>> from the /etc/sudoer's configuration. E.g.:
>>
>> globus  ALL=(commacct) NOPASSWD: /usr/local/gt-4.0.3/libexec/globus-
>> job-manager-script.pl *
>>
>> This is missing in the documentation and I've opened a bug (4999)  
>> on it.
>>
>> Von
>>
>> On Feb 7, 2007, at 2:33 PM, Wonjun Lee wrote:
>>
>>> Tom,
>>>
>>> It's weired since before installing gridshib, it worked fine in a
>>> same command,
>>> "globusrun-ws -submit -S -f test_multi.xml" making a output file in
>>> the remote site.
>>> Every settings of sudoers seemed okay (break between two lines).
>>>
>>> I put a same user name, vmware (gatekeepr's account=nanoHUB user
>>> name which is
>>> in the sudoers) in the attr-authz.xml file of gram-service. Also
>>> the location of
>>> the globus-job-manager-script.pl is located all right.
>>>
>>> My sudoers looks like,
>>>
>>> globus ALL=(vmware, wlee) NOPASSWD:
>>> /opt/globus/libexec/globus-gridmap-and-execute -g
>>> /etc/grid-security/grid-mapfile /opt/globus/libexec/globus-job-
>>> manager-script.pl *
>>> globus ALL=(vmware, wlee) NOPASSWD:
>>> /opt/globus/libexec/globus-gridmap-and-execute -g
>>> /etc/grid-security/grid-mapfile /opt/globus/libexec/globus-gram-
>>> local-proxy-tool *
>>>
>>> The error message looks like,
>>>
>>> Delegating user credentials...Done
>>> Submitting job...Done
>>> Job ID: uuid:edd43......
>>> Termination time: .....
>>> Current job state: Failed
>>> Destroying job...Done
>>> Cleaning up ...Done
>>> globusrun-ws: Job failed: Error code: 200
>>> Sudo is misconfigured to run the globus-job-manager-script.pl
>>> script for user
>>> vmware.
>>>
>>> Thank you,
>>> Wonjun
>>>
>>> 인용 Tom Scavo <trscavo at gmail.com>:
>>>
>>>> Wonjun,
>>>>
>>>> Please refer to this message:
>>>>
>>>> http://www.globus.org/mail_archive/gt-user/2006/09/msg00107.html
>>>>
>>>> Subsequent messages in the thread give explicit suggestions for
>>>> troubleshooting your problem.
>>>>
>>>> Hope this helps,
>>>> Tom
>>>>
>>>> On 2/6/07, Wonjun Lee <wlee at purdue.edu> wrote:
>>>>> Hi Tom,
>>>>>
>>>>> I checked another webservice (coutner-client) is properly working
>>>>> all right
>>>> in a
>>>>> gridshib embedded system. The container log file had a user  
>>>>> name and
>>>> attributes
>>>>> giving acceptance to a user.
>>>>> For the case of running simple globusrun-ws program, I configured
>>>>> files in
>>>> the
>>>>> "GLOBUS_LOCATION/etc/gram-service" same as the others. Is it
>>>>> right way but
>>>> I met
>>>>> a following error,
>>>>>
>>>>> Delegating user credentials...Done.
>>>>> Submitting job...Done
>>>>> Job ID: uuid:0f76cb.....
>>>>> Termination time: 02/07/2007 21:50 GMT
>>>>> Current job state: Failed
>>>>> Destroying job...Done.
>>>>> Cleaning up any delegated credentials...Done
>>>>> globusrun-ws: Job failed: Error code: 201
>>>>> Script stderr:
>>>>> sudo: no passwd entry for wlee!
>>>>>
>>>>> I checked out wlee is on the sudoer list. Anything that i missed
>>>>> here?
>>>>> Thank you,
>>>>> Wonjun
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>