By any chance did you skip step 2.3?
Did you successfully run the myproxy-retrieve command in step 2.3 before
proceeding to step 2.4?
Also make sure both your machines have accurate system clocks.
Sometimes system clock problems cause low-level SSL errors like this.

On 6/8/10 1:50 AM, Deepti Malhotra wrote:
> Hi,
> 
>           I am installing globus tollkit 5.0.1 on my machine. I have done 
> successfully with my first machine named nodeA on 4th june and now 2day i 
> have been working on second machine named webserver. 
> 
> In step 2.4 i.e GridFTP of second machine by using quickstart
>  
> 
> 
>       
>       
>       
>       
>       
>       
> 
> [r...@webserver
> grid-security]# vim /etc/xinetd.d/gridftp 
> 
> [r...@webserver
> grid-security]# vim /etc/services 
> 
> [r...@webserver
> grid-security]# /etc/init.d/xinetd reload 
> 
> Reloading
> configuration:                                   [  OK  ] 
> 
> 
> 
> 
> 
> 
> 
> [r...@webserver ~]# export
> GLOBUS_LOCATION=/usr/local/globus-5.0.1/ 
> 
> [r...@webserver ~]# source
> $GLOBUS_LOCATION/etc/globus-user-env.csh
> 
> -bash:
> /usr/local/globus-5.0.1//etc/globus-user-env.csh: line 167: syntax
> error: unexpected end of file
> 
> [r...@webserver
> ~]# source $GLOBUS_LOCATION/etc/globus-user-env.sh
> 
> [r...@webserver
> ~]# myproxy-logon -s nodeA
> 
> Enter MyProxy
> pass phrase: 
> 
> Error authenticating: Connection closed.
> Error writing: GSS Major Status: General failure
> GSS Minor Status Error Chain:
> globus_gsi_gssapi: internal problem with SSL BIO: SSL failed wrapping entire 
> message: SSL_write wrote -1 bytes, should be 79 bytes
> 
> Do i have to perform all the steps on both the machines each time.
> Can anyboby suggest me do i have to perform all the steps on machine first 
> i.e nodeA again.
> 
> 
> 
> 
> 
> 
> Regards
> 
> Deepti Malhotra
> 
> Research Scholar
> 
> Deptt.Of Computer Science & IT
> 
> Jammu University
> 
> Jammu
> 
> 

Reply via email to