Bugzilla – Bug 2666
RFT does not return all errors from gridftp server
Last modified: 2005-03-31 13:36:56
You need to
before you can comment on or make changes to this bug.
I was trying to do some RFT transfers, but got an error message from RFT:
rynge@viz-9:~$ rft -h viz-login.isi.edu -r 9000 transfer.xfr
Number of transfers in this request: 1
Subscribed for overall status
Termination time to set: 60 minutes
Overall status of transfer:
Error:Error authenticating user at source/dest hostnull [Caused by:
Not very informative. After enabling debugging on the gridftp server, I found
the real problem:
globus_gsi_callback_module: Could not verify credential
globus_gsi_callback_module: The certificate is not yet valid: Cert with subject:
/C=US/O=NPACI/OU=SDSC/CN=Mats Rynge/UID=ux454281/CN=609403960/CN=420783230 is
not yet valid- check clock skew between hosts.
The real problem is obiously my fault, but it would be nice if RFT could return
the error, instead of my changing hats from user to sysadmin and tailing logfiles.
Created an attachment (id=498) [details]
Assigning this to jarek.
This is the Error I see at RFT:
2005-01-31 19:02:35,430 ERROR service.TransferWork [Thread-9010,run:575] Terminal transfer
errorError authenticating user at source/dest hostnull [Caused by: java.io.EOFException]Error
authenticating user at source/dest hostnull. Caused byjava.io.EOFException at
What gridftp server is this exactly? I believe this is a server problem not a
Both RFT and GridFTP built from CVS HEAD.
Was the certificate on client or server expired?
With the client certificate expired I get the following error:
Caused by java.io.IOException: 530 Authentication failed.
Older gridftp server was a little more verbose on this error.
I meant was the client or server ceritifcate not yet valid?
From what I can tell the server is closing the connection. The Java client code
throws EOFException only if the connection is closed. Reassigning to Mike for
There were two problems here, the original reported problem, was where the
server would close the connection on certain authentication errors, and was
fixed by a merge a few days after the report (which is why Jarek's results
didn't match Mats'). The other is reporting a useful error to the client,
which I've just fixed.
Everything's in the trunk.