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

Jump to bottom

Failed huge file upload to Hubic with command line interface #9310

Closed
cyberduck opened this issue Feb 27, 2016 · 1 comment
Closed

Failed huge file upload to Hubic with command line interface #9310

cyberduck opened this issue Feb 27, 2016 · 1 comment
Assignees
@dkocher
Labels
bug fixed openstack OpenStack Swift Protocol Implementation
Milestone
4.8.3

Comments

@cyberduck
Copy link
Collaborator

21bbfeb created the issue

Server: CentOs 7

When try to upload huge file (250G) to Hubic upload fails after 2 reconnects.
For example - uploads 45Gb, error connection, after this first reconnect good, but second fails with error;

Transfer incomplete…log4j:WARN No appenders could be found for logger (ch.cyberduck.core.threading.SessionBackgroundAction).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

java.lang.Exception
        at ch.cyberduck.core.threading.BackgroundCallable.<init>(BackgroundCallable.java:25)
        at ch.cyberduck.core.AbstractController.background(AbstractController.java:106)
        at ch.cyberduck.cli.Terminal.execute(Terminal.java:452)
        at ch.cyberduck.cli.Terminal.transfer(Terminal.java:348)
        at ch.cyberduck.cli.Terminal.execute(Terminal.java:255)
        at ch.cyberduck.cli.Terminal.open(Terminal.java:150)
        at ch.cyberduck.cli.Terminal.main(Terminal.java:140)
Caused by: java.lang.NullPointerException
        at ch.cyberduck.core.openstack.SwiftLargeObjectUploadFeature.upload(SwiftLargeObjectUploadFeature.java:140)
        at ch.cyberduck.core.openstack.SwiftLargeObjectUploadFeature.upload(SwiftLargeObjectUploadFeature.java:56)
        at ch.cyberduck.core.openstack.SwiftThresholdUploadService.upload(SwiftThresholdUploadService.java:111)
        at ch.cyberduck.core.transfer.UploadTransfer.transfer(UploadTransfer.java:245)
        at ch.cyberduck.core.worker.AbstractTransferWorker$3.call(AbstractTransferWorker.java:382)
        at ch.cyberduck.core.worker.SingleTransferWorker.submit(SingleTransferWorker.java:84)
        at ch.cyberduck.core.worker.AbstractTransferWorker.transfer(AbstractTransferWorker.java:375)
        at ch.cyberduck.core.worker.AbstractTransferWorker.run(AbstractTransferWorker.java:237)
        at ch.cyberduck.core.worker.AbstractTransferWorker.run(AbstractTransferWorker.java:64)
        at ch.cyberduck.core.threading.WorkerBackgroundAction.run(WorkerBackgroundAction.java:110)
        at ch.cyberduck.core.threading.AbstractBackgroundAction.call(AbstractBackgroundAction.java:119)
        at ch.cyberduck.core.threading.SessionBackgroundAction.call(SessionBackgroundAction.java:184)
        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:617)
        at ch.cyberduck.core.threading.NamedThreadFactory$1.run(NamedThreadFactory.java:58)
        at java.lang.Thread.run(Thread.java:745)

Start with command

duck -u my_user -pmy_key --upload cyberduck://hubic@my_gateway/default/Backups/ /backup/huge_250G_file.raw --throttle 2097152 -e resume &
@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 51d3f32.

@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.
Assignees

@dkocher dkocher

Labels
bug fixed openstack OpenStack Swift Protocol Implementation
Projects
None yet
Milestone
4.8.3
Development

No branches or pull requests
2 participants
@dkocher @cyberduck