Hi all,
duiring these days I'm trying to consume an axis web service from a
GT4 service. I'm able to contact correctly this axis web service from
a javastandalone client,
but when I tried to run the same calls from inside a GT4 container, I
receives this fault:
AxisFault
faultCode:
Hi!
I use GT 4.0.8 and want to connect to a host using
GSSAPIAuthentication. So I followed the installation instructions on http://globus.org/toolkit/docs/4.0/security/openssh/admin-index.html
.
When I try to start the daemon by $GLOBUS_LOCATION/sbin/SXXsshd
start the message Starting up
Check syslog for errors.
See also:
http://grid.ncsa.uiuc.edu/ssh/ts_common.html
Christian Szongott wrote:
Hi!
I use GT 4.0.8 and want to connect to a host using GSSAPIAuthentication.
So I followed the installation instructions on
The web service I'm trying to contact is VOMS, in particular
voms-admin interface, the strange thing is that I can contact this
specific web service from a standalone client built on top of the same
stubs generated with axsi wsdl2java.
Thank you for the support,
Andrea
On Mon, Feb 23, 2009 at
Can i see the configuration for the gridftp servers? They should have a --max-connections X if
command line, or instances = X in from xinetd. The value of X should be around 50. Sometimes when
it is set too high (or unlimited) and there are many simultaneous connections that it is attempting
Here is the configuration (identical on both machines)
service gsiftp
{
instances = 100
socket_type = stream
wait= no
user= root
env += GLOBUS_LOCATION=/export/work/globus-4.2.1
env +=
i recommend changing the instances value to something between 10 and 50. If you assume that each
transfer will get a 1/instance share of the endpoints BW values as low as 10 make more sense.I am
not sure it will solve your problem entirely, but this has been the cause of very similar problems
I've tried increasing the number of container threads to improve
performance; that hasn't helped.
This could actually hurt. Others have noticed that too many container threads is what causes the
container to overheat.
My guess is that your build failed. If you kept a log of your output
from make, check it for errors. Or you could try 'make gsi-openssh
install' again and watch for errors.
Christian Szongott wrote:
It seems to be a more basic problem. I've figured out, that
$GLOBUS_LOCATION/sbin/sshd is called
I just tried to install gsi-openssh (make gsi-openssh install), as you
mentioned. During the build process I can't see any errors but the
sshd is still not there. Here's what I got:
/usr/local/gt4/sbin/gpt-build -srcdir=source-trees/core/source
gcc32dbg
/usr/local/gt4/sbin/gpt-build
Hi Charles, list
I had successfully installed GT according to the Quick start guide
Ans was able to do the gridftp work my first try.
Today after 3-4 days, i am trying to do that again.
and i get
[skha...@comet ~]$ myproxy-logon -s protos
Error authenticating: GSS Major Status: Authentication
Sorry, I should have expected this SKIPPING REBUILD business.
One way to force a rebuild is to add -force to the buildopts via configure:
./configure --prefix=$GLOBUS_LOCATION \
--with-buildopts=-verbose -force \
--with-gsiopensshargs=--with-pam
Then when you run make gsi-openssh
12 matches
Mail list logo