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

Re-authentication failure #7608

Closed
cyberduck opened this issue Nov 14, 2013 · 10 comments
Closed

Re-authentication failure #7608

cyberduck opened this issue Nov 14, 2013 · 10 comments
Assignees
Labels
bug fixed openstack version:4.4
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Nov 14, 2013

3f847de created the issue

I like your program but I continually have this bug. Windows 7. I've tried on a couple different machines. This has been going on for a long time. I've updated to the latest version a week ago and still have this problem. It just flickers between "Listing directory" and whatever else was down at the bottom of the window already (e.g. 0 files). Sometimes I can hit STOP to break the cycle and then try again but usually I have to close the program and try again. It happens almost daily.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 15, 2013

@dkocher commented

Plus attach the file cyberduck.log in the application support directory.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 18, 2013

@dkocher commented

Please reopen the ticket with more details if available if still an issue with the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 3, 2014

3f847de commented

This continues to happen, even with your most current version, and even on other machines where I have tested, including on Win 2008 and Win 2012 Server. I have shared the log file with you of one such instance of it cycling. If it matters, I am usually connecting to Rackspace cloud or a Windows IIS-based FTP site, and I leave your program open overnight an often find the cycling problem a day or more later when I go back and hit refresh.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 12, 2014

@dkocher commented

Replying to [comment:4 gordon.seay@…]:

2013-11-19 18:38:14,996 [background-1] FATAL ch.cyberduck.ui.AbstractController - Unhandled exception running background task null
java.lang.NullPointerException
	at org.apache.http.impl.client.AbstractHttpClient.determineTarget(AbstractHttpClient.java:814)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1075)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:1050)
	at ch.iterate.openstack.swift.Client.authenticate(Client.java:212)
	at ch.iterate.openstack.swift.Client.authenticate(Client.java:202)
	at ch.iterate.openstack.swift.Client.authenticate(Client.java:190)
	at ch.iterate.openstack.swift.Client.execute(Client.java:371)
	at ch.iterate.openstack.swift.Client.listObjectsStartingWith(Client.java:442)
	at ch.cyberduck.core.openstack.SwiftObjectListService.list(SwiftObjectListService.java:67)
	at ch.cyberduck.core.openstack.SwiftSession.list(SwiftSession.java:158)
	at ch.cyberduck.ui.action.SessionListWorker.run(SessionListWorker.java:62)
	at ch.cyberduck.ui.action.SessionListWorker.<bridge>run(SessionListWorker.java:37)
	at ch.cyberduck.ui.threading.WorkerBackgroundAction.run(WorkerBackgroundAction.java:43)
	at ch.cyberduck.ui.threading.WorkerBackgroundAction.<bridge>run(WorkerBackgroundAction.java:29)
	at ch.cyberduck.core.threading.AbstractBackgroundAction.call(AbstractBackgroundAction.java:112)
	at ch.cyberduck.core.threading.SessionBackgroundAction.call(SessionBackgroundAction.java:173)
	at ch.cyberduck.ui.AbstractController$BackgroundCallable.call(AbstractController.java:153)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:167)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:604)
	at ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:57)
	at java.lang.Thread.run(Thread.java:937)

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 12, 2014

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 13, 2014

3f847de commented

How does one get this fix?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 13, 2014

@dkocher commented

Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 30, 2014

3f847de commented

I still haven't been able to get a snapshot build or even any update. The updater isn't working. I have tried regularly since your response but always see: "An error occurred during installation. please try again later. Unable to check for updates, the server file failed to load. bad read of entry 0 from compressed archive."

Now what? I would really like to get this resolved. My current version is still 4.4.3.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 30, 2014

@dkocher commented

Replying to [comment:12 gordon.seay@…]:

I still haven't been able to get a snapshot build or even any update. The updater isn't working. I have tried regularly since your response but always see: "An error occurred during installation. please try again later. Unable to check for updates, the server file failed to load. bad read of entry 0 from compressed archive."

Now what? I would really like to get this resolved. My current version is still 4.4.3.

Pease try to install manually from (https://update.cyberduck.io/windows/nightly/)(https://update.cyberduck.io/windows/nightly/).

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 31, 2014

3f847de commented

I have installed the newest nightly version. However, when I tried checking for updates thereafter (even though there should be none), I again received the error: "An error occurred during installation. please try again later. Unable to check for updates, the server file failed to load. bad read of entry 0 from compressed archive."

@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 fixed openstack version:4.4
Projects
None yet
Development

No branches or pull requests

2 participants