gridsam-discuss Mailing List for GridSAM (Page 10)

Brought to you by: justinbradley, npch, stevecrouch

gridsam-discuss — GridSAM users and developers

You can subscribe to this list here.

2005	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (1)	Oct (1)	Nov (3)	Dec (18)
2006	Jan (11)	Feb (19)	Mar (5)	Apr (9)	May (5)	Jun (1)	Jul	Aug (6)	Sep (8)	Oct	Nov (10)	Dec (1)
2007	Jan (3)	Feb (14)	Mar (8)	Apr (5)	May (5)	Jun (1)	Jul (1)	Aug	Sep	Oct (8)	Nov (3)	Dec (1)
2008	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (5)	Sep	Oct (1)	Nov (9)	Dec (7)
2009	Jan (2)	Feb (1)	Mar	Apr (8)	May (3)	Jun (2)	Jul (7)	Aug (5)	Sep	Oct (6)	Nov (1)	Dec
2010	Jan	Feb	Mar (6)	Apr (1)	May (1)	Jun (2)	Jul (3)	Aug (1)	Sep	Oct	Nov	Dec (5)
2011	Jan (2)	Feb (3)	Mar (6)	Apr	May	Jun	Jul	Aug	Sep (2)	Oct	Nov	Dec

Flat | Threaded

<< < 1 .. 8 9 10 (Page 10 of 10)

[gridsam-discuss] Re: GridSAM to NGS: Staging files out using SFTP: Error

From: William L. <ww...@do...> - 2005-12-13 10:58:23

Yes. That's part of the test. Although the test targets the Leeds node. I
will do some test on the Oxford node in the mean time. Can you send me your
JSDL and let me know the GridSAM version you are using, please?

By the way, the 2.x release has a more stable version of the Globus Cogkit
integrated with GridSAM.

William

On 12/13/05, Garry Smith <gar...@co...> wrote:
>
> Hi,
>
> Has anyone been successful using sftp to stage results out from NGS Globu=
s
> jobmanagers?
>
> gridsam-status -s "
> http://gridsamServer:8080/gridsam/services/gridsam?WSDL"-j
> urn:gridsam:14451683081fa5170108200242d8001b
> Job Progress: pending -> staging-in -> staged-in -> active -> executed ->
> staging-out -> failed
>
> --- pending - 2005-12-12 17:26:25.0 ---
> job is being scheduled
> --- staging-in - 2005-12-12 17:26:25.0 ---
> staging files...
> --- staged-in - 2005-12-12 17:27:27.0 ---
> 0 files staged in
> --- active - 2005-12-12 17:27:27.0 ---
> job is being submitted through globus
> --- executed - 2005-12-12 17:27:28.0 ---
> globus job completed
> --- staging-out - 2005-12-12 17:27:48.0 ---
> staging files out...
> --- failed - 2005-12-12 17:28:50.0 ---
> helloworld-stdout.txt fails to be staged: Could not determine the type of
> file
> "gsiftp://grid-compute.oesc.ox.ac.uk/helloworld-stdout.txt".
>
> --------------
> Job Properties
> --------------
> urn:gridsam:globus:id=3D
> https://grid-compute.oesc.ox.ac.uk:64054/26651/1134408443/
> urn:gridsam:globus:rsl=3D&
> (executable=3D/bin/echo)
>     (arguments=3Dhello world )
> (stdout=3Dhelloworld-stdout.txt)
>
> (stderr=3Dhelloworld-stderr.txt)
>
> Thanks
> Garry
>



--
--- William Lee @  London e-Science Centre, Imperial College London --
--- Software Coordinator ---
A: Room 380, Department of Computing, Imperial College London,  Huxley
Building, South Kensington campus, London SW7 2AZ, UK
E: wwhl at doc.ic.ac.uk | william at imageunion.com
W: www.lesc.ic.ac.uk | www.imageunion.com
P: +44(0)20 7594 8310
F: +44(0)20 7581 8024

--- Projects ----------------------------
GridSAM: http://www.lesc.ic.ac.uk/gridsam
Markets: http://www.lesc.ic.ac.uk/markets
ICENI:   http://www.lesc.ic.ac.uk/iceni
-----------------------------------------

[gridsam-discuss] Re: GridSAM to Globus: automatically maintaing the GridSAM proxy

From: William L. <ww...@do...> - 2005-12-13 10:53:20

Answers to your questions


Questions:
>
> i. What is the recommended way to read the passphrase (i.e. with out a
> user
> present to insert the passphrase)?


If you are referring to the myproxy command. That's designed for interactiv=
e
use, so the only way to input a passphrase is via the standard input. The
myproxy command comes from he Globus Toolkit Cogkit directly. You might use
other tools that are compatible with the myproxy server interface.

For gridsam-submit however, you can create a file
${HOME}/.gridsam/client.properties, insert the lines

myproxypassword=3Dmypassword
myproxyuser=3D...
myproxyport=3D...
myproxyhost=3D...

These settings would be used if the command-line options are not given in
the gridsam-submit command.


> ii. I want the returned proxy to have the same name each time it is
> returned.
> What is the recommended way to achieve this?
>
>
You can use the myproxy get "-o" option. Check out "myproxy get -help" for
other opions.

William

--
--- William Lee @  London e-Science Centre, Imperial College London --
--- Software Coordinator ---
A: Room 380, Department of Computing, Imperial College London,  Huxley
Building, South Kensington campus, London SW7 2AZ, UK
E: wwhl at doc.ic.ac.uk | william at imageunion.com
W: www.lesc.ic.ac.uk | www.imageunion.com
P: +44(0)20 7594 8310
F: +44(0)20 7581 8024

--- Projects ----------------------------
GridSAM: http://www.lesc.ic.ac.uk/gridsam
Markets: http://www.lesc.ic.ac.uk/markets
ICENI:   http://www.lesc.ic.ac.uk/iceni
-----------------------------------------

[gridsam-discuss] GridSAM to NGS: Staging files out using SFTP: Error

From: Garry S. <gar...@co...> - 2005-12-13 10:50:35

Hi,

Has anyone been successful using sftp to stage results out from NGS Globus 
jobmanagers?

gridsam-status -s "http://gridsamServer:8080/gridsam/services/gridsam?WSDL"-j 
urn:gridsam:14451683081fa5170108200242d8001b
Job Progress: pending -> staging-in -> staged-in -> active -> executed -> 
staging-out -> failed

--- pending - 2005-12-12 17:26:25.0 ---
job is being scheduled
--- staging-in - 2005-12-12 17:26:25.0 ---
staging files...
--- staged-in - 2005-12-12 17:27:27.0 ---
0 files staged in
--- active - 2005-12-12 17:27:27.0 ---
job is being submitted through globus
--- executed - 2005-12-12 17:27:28.0 ---
globus job completed
--- staging-out - 2005-12-12 17:27:48.0 ---
staging files out...
--- failed - 2005-12-12 17:28:50.0 ---
helloworld-stdout.txt fails to be staged: Could not determine the type of file 
"gsiftp://grid-compute.oesc.ox.ac.uk/helloworld-stdout.txt".

--------------
Job Properties
--------------
urn:gridsam:globus:id=https://grid-compute.oesc.ox.ac.uk:64054/26651/1134408443/
urn:gridsam:globus:rsl=&
(executable=/bin/echo)
    (arguments=hello world )
(stdout=helloworld-stdout.txt)

(stderr=helloworld-stderr.txt)

Thanks
Garry

[gridsam-discuss] GridSAM to Globus: automatically maintaing the GridSAM proxy

From: Garry S. <gar...@co...> - 2005-12-12 16:48:19

Hi William,

GridSAM v1 with jobmanager configured to a NGS job manager.

On the GridSAM server:

1.
~/bin/OMIICLIENT2_3_0/OMIICLIENT/gridsam/bin/myproxy -l machineA host 
myproxy.grid-support.ac.uk put
Enter MyProxy Pass Phrase:
A proxy valid for 168 hours (7 days) for user machineA now exists on 
myproxy.grid-support.ac.uk.

2.
~/bin/OMIICLIENT2_3_0/OMIICLIENT/gridsam/bin/myproxy -l machineA -host 
myproxy.grid-support.ac.uk get
Enter MyProxy Pass Phrase:
A proxy has been received for user machineA in ./x509up_40827.pem

I would like to automate this task using a cron job.

Questions:

i. What is the recommended way to read the passphrase (i.e. with out a user 
present to insert the passphrase)?

ii. I want the returned proxy to have the same name each time it is returned.  
What is the recommended way to achieve this?

My cog.properties already contains the following line (but with no effect):
proxy=/tmp/x509up_u1000

Thanks
Garry

[gridsam-discuss] Intermittent failure: GridSAM server SSH to Condor: failed to create job directory: Could not create folder "sftp://user@machine.domain/".

From: Garry S. <gar...@co...> - 2005-11-15 21:23:45

Hi,

Periodically I get the following error message:
failed to create job directory: Could not create folder 
"sftp://us...@ma...main/".

Jobmanager.xml configured to access Condor over SSH. See jobmanager.xml below

OMII version 2.1.0
java version "1.5.0_04"  Sun
SuSE Linux 9.2
GridSAM installed using the Stack Installer

The OMII/GridSAM client and server are on the same machine (surfboard).
The condor host in a remote machine accessed over SSH.

I am seeing this error periodically which prevents jobs from executing on 
condor. If I restart the tomcat container then I am able to submit jobs 
again. At some point after this the error will reappear again causing jobs 
not to execute.

The fact that this appears after a number of successful job submissions makes 
me think this is a bug in the GridSAM server.  The number of successful 
submissions before I get this error differs each time.

Has anyone else encountered this? Is there already a fix?

Details:

in the text below the term "condor.host" replaces the hostname of the Condor 
machine.

Client Command line:
-------------------------------
garry@surfboard:~/jsdl> ~/bin/OMIICLIENT2_1_0/gridsam/bin/gridsam-submit -s 
"http://surfboard.lan:8090/gridsam/services/gridsam?WSDL" 
-j ./helloworld-noproxy.jsdl

garry@surfboard:~/jsdl> ~/bin/OMIICLIENT2_1_0/gridsam/bin/gridsam-status -s 
"http://surfboard.lan:8090/gridsam/services/gridsam?WSDL" -j 
urn:gridsam:ff8080820794ba20010795925c7b0202
Job Progress: pending -> failed

--- pending - 2005-11-15 20:16:35.0 ---
job is being scheduled
--- failed - 2005-11-15 20:16:38.0 ---
failed to create job directory: Could not create folder 
"sftp://user@condor.host/".

--------------
Job Properties
--------------



jobmanager.xml:
-------------------------

<?xml version="1.0" encoding="UTF-8"?>
<module id="jobmanager.ssh" version="1.0.0">

    <!-- dependent modules -->
    <sub-module 
descriptor="org/icenigrid/gridsam/resource/config/common.xml"/>
    <sub-module descriptor="org/icenigrid/gridsam/resource/config/shell.xml"/>
    <sub-module 
descriptor="org/icenigrid/gridsam/resource/config/condor.xml"/>
    <sub-module 
descriptor="org/icenigrid/gridsam/resource/config/embedded.xml"/>
    <sub-module descriptor="database.xml"/>


    <!-- override the factory defaults here -->
    <contribution configuration-id="hivemind.ApplicationDefaults">

        <!-- condor command location -->
        <default symbol="condor.CondorSubmitCommand" 
value="/usr/local/condor/bin/condor_submit"/>
        <default symbol="condor.CondorRmCommand" 
value="/usr/local/condor/bin/condor_rm"/>

        <!-- log file for monitoring job status -->
        <default symbol="condor.CondorLogFile" value="/tmp/condor.log"/>

        <!-- the location of the tail command -->
        <default symbol="condor.TailCommand" value="tail"/>

        <!-- the default location of the classad generation script
            WEB-INF/classes/classad.groovy
        -->
        <default symbol="condor.ScriptResource" value="classad.groovy"/>

    </contribution>

    <!-- uncomment the following to use ssh-based shell -->


    <sub-module descriptor="org/icenigrid/gridsam/resource/config/ssh.xml"/>
    <contribution configuration-id="ssh.ShellConfig">
        <Server host="condor.host" user="user">
            <!-- PublicKeyAuthentication keyfile="${user.home}/.ssh/id_rsa" 
passphrase="" -->
                <PasswordAuthentication password="password" />
        </Server>
    </contribution>
</module>


JSDL:
--------
<JobDefinition xmlns="http://schemas.ggf.org/jsdl/2005/06/jsdl">
  <JobDescription>
    <Application>
      <POSIXApplication 
xmlns="http://schemas.ggf.org/jsdl/2005/06/jsdl-posix">
        <Executable>/bin/echo</Executable>
        <Argument>Hello World</Argument>
      </POSIXApplication>
    </Application>
  </JobDescription>
</JobDefinition>


Any ideas?

Thanks and regards
Garry

Re: [gridsam-discuss] Unable to retreive proxy credentials. MyProxy get failed

From: William L. <ww...@do...> - 2005-11-02 22:50:17

Have you added the CA certificate which signed the certificate of the
grid-support.ac.uk MyProxy server to the cog.properties files (I would
think it's the server-side, because you can upload the proxy on your
client)?

William

On 02/11/05, Garry Smith <gar...@co...> wrote:
> Hi William,
>
> I have now upgraded to the GridSAM 1.0 client (as shipped in the
> omii-client-2.1.0.tar.gz). This is now installed on the same machine (but=
 in
> a different user account) as the GridSAM 1.0 server.
>
> Machine: SuSE 9.0, Sun jdk 1.5.0_04, Intel Pentium 3.
> GridSAM v1.0 submission to fork and condor work.
>
> GridSAM v1.0 submission to Globus fails.
>
> "job is being submitted through globus
> --- failed - 2005-11-02 16:59:06.0 ---
> Error retrieving MyProxy credential:Unable to retreive proxy credentials.
> MyProxy get failed. [Caused by: Authentication failed [Caused by: Failure
> unspecified at GSS-API level [Caused by: Unknown CA]]]"
>
> I am submitting the user credential to the MyProxy at grid-support.ac.uk.
> MyProxy Webstart client for Java 1.5. Using the myproxy client I can retr=
ieve
> the myproxy credential that is referenced in the JSDL.
>
> JobManager.xml:
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> <module id=3D"jobmanager.globus" version=3D"1.0.0">
>
>     <!-- dependent modules -->
>     <sub-module
> descriptor=3D"org/icenigrid/gridsam/resource/config/common.xml"/>
>     <sub-module
> descriptor=3D"org/icenigrid/gridsam/resource/config/embedded.xml"/>
>     <sub-module
> descriptor=3D"org/icenigrid/gridsam/resource/config/globus.xml"/>
>     <sub-module descriptor=3D"database.xml"/>
>
>     <!-- override the factory defaults here -->
>     <contribution configuration-id=3D"hivemind.ApplicationDefaults">
>         <!--
>             The job manager location
>         -->
>         <default symbol=3D"globus.JobManager" value=3D"grid-compute.leeds=
.ac.uk"/>
>         <!--
>             The root file system for staging files
>         -->
>         <default symbol=3D"globus.RootFileSystemURI"
> value=3D"gsiftp://grid-compute.leeds.ac.uk"/>
>         <!--
>             How often the status of the job is polled
>         -->
>         <default symbol=3D"globus.MonitoringPeriod" value=3D"20000"/>
>
>         <!-- the default location of the classad generation script
>             WEB-INF/classes/rsl.groovy
>         -->
>         <default symbol=3D"globus.ScriptResource" value=3D"rsl.groovy"/>
>
>     </contribution>
>
> </module>
>
> First attempt (myProxy details included in the JSDL):
>
> JSDL:
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
>   <JobDefinition xmlns=3D"http://schemas.ggf.org/jsdl/2005/06/jsdl">
>    <JobDescription>
>          <Application>
>                 <POSIXApplication
> xmlns=3D"http://schemas.ggf.org/jsdl/2005/06/jsdl-posix">
>                     <Executable>/bin/echo</Executable>
>                     <Argument>hello world</Argument>
>                 </POSIXApplication>
>             </Application>
>         </JobDescription>
>         <myproxy:MyProxy xmlns:myproxy=3D"urn:gridsam:myproxy">
>           <myproxy:ProxyServer>myproxy.grid-support.ac.uk</myproxy:ProxyS=
erver>
>           <myproxy:ProxyServerDN>/C=3DUK/O=3DeScience/OU=3DCLRC/L=3DDL/CN=
=3Dhost/myproxy.grid-support.ac.uk/E=3Da...@dl...</myproxy:Proxy=
ServerDN>
>           <myproxy:ProxyServerPort>7512</myproxy:ProxyServerPort>
>           <myproxy:ProxyServerUserName>name</myproxy:ProxyServerUserName>
>           <myproxy:ProxyServerPassPhrase>passphrase</myproxy:ProxyServerP=
assPhrase>
>           <myproxy:ProxyServerLifetime>2</myproxy:ProxyServerLifetime>
>           </myproxy:MyProxy>
>     </JobDefinition>
>
> Command line:
>
> garry@surfboard:~/jsdl> ~/bin/OMIICLIENT/gridsam/bin/gridsam-status -s
> "http://surfboard.lan:8090/gridsam/services/gridsam?WSDL" -j
> urn:gridsam:ff8080820750da27010751eade650035
> Job Progress: pending -> staging-in -> staged-in -> active -> failed
>
> --- pending - 2005-11-02 16:59:05.0 ---
> job is being scheduled
> --- staging-in - 2005-11-02 16:59:06.0 ---
> staging files...
> --- staged-in - 2005-11-02 16:59:06.0 ---
> no file needs to be staged in
> --- active - 2005-11-02 16:59:06.0 ---
> job is being submitted through globus
> --- failed - 2005-11-02 16:59:06.0 ---
> Error retrieving MyProxy credential:Unable to retreive proxy credentials.
> MyProxy get failed. [Caused by: Authentication failed [Caused by: Failure
> unspecified at GSS-API level [Caused by: Unknown CA]]]
>
> --------------
> Job Properties
> --------------
> urn:gridsam:globus:rsl=3D&
> (executable=3D/bin/echo)
>     (arguments=3Dhello world )
> garry@surfboard:~/jsdl>
>
>
> gridsam.log:
> [ff8080820750da27010751eade650035] state {pending} reached
> [ff8080820750da27010751eade650035] state {staging-in} reached
> [ff8080820750da27010751eade650035] state {staged-in} reached
> [ff8080820750da27010751eade650035] executing groovy script rsl.groovy
> [ff8080820750da27010751eade650035] executed groovy script rsl.groovy
> [ff8080820750da27010751eade650035] state {active} reached
> [GRAMSubmissionStage] RSL &( arguments =3D "hello" "world" )( executable =
=3D
> "/bin/echo" )
> [ff8080820750da27010751eade650035] state {failed} reached
> [ff8080820750da27010751eade650035] failed 1130950745702   1130950746336
> 1130950746356   1130950746644  1130950746789
>
>
> Second attempt:
> This time specify the myproxy details on the command line:
>
> JSDL (helloworld-noproxy.jsdl):
>
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
>   <JobDefinition xmlns=3D"http://schemas.ggf.org/jsdl/2005/06/jsdl">
>    <JobDescription>
>          <Application>
>                 <POSIXApplication
> xmlns=3D"http://schemas.ggf.org/jsdl/2005/06/jsdl-posix">
>                     <Executable>/bin/echo</Executable>
>                     <Argument>hello world</Argument>
>                 </POSIXApplication>
>             </Application>
>         </JobDescription>
>     </JobDefinition>
>
>
> Command line:
> ~/bin/OMIICLIENT/gridsam/bin/gridsam-submit -s
> "http://surfboard.lan:8090/gridsam/services/gridsam?WSDL"
> -j ./helloworld-noproxy.jsdl -myproxy -myproxypassword password -myproxyh=
ost
> myproxy.grid-support.ac.uk -myproxyuser username
>
> gridsam.log:
>
> [GridSAMService] authorised user (submitJob): CN=3Dgarry smith, L=3DDSG,
> OU=3DPortsmouth, O=3DeScience, C=3DUK
>  [ff8080820750da27010751fe55b60041] state {pending} reached
> 2005-11-02 17:20:21,989 INFO  [ff8080820750da27010751fe55b60041] state
> {staging-in} reached
>  [ff8080820750da27010751fe55b60041] state {staged-in} reached
>  [ff8080820750da27010751fe55b60041] executing groovy script rsl.groovy
> [ff8080820750da27010751fe55b60041] executed groovy script rsl.groovy
> [ff8080820750da27010751fe55b60041] state {active} reached
> [GRAMSubmissionStage] RSL &( arguments =3D "hello" "world" )( executable =
=3D
> "/bin/echo" )
> [ff8080820750da27010751fe55b60041] state {failed} reached
> [ff8080820750da27010751fe55b60041] failed 1130952021430   1130952021989
> 1130952022016   1130952022268  1130952022391
>
> Command line status:
>
> garry@surfboard:~/jsdl> ~/bin/OMIICLIENT/gridsam/bin/gridsam-status -s
> "http://surfboard.lan:8090/gridsam/services/gridsam?WSDL" -j
> urn:gridsam:ff8080820750da27010751fe55b60041
> Job Progress: pending -> staging-in -> staged-in -> active -> failed
>
> --- pending - 2005-11-02 17:20:21.0 ---
> job is being scheduled
> --- staging-in - 2005-11-02 17:20:21.0 ---
> staging files...
> --- staged-in - 2005-11-02 17:20:22.0 ---
> no file needs to be staged in
> --- active - 2005-11-02 17:20:22.0 ---
> job is being submitted through globus
> --- failed - 2005-11-02 17:20:22.0 ---
> Error retrieving MyProxy credential:Unable to retreive proxy credentials.
> MyProxy get failed. [Caused by: Authentication failed [Caused by: Failure
> unspecified at GSS-API level [Caused by: Unknown CA]]]
>
> Seems like the problem is now with the users credential and not the GridS=
AM
> credential...
>
> On Thursday 27 October 2005 15:16, William Lee wrote:
> > I have another thought with the problem you have with globus credential=
.
>
> > The problem can be solved by moving some of the security related jars
> > to the shared/lib in tomcat. This is a problem to get round a
> > limitation in the globus cogkit. See the following doc for the
> > instruction.
> > http://gridsam.sourceforge.net/1.0/docs/deploymentguide/gt2.html
>
> I followed the instructions. although I am not running mutliple GridSAMs
> on this machine at the moment.
>
> > The other thing I can think of is the cog.properties file. On my
> > system, it only contains two lines
> >
> > usercert=3D/homes/wwhl/.globus/usercert.pem
> > userkey=3D/homes/wwhl/.globus/userkey.pem
> >
> > without any reference to the proxy file.
>
> I previously removed the reference to the proxy in the server's
> cog.properties. The server defaults to reading its proxy
> from  /tmp/x509up_u501 which I populate ahead of the request (if expired)
>
>
> Any thoughts?
>
> regards
> Garry
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Downl=
oad
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> GridSAM-Discuss mailing list
> Gri...@li...
> https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
>


--
--- William Lee @  London e-Science Centre, Imperial College London --
--- Software Coordinator ---
A: Room 380, Department of Computing, Imperial College London,  Huxley
Building, South Kensington campus, London SW7 2AZ, UK
E: wwhl at doc.ic.ac.uk | william at imageunion.com
W: www.lesc.ic.ac.uk | www.imageunion.com
P: +44(0)20 7594 8310
F: +44(0)20 7581 8024

--- Projects ----------------------------
GridSAM: http://www.lesc.ic.ac.uk/gridsam
Markets: http://www.lesc.ic.ac.uk/markets
ICENI:   http://www.lesc.ic.ac.uk/iceni
-----------------------------------------

[gridsam-discuss] Unable to retreive proxy credentials. MyProxy get failed

From: Garry S. <gar...@co...> - 2005-11-02 17:22:25

Hi William,

I have now upgraded to the GridSAM 1.0 client (as shipped in the  
omii-client-2.1.0.tar.gz). This is now installed on the same machine (but in 
a different user account) as the GridSAM 1.0 server.

Machine: SuSE 9.0, Sun jdk 1.5.0_04, Intel Pentium 3.
GridSAM v1.0 submission to fork and condor work.

GridSAM v1.0 submission to Globus fails.

"job is being submitted through globus
--- failed - 2005-11-02 16:59:06.0 ---
Error retrieving MyProxy credential:Unable to retreive proxy credentials. 
MyProxy get failed. [Caused by: Authentication failed [Caused by: Failure 
unspecified at GSS-API level [Caused by: Unknown CA]]]"

