You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can connect to our internal iRODS instance directly after the creation of a new bookmark, using a .cyberduckprofile file that I created. The .cyberduckprofile file looks like this:
When I close cyberduck and start it again, I'd like to connect using the bookmark that it created automatically.
Double-clicking the bookmark leads to the display "Connection opened" with the right server name in the Windows tray bar. However, the connection is not really opened and the cyberduck.log says:
2016-06-03 07:35:19,845 [background-1] FATAL ch.cyberduck.core.threading.SessionBackgroundAction - Failure running background task. zone is null or empty
java.lang.IllegalArgumentException: zone is null or empty
at org.irods.jargon.core.connection.IRODSAccount.instance(IRODSAccount.java:113)
at ch.cyberduck.core.irods.IRODSSession.login(IRODSSession.java:136)
at ch.cyberduck.core.KeychainLoginService.authenticate(KeychainLoginService.java:69)
at ch.cyberduck.core.LoginConnectionService.authenticate(LoginConnectionService.java:214)
at ch.cyberduck.core.LoginConnectionService.connect(LoginConnectionService.java:204)
at ch.cyberduck.core.LoginConnectionService.check(LoginConnectionService.java:139)
at ch.cyberduck.core.LoginConnectionService.check(LoginConnectionService.java:146)
at ch.cyberduck.core.threading.SessionBackgroundAction.connect(SessionBackgroundAction.java:218)
at ch.cyberduck.core.threading.SessionBackgroundAction.call(SessionBackgroundAction.java:183)
at ch.cyberduck.core.threading.BackgroundCallable.call(BackgroundCallable.java:51)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:618)
at ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:58)
at java.lang.Thread.run(Thread.java:955)
Checking the bookmark file: the zone (stored as "region" in cyberduck) is really not there, so this explains the error.
I suspect that the reference to the profile in the bookmark (using the Protocol key) is ambiguous. Do you have multiple profiles installed that have Protocol and Vendor set to irods?
Please resolve this issue by setting the Vendor setting to a different value than irods which is already reserved as the protocol identifier. For example use
I can connect to our internal iRODS instance directly after the creation of a new bookmark, using a .cyberduckprofile file that I created. The .cyberduckprofile file looks like this:
When I close cyberduck and start it again, I'd like to connect using the bookmark that it created automatically.
Double-clicking the bookmark leads to the display "Connection opened" with the right server name in the Windows tray bar. However, the connection is not really opened and the cyberduck.log says:
Checking the bookmark file: the zone (stored as "region" in cyberduck) is really not there, so this explains the error.
Can you fix cyberduck please, so that it saves the zone ("region") info in the bookmark as well?
I tested with 5.0 and the previous release of Cyberduck.
BTW, ideally the zone ("region") would be configurable as a user option. But multiple .cyberduckprofile files for multiple zones should work as well.
Thanks+Regards,
Carsten
The text was updated successfully, but these errors were encountered: