Hello CIJO, CIJO YOHANNAN wrote: > I am getting this error when i try to get GridFTP running: > > project3:~# myproxy-logon -s project3.lan.dbit.in > Error authenticating: Connection closed.
The myproxy-server closed the connection, but I don't know the reason without seeing the relevant myproxy-server logs. > project3:~# myproxy-server -d > myproxy-server v4.2 10 Jan 2008 PAM starting at Thu Mar 12 14:36:19 2009 > reading configuration file /etc/myproxy-server.config > using storage directory /var/myproxy > Port 7512 on localhost already in use, probably by another > myproxy-server instance. Use the -p option to run multiple > myproxy-server instances on different ports. > Failure: Error in bind() > Address already in use You attempted to start another myproxy-server instance, but because a myproxy-server was already running on port 7512, this instance could not start. > project3:~# grid-proxy-init -debug -verify > > ERROR: Couldn't find valid credentials to generate a proxy. > grid_proxy_init.c:557: globus_sysconfig: Error with certificate > filename > globus_sysconfig: Error with certificate filename > globus_sysconfig: File has zero length: File: /root/.globus/usercert.pem This problem with your host credentials is very likely what is causing the myproxy-server failure. > I would be glad if someone could help me with the exact procedure/commands > to run to get this running. I recommend the GT Quickstart: http://www.globus.org/toolkit/docs/latest-stable/admin/quickstart In the "Setting up security on your first machine" section, you'll see instructions for creating /etc/grid-security/host*.pem as required by the myproxy-server. -Jim
smime.p7s
Description: S/MIME Cryptographic Signature