I am submitting the user credential to the MyProxy at grid-support.ac.uk.
MyProxy Webstart client for Java 1.5. Using the myproxy client I can retrieve 
the myproxy credential that is referenced in the JSDL.

JobManager.xml:
<?xml version="1.0" encoding="UTF-8"?>
<module id="jobmanager.globus" version="1.0.0">

    <!-- dependent modules -->
    <sub-module 
descriptor="org/icenigrid/gridsam/resource/config/common.xml"/>
    <sub-module 
descriptor="org/icenigrid/gridsam/resource/config/embedded.xml"/>
    <sub-module 
descriptor="org/icenigrid/gridsam/resource/config/globus.xml"/>
    <sub-module descriptor="database.xml"/>

    <!-- override the factory defaults here -->
    <contribution configuration-id="hivemind.ApplicationDefaults">
        <!--
            The job manager location
        -->
        <default symbol="globus.JobManager" value="grid-compute.leeds.ac.uk"/>
        <!--
            The root file system for staging files
        -->
        <default symbol="globus.RootFileSystemURI" 
value="gsiftp://grid-compute.leeds.ac.uk"/>
        <!--
            How often the status of the job is polled
        -->
        <default symbol="globus.MonitoringPeriod" value="20000"/>

        <!-- the default location of the classad generation script
            WEB-INF/classes/rsl.groovy
        -->
        <default symbol="globus.ScriptResource" value="rsl.groovy"/>

    </contribution>

</module>

First attempt (myProxy details included in the JSDL):

JSDL:
<?xml version="1.0" encoding="UTF-8"?>
  <JobDefinition xmlns="http://schemas.ggf.org/jsdl/2005/06/jsdl">
   <JobDescription>
         <Application>
                <POSIXApplication 
xmlns="http://schemas.ggf.org/jsdl/2005/06/jsdl-posix">
                    <Executable>/bin/echo</Executable>
                    <Argument>hello world</Argument>
                </POSIXApplication>
            </Application>
        </JobDescription>
        <myproxy:MyProxy xmlns:myproxy="urn:gridsam:myproxy">
          <myproxy:ProxyServer>myproxy.grid-support.ac.uk</myproxy:ProxyServer>
          <myproxy:ProxyServerDN>/C=UK/O=eScience/OU=CLRC/L=DL/CN=host/myproxy.grid-support.ac.uk/E=a.j...@dl...</myproxy:ProxyServerDN>
          <myproxy:ProxyServerPort>7512</myproxy:ProxyServerPort>
          <myproxy:ProxyServerUserName>name</myproxy:ProxyServerUserName>
          <myproxy:ProxyServerPassPhrase>passphrase</myproxy:ProxyServerPassPhrase>
          <myproxy:ProxyServerLifetime>2</myproxy:ProxyServerLifetime>
          </myproxy:MyProxy>
    </JobDefinition>

