Hello,
Thanks for reply!!!!
The problem is solved. It was because of SSH used by PBS. Finally I have
configured SSH for passwordless authentication, so now it is working!
_ _ _ _ _ _ _ _ _ _
Regads
Saumesh Kumar
IIT Roorkee
On Wed, Apr 13, 2011 at 8:07 PM, Prashanth Chengi
<[email protected]>wrote:
> A fork submission runs on the headnode itself, hence no problem. With a PBS
> job, the job has to be spawned across nodes. Do you have passwordless ssh
> enabled? Are normal pbs job submissions working fine ?
>
> Regards,
> Prashanth Chengi
> National PARAM SuperComputing Facility
> System Administration and Networking Group
> C-DAC Pune
>
> --
> Our greatest triumph is not in never falling.
> It is in getting up every time we fall.
>
>
> On Wed, 13 Apr 2011, Saumesh Kumar wrote:
>
> Hello
>>
>> I am having a problem in submitting jobs to PBS through globus.
>>
>> When I run the following command:
>> globusrun-ws -submit -F saum.grid -Ft PBS -s -c
>> /bin/uname -a
>>
>> I get the following output:
>> Delegating user credentials...Done.
>> Submitting job...Done.
>> Job ID: uuid:88512a06-65d6-11e0-b240-080027a29961
>> Termination time: 04/14/2011 14:01 GMT
>> Current job state: Pending
>> Current job state: Active
>> Current job state: CleanUp-Hold
>> Permission denied, please try
>> again. }
>> Permission denied, please try
>> again. }
>> Permission denied
>> (publickey,password). } <= ============== error
>> [: 59: !=: unexpected
>> operator }
>> Current job state: CleanUp
>> Current job state: Done
>> Destroying job...Done.
>> Cleaning up any delegated credentials...Done.
>>
>>
>>
>> Whereas when run the same job for Fork, everything works fine. ( i.e
>> "globusrun-ws -submit -F saum.grid -Ft Fork-s -c /bin/uname -a" is
>> working. )
>>
>>
>> What is the problem with PBS and how can I configure it to remove that
>> permission denied error???
>>
>> _ _ _ _ _ _ _ _ _ _
>> Regads
>> Saumesh Kumar
>> IIT Roorkee
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
