Split irods provider and consumer in two different nodes and cyberduck issue

[Francisco Morales]

Hi, 

I have opened this github issue https://github.com/iterate-ch/cyberduck/issues/18152 regarding connecting cyberduck to irods via irods protocol instead of eg webdav. As explained in the ticket, the connection works (list files, upload, download) when there is a single irods node that serves as a provider and consumer (both the icat and resources are attached to the same vm). Now, when the setup is split in two different machines, the connection breaks. More specifically, we can tell cyberduck to connect directly to the icat node and listing files works but uploading/downloading fails; while connecting cyberduck directly to the consumer node does not list any data object and upload/downloads subsequently do not work. 

I'm assuming that this behavior is not expected since connecting icommands directly to the consumer node does work.

Any thoughts?

Best regards, 

Francisco

[Terrell Russell]

Hi Francisco,

There should be no difference - agreed, it should work, regardless of where the client (Cyberduck) connects.

What version of iRODS is this?

Can you capture any more of the logs in the iRODS server?   It should never hit that critical error, can you increase the log level?

Have you tried to reproduce this with docker compose?

Terrell

--
--
The Integrated Rule-Oriented Data System (iRODS) - https://irods.org
 
iROD-Chat: http://groups.google.com/group/iROD-Chat
---
You received this message because you are subscribed to the Google Groups "iRODS-Chat" group.
To unsubscribe from this group and stop receiving emails from it, send an email to irod-chat+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/irod-chat/0215dad9-fdcd-427b-9e52-160838b2ec36n%40googlegroups.com.

[Francisco Morales]

Hi Terrel, 

Quick answer first: tested with irods 4.3.4 and 5.0.2. Same behavior observed, although the critical error comes specifically from an irods 5.0.2 instance.

I'll run some more tests with extra logging next week.

Best regards, 

Francisco