Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iRODS support is broken in versions of Cyberduck since 5.2.3 #9913

Closed
cyberduck opened this issue Apr 6, 2017 · 1 comment
Closed

iRODS support is broken in versions of Cyberduck since 5.2.3 #9913

cyberduck opened this issue Apr 6, 2017 · 1 comment
Labels
bug duplicate irods IRODS Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Apr 6, 2017

02edc53 created the issue

We run a large storage facility for academic researchers based on the iRODS middleware and have been recommending Cyberduck to users who prefer a GUI. In recent versions of Cyberduck the support for iRODS has broken and it is not possible to authenticate. The version we are therefore asking users to stay with is 5.2. All newer versions that I have tested fail to connect.

The issue has been discussed on the iRODS-chat mailing list at https://groups.google.com/forum/#!searchin/iROD-Chat/cyberduck%7Csort:relevance/irod-chat/F1HaH4BGEcs/aGQgRsz7AQAJ

I'm replicating it here:

"We're noticing problems with the current version of Cyberduck and PAM authentication. Version 5.2 was fine but after upgrading to 5.3 PAM logins fail with:

Connection failed
Error code received from iRODS: -319000

Logging in with a non-PAM account still works

Looking through the irods server logs there seems to have been a change:

The older, working version simply has: (username replaced with xxxxxxx)

Jan 19 14:53:14 pid:13907 NOTICE: Agent process 38176 started for puser=xxxxxxx and cuser=xxxxxxx from 144.82.115.64

whereas the newer, failing version has:

Jan 19 14:54:58 pid:13907 NOTICE: Agent process 38245 started for puser=xxxxxxx and cuser=xxxxxxx from 144.82.8.64
Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38247 started for puser=xxxxxxx and cuser=xxxxxxx from 144.82.8.64
Jan 19 14:54:59 pid:38247 NOTICE: readAndProcClientMsg: received disconnect msg from client
Jan 19 14:54:59 pid:38247 NOTICE: Agent exiting with status = 0
Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38248 started for puser=xxxxxxx and cuser=PAM:xxxxxxx from 144.82.8.64
Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38247 exited with status 0
Jan 19 14:54:59 pid:13907 NOTICE: Agent process 38250 started for puser=PAM:xxxxxxx and cuser=PAM:xxxxxxx from 144.82.8.64
Jan 19 14:54:59 pid:38250 NOTICE: rsAuthCheck: chlCheckAuth status = -319000

I've tested a few versions now on Windows (7,8 and 10) and macOS and it seems that it's been broken on all of them since 5.3.0.

My guess of the culprit change from the log is:

  • [Feature] Use multiple connections in browser for parallel background task executions

I hope it's possible to re-enable full iRODS support as Cyberduck has been very useful to a lot of researchers, especially those who have to transfer large (of the order of 1TB) files where iRODS' parallel transfer support is useful.

Many thanks,

Daniel.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 7, 2017

02edc53 commented

Apologies - the search I made of issues prior to submitting this didn't reveal anything but I've now noticed

https://trac.cyberduck.io/ticket/9872

I'm investigating further but hope that this has fixed the issue.

Sorry.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug duplicate irods IRODS Protocol Implementation
Projects
None yet
Development

No branches or pull requests

1 participant