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

Error code received from iRODS: -319000 #9826

Closed
cyberduck opened this issue Jan 24, 2017 · 5 comments
Closed

Error code received from iRODS: -319000 #9826

cyberduck opened this issue Jan 24, 2017 · 5 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 24, 2017

cb85eba created the issue

After upgrading Cyberduck from 5.2.3 to version 5.3.3 the connection to my irods server failed with an error:

Connection failed
Error code received from iRODS: -319000

After downgrading to 5.2.3 it worked again. It seems irods is broken in 5.3.0 and upwards. Using iRODS 4.1.9 with PAM authentication.

Discussion about this issue in IROD-Chat:
(https://groups.google.com/forum/#!topic/iROD-Chat/F1HaH4BGEcs)


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 24, 2017

@dkocher commented

Do you use PAM for authentication?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 24, 2017

cb85eba commented

Replying to [comment:3 dkocher]:

Do you use PAM for authentication?
Yes.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 30, 2017

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 6, 2017

@dkocher commented

In db4cad7.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 8, 2017

@dkocher commented

Reopen for #9872.

@cyberduck cyberduck closed this Mar 8, 2017
@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants