[Gridsphere-users] Problems with Grid Portlets
Steffen Limmer
limmers at gmx.de
Tue Mar 11 07:41:40 PDT 2008
Hi,
we have no /etc/grid-security directory on racl00.
We installed all the security stuff in $GLOBUS_LOCATION/etc. That was the problem. Now we tell Grid Portlets, where it can find the CA certificates in the ~/.globus/cog.properties file and everything works.
Thanks for your help.
Best regards, Steffen Limmer
>
> Hi,
>
> /etc/grid-security on all machines is the same?
>
> Normal command-line grid operations do work?
>
> Oliver
>
> On Mar 11, 2008, at 2:19 PM, Steffen Limmer wrote:
>
> > Hi,
> >
> > we have some problems to get the Grid Portlets work correctly.
> > We have two machines with a GT4 installation.
> > On the first host, grid.inf-ra.uni-jena.de, we have GT4.0.4
> > installed and on the second, racl00.inf-ra.uni-jena.de we have
> > GT4.0.6.
> > On grid.inf-ra.uni-jena.de we deployed the Grid Portlets 1.4 with
> > Tomcat 2.2.25 and GridSphere 2.2.9 and everything works fine.
> > Now we try to deploy Grid Portlets on racl00 and don't get it to work.
> > It creates successfully portal credentials but it gets no
> > informations about the Resources, the FileBrowser Portlet don't work
> > and when we try to recieve a credential from MyProxy we get the
> > following error message:
> >
> > MyProxy get failed. [Caused by: Authentication failed [Caused by:
> > Failure unspecified at GSS-API level [Caused by: Unknown CA]]]
> >
> > Thats our Resources.xml:
> >
> *************************************************************************
> > <?xml version="1.0" encoding="UTF-8"?>
> > <grid-resources>
> > <!-- Racl Cluster -->
> > <hardware-resource label="Portal"
> > description="Master Node of the JETI-CL"
> > hostname="racl00.inf-ra.uni-jena.de">
> > <!-- Secure directory resource -->
> > <localhost-resource/>
> > <!-- GRAM (GT2-GT4) -->
> > <ws-gram-resource/>
> > <!-- GRID FTP (GT2-GT4) -->
> > <gridftp-resource/>
> > <!-- <ws-mds-resource/> -->
> > <ws-mds-resource/>
> > </hardware-resource>
> >
> > <!-- Leave this resource definition. -->
> > <hardware-resource label="Grid"
> > description="Master Node of the Linux-Pool-
> > Cluster"
> > hostname="grid.inf-ra.uni-jena.de">
> > <!-- GRID FTP (GT2-GT4) -->
> > <gridftp-resource/>
> > <!-- MYPROXY (GT2-GT4) -->
> > <myproxy-resource label="MyProxy"
> > port="7512"
> > portalCertFile="/home/racl/gridsphere/hostcert.pem"
> > portalKeyFile="/home/racl/gridsphere/hostkey.pem"/>
> > <ws-gram-resource/>
> > </hardware-resource>
> > </grid-resources>
> >
> > ************************************************************************
> > In the MyProxy logs on grid.inf-ra.uni-jena.de occures the following
> > error when we access the Portlets:
> > ****************************
> > Mar 11 14:00:49 grid xinetd[12526]: START: myproxy-server pid=11277
> > from=141.35.14.29
> > Mar 11 14:00:49 grid myproxy-server[11277]: myproxy-server v3.7 12
> > Dec 2006 PAM starting at Tue Mar 11 14:00:49 2008
> > Mar 11 14:00:49 grid myproxy-server[11277]: using storage directory /
> > var/myproxy
> > Mar 11 14:00:49 grid myproxy-server[11277]: Connection from
> > 141.35.14.29
> > Mar 11 14:00:49 grid xinetd[12526]: EXIT: myproxy-server status=1
> > pid=11277 duration=0(sec)
> > Mar 11 14:00:49 grid myproxy-server[11277]: Error authenticating
> > client: GSS Major Status: Some Other GSS failure GSS Minor Status
> > Error Chain: (null) GSS token read error. The client may have
> > aborted the network connection. Check client-side error messages for
> > more information.
> > Mar 11 14:00:49 grid myproxy-server[11277]: Failure: error in
> > myproxy_send()
> > ********************************************
> > In the container.log from globus we get also an error:
> > ********************************************
> > 2008-03-11 12:17:41,973 ERROR container.GSIServiceThread
> > [ServiceThread-22,process:147] Error processing request
> > java.net.SocketException: Connection reset
> > at java.net.SocketInputStream.read(SocketInputStream.java:168)
> > at org.globus.gsi.gssapi.SSLUtil.read(SSLUtil.java:37)
> > at
> > org
> > .globus
> > .gsi
> > .gssapi.net.impl.GSIGssInputStream.readToken(GSIGssInputStream.java:
> > 64)
> > at
> > org
> > .globus
> > .gsi
> > .gssapi
> > .net
> > .impl.GSIGssInputStream.readHandshakeToken(GSIGssInputStream.java:54)
> > at
> > org
> > .globus.gsi.gssapi.net.impl.GSIGssSocket.readToken(GSIGssSocket.java:
> > 60)
> > at
> > org
> > .globus.gsi.gssapi.net.GssSocket.authenticateServer(GssSocket.java:
> > 122)
> > at
> > org.globus.gsi.gssapi.net.GssSocket.startHandshake(GssSocket.java:142)
> > at
> > org.globus.gsi.gssapi.net.GssSocket.getOutputStream(GssSocket.java:
> > 161)
> > at
> > org
> > .globus
> > .wsrf.container.GSIServiceThread.process(GSIServiceThread.java:99)
> > at
> > org.globus.wsrf.container.ServiceThread.run(ServiceThread.java:291)
> > ***********************************************
> >
> > Has anybody an idea, what could be the problem and how we can solve
> > it?
> > We are thankful for any suggestions.
> > Thanks in advance.
> >
> > Kind regards, Steffen Limmer
> > --
> > Psssst! Schon vom neuen GMX MultiMessenger gehört?
> > Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
> > _______________________________________________
> > Gridsphere-users mailing list
> > Gridsphere-users at gridsphere.org
> > http://lists.gridsphere.org/mailman/listinfo/gridsphere-users
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (Darwin)
>
> iD8DBQFH1ooNm9f1ZrJBmokRAsrrAJ0ZruF7chZ1E0pAwCb71jJEtFjUcwCglquV
> LjhVT6qgiLdQT9RXtlcwgEY=
> =+jzD
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Gridsphere-users mailing list
> Gridsphere-users at gridsphere.org
> http://lists.gridsphere.org/mailman/listinfo/gridsphere-users
--
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
More information about the Gridsphere-users
mailing list