Command line:

garry@surfboard:~/jsdl> ~/bin/OMIICLIENT/gridsam/bin/gridsam-status -s 
"http://surfboard.lan:8090/gridsam/services/gridsam?WSDL" -j 
urn:gridsam:ff8080820750da27010751eade650035
Job Progress: pending -> staging-in -> staged-in -> active -> failed

--- pending - 2005-11-02 16:59:05.0 ---
job is being scheduled
--- staging-in - 2005-11-02 16:59:06.0 ---
staging files...
--- staged-in - 2005-11-02 16:59:06.0 ---
no file needs to be staged in
--- active - 2005-11-02 16:59:06.0 ---
job is being submitted through globus
--- failed - 2005-11-02 16:59:06.0 ---
Error retrieving MyProxy credential:Unable to retreive proxy credentials. 
MyProxy get failed. [Caused by: Authentication failed [Caused by: Failure 
unspecified at GSS-API level [Caused by: Unknown CA]]]

--------------
Job Properties
--------------
urn:gridsam:globus:rsl=&
(executable=/bin/echo)
    (arguments=hello world )
garry@surfboard:~/jsdl>


gridsam.log:
[ff8080820750da27010751eade650035] state {pending} reached 
[ff8080820750da27010751eade650035] state {staging-in} reached
[ff8080820750da27010751eade650035] state {staged-in} reached
[ff8080820750da27010751eade650035] executing groovy script rsl.groovy
[ff8080820750da27010751eade650035] executed groovy script rsl.groovy 
[ff8080820750da27010751eade650035] state {active} reached
[GRAMSubmissionStage] RSL &( arguments = "hello" "world" )( executable = 
"/bin/echo" )
[ff8080820750da27010751eade650035] state {failed} reached
[ff8080820750da27010751eade650035] failed 1130950745702   1130950746336   
1130950746356   1130950746644  1130950746789


Second attempt:
This time specify the myproxy details on the command line:

JSDL (helloworld-noproxy.jsdl):

<?xml version="1.0" encoding="UTF-8"?>
  <JobDefinition xmlns="http://schemas.ggf.org/jsdl/2005/06/jsdl">
   <JobDescription>
         <Application>
                <POSIXApplication 
xmlns="http://schemas.ggf.org/jsdl/2005/06/jsdl-posix">
                    <Executable>/bin/echo</Executable>
                    <Argument>hello world</Argument>
                </POSIXApplication>
            </Application>
        </JobDescription>
    </JobDefinition>


Command line:
~/bin/OMIICLIENT/gridsam/bin/gridsam-submit -s 
"http://surfboard.lan:8090/gridsam/services/gridsam?WSDL" 
-j ./helloworld-noproxy.jsdl -myproxy -myproxypassword password -myproxyhost 
myproxy.grid-support.ac.uk -myproxyuser username

gridsam.log:

[GridSAMService] authorised user (submitJob): CN=garry smith, L=DSG, 
OU=Portsmouth, O=eScience, C=UK
 [ff8080820750da27010751fe55b60041] state {pending} reached
2005-11-02 17:20:21,989 INFO  [ff8080820750da27010751fe55b60041] state 
{staging-in} reached
 [ff8080820750da27010751fe55b60041] state {staged-in} reached
 [ff8080820750da27010751fe55b60041] executing groovy script rsl.groovy
[ff8080820750da27010751fe55b60041] executed groovy script rsl.groovy
[ff8080820750da27010751fe55b60041] state {active} reached
[GRAMSubmissionStage] RSL &( arguments = "hello" "world" )( executable = 
"/bin/echo" )
[ff8080820750da27010751fe55b60041] state {failed} reached
[ff8080820750da27010751fe55b60041] failed 1130952021430   1130952021989   
1130952022016   1130952022268  1130952022391

Command line status:

garry@surfboard:~/jsdl> ~/bin/OMIICLIENT/gridsam/bin/gridsam-status -s 
"http://surfboard.lan:8090/gridsam/services/gridsam?WSDL" -j 
urn:gridsam:ff8080820750da27010751fe55b60041
Job Progress: pending -> staging-in -> staged-in -> active -> failed

--- pending - 2005-11-02 17:20:21.0 ---
job is being scheduled
--- staging-in - 2005-11-02 17:20:21.0 ---
staging files...
--- staged-in - 2005-11-02 17:20:22.0 ---
no file needs to be staged in
--- active - 2005-11-02 17:20:22.0 ---
job is being submitted through globus
--- failed - 2005-11-02 17:20:22.0 ---
Error retrieving MyProxy credential:Unable to retreive proxy credentials. 
MyProxy get failed. [Caused by: Authentication failed [Caused by: Failure 
unspecified at GSS-API level [Caused by: Unknown CA]]]

Seems like the problem is now with the users credential and not the GridSAM 
credential...

On Thursday 27 October 2005 15:16, William Lee wrote:
> I have another thought with the problem you have with globus credential.

> The problem can be solved by moving some of the security related jars
> to the shared/lib in tomcat. This is a problem to get round a
> limitation in the globus cogkit. See the following doc for the
> instruction.
> http://gridsam.sourceforge.net/1.0/docs/deploymentguide/gt2.html

I followed the instructions. although I am not running mutliple GridSAMs 
on this machine at the moment.

> The other thing I can think of is the cog.properties file. On my
> system, it only contains two lines
>
> usercert=/homes/wwhl/.globus/usercert.pem
> userkey=/homes/wwhl/.globus/userkey.pem
>
> without any reference to the proxy file.

I previously removed the reference to the proxy in the server's 
cog.properties. The server defaults to reading its proxy 
from  /tmp/x509up_u501 which I populate ahead of the request (if expired)


Any thoughts?

regards
Garry

[gridsam-discuss] Re: GridSAM ERROR [GSIFTPFileSystem] User globus credential is required but not specified in the context

From: William L. <ww...@do...> - 2005-10-27 14:16:59

Hi Garry,

(I've cc' this to the gridsam mailing-list. If you haven't subscribe
to the list yet, I would encourage you to do so -
http://sourceforge.net/mail/?group_id=3D141177)

I have another thought with the problem you have with globus credential.

Are you running multiple instances of GridSAM in the OMII container? I
can re-create your error if I'm running more than one instances of the
GridSAM webapp in a single container.

The problem can be solved by moving some of the security related jars
to the shared/lib in tomcat. This is a problem to get round a
limitation in the globus cogkit. See the following doc for the
instruction.

http://gridsam.sourceforge.net/1.0/docs/deploymentguide/gt2.html

The other thing I can think of is the cog.properties file. On my
system, it only contains two lines

usercert=3D/homes/wwhl/.globus/usercert.pem
userkey=3D/homes/wwhl/.globus/userkey.pem

without any reference to the proxy file.

William

--
--- William Lee @  London e-Science Centre, Imperial College London --
--- Software Coordinator ---
A: Room 380, Department of Computing, Imperial College London,  Huxley
Building, South Kensington campus, London SW7 2AZ, UK
E: wwhl at doc.ic.ac.uk | william at imageunion.com
W: www.lesc.ic.ac.uk | www.imageunion.com
P: +44(0)20 7594 8310
F: +44(0)20 7581 8024

--- Projects ----------------------------
GridSAM: http://www.lesc.ic.ac.uk/gridsam
Markets: http://www.lesc.ic.ac.uk/markets
ICENI:   http://www.lesc.ic.ac.uk/iceni
-----------------------------------------

[gridsam-discuss] Welcome to the GridSAM mailing lists

From: William L. <ww...@do...> - 2005-09-23 16:27:59

Hi all,

In order to provide a forum for developers and users of the GridSAM
system to share ideas, we have created two mailing lists as well as an
online forum on sourceforge.

* Plugin and core developers
http://lists.sourceforge.net/lists/listinfo/gridsam-developer

* End-users and general interest
http://lists.sourceforge.net/lists/listinfo/gridsam-discuss

Please feel free to subscribe to the relevant mailing-list in order to
post and receive useful information from us and other like-minded
users.

William


--- William Lee @  London e-Science Centre, Imperial College London --
--- Software Coordinator ---
A: Room 380, Department of Computing, Imperial College London,  Huxley
Building, South Kensington campus, London SW7 2AZ, UK
E: wwhl at doc.ic.ac.uk | william at imageunion.com
W: www.lesc.ic.ac.uk | www.imageunion.com
P: +44(0)20 7594 8310
F: +44(0)20 7581 8024

--- Projects ----------------------------
GridSAM: http://www.lesc.ic.ac.uk/gridsam
Markets: http://www.lesc.ic.ac.uk/markets
ICENI:   http://www.lesc.ic.ac.uk/iceni
-----------------------------------------

2 messages has been excluded from this view by a project administrator.

Flat | Threaded

<< < 1 .. 8 9 10 (Page 10 of 10)