Re: [gridsam-discuss] Problem using gridFTP

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Thanks for your help. 

Changing the logging level (to DEBUG), the problem seems disappear. I
have performed several executions and not crash, but when I turn to set
the logging level to INFO , the problem appears after only one or two
executions. I guess that any sentence causes the problem when INFO
debugging is set.

On Wed, 2011-03-09 at 13:28 +0000, Justin Bradley wrote:
> Hi Ismael, 
> 
> Just to check, but have you run grid-proxy-init from your GridSAM's user account?
> 
> It might be useful to up the logging level on GridSAM too, may give us a better idea as to what it happening.
> ( webapps/gridsam/WEB-INF/classes/log4j.properties )  By default its set to INFO rather than DEBUG.
> 
> Googling gave me this http://lists.globus.org/pipermail/workspace-user/2010-July/001358.html
> Its the same error you are getting, although may not be the same problem, its worth having a quick read.
> 
> 	Justin
> 
> On 9 Mar 2011, at 13:01, Ismael Marín Carrión wrote:
> 
> > Hi Justin,
> > 
> > 
> > On Wed, 2011-03-09 at 12:05 +0000, Justin Bradley wrote:
> >> Hi,
> >> 
> >> 
> >> Do you have access to the gridFTP server logs, if so do they give any
> >> more detail?
> > 
> > Yes, but it does not provide any error when connexion is broken.
> > 
> >> Also, how are you authenticating with the gridFTP server?
> >> 
> > I use a myproxy server for authenticating. In the JSDL, I provide the
> > server, port and, user and passwd needed for it.
> >> 
> >> Regards,
> >> Justin
> >> 
> >> On 9 Mar 2011, at 09:06, Ismael Marín Carrión wrote:
> >> 
> >>> Dear all,
> >>> 
> >>> I'm getting a random error when I use gridFTP for data staging-out.
> >>> The gridFTP is running as standalone (daemon flag is activated) and
> >>> version is 3.23.
> >>> 
> >>> The error stack is:
> >>> 
> >>> 2011-03-09 09:45:44,099 INFO  [job] ff8080812e99ca64012e99caad8a0001
> >>> reason for failure: Unknown message with code "Unknown message with
> >>> code "Unknown message with code "Unknown message with code "Unknown
> >>> message with code "Server refused performing the request. Custom
> >>> message:  (error code 1) [Nested exception message:  Custom message:
> >>> Unexpected reply: 451 active connection to server failed
> >>> java.net.ConnectException: Connection refused
> >>> java.net.ConnectException: Connection refused
> >>> at java.net.PlainSocketImpl.socketConnect(Native Method)
> >>> at
> >>> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327)
> >>> at
> >>> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193)
> >>> at
> >>> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180)
> >>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384)
> >>> at java.net.Socket.connect(Socket.java:546)
> >>> at java.net.Socket.connect(Socket.java:495)
> >>> at java.net.Socket.<init>(Socket.java:392)
> >>> at java.net.Socket.<init>(Socket.java:293)
> >>> at org.globus.net.SocketFactory.createSocket(SocketFactory.java:74)
> >>> at org.globus.net.SocketFactory.createSocket(SocketFactory.java:53)
> >>> at
> >>> org.globus.ftp.dc.GridFTPActiveConnectTask.execute(GridFTPActiveConnectTask.java:70)
> >>> at org.globus.ftp.dc.TaskThread.run(TaskThread.java:71)
> >>> at java.lang.Thread.run(Thread.java:636)
> >>> ]".".".".".
> >>> 
> >>> This not happens using globus-url-copy client or even other
> >>> java-based clients making use of jglobus (1.6 and 1.8). No problems
> >>> were found with a batch of 400 requests (with a level of concurrency
> >>> of 2 requests). Also, the server uses a limited range of ports,
> >>> while the client uses any free port. Thus, I guess that some in the
> >>> implementation of GridSAM causes this problem.
> >>> 
> >>> Moreover, tracking the code, GridSAM 2.3 is using:
> >>> 
> >>> import uk.ac.nesc.vfs.gsiftp.GSIFTPFileProvider;
> >>> import uk.ac.nesc.vfs.gsiftp.GSIFTPFileSystemConfigBuilder;
> >>> 
> >>> and not the similar classes on
> >>> org.icenigrid.gridsam.core.plugin.vfs.gsiftp.*. Using these last
> >>> classes GridSam crashes before of establishing a connexion with the
> >>> gridFTP server.
> >>> 
> >>> Therefore, Could you tell me some workaround for this? or What is
> >>> version/s of gridFTP tested with GridSam? and eventually, Could I
> >>> download the java package uk.ac.nesc.vfs.gsiftp?
> >>> 
> >>> Best regards and thanks in advance.
> >>> ------------------------------------------------------------------------------
> >>> Colocation vs. Managed Hosting
> >>> A question and answer guide to determining the best fit
> >>> for your organization - today and in the future.
> >>> http://p.sf.net/sfu/internap-sfd2d_______________________________________________
> >>> GridSAM-Discuss mailing list
> >>> Gri...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
> >> 
> >> --
> >> Justin Bradley
> >> Senior Software Consultant
> >> jb...@ec...
> >> ECS / EPrints Services / SSI
> >> Bay 22, 4067, B32
> >> University of Southampton
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> ------------------------------------------------------------------------------
> >> Colocation vs. Managed Hosting
> >> A question and answer guide to determining the best fit
> >> for your organization - today and in the future.
> >> http://p.sf.net/sfu/internap-sfd2d
> >> _______________________________________________ GridSAM-Discuss mailing list Gri...@li... https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
> > 
> > 
> 
> --
> Justin Bradley
> Senior Software Consultant
> jb...@ec...
> ECS / EPrints Services / SSI
> Bay 22, 4067, B32
> University of Southampton
> 
> 
> 
> 
> 