-
-
Notifications
You must be signed in to change notification settings - Fork 849
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
Bug: A libcurl function was given a bad argument on handle null #2209
Comments
This is the issue - the file cannot be read or accessed and is causing an access issue. Either the path truly does not exist, but the application thinks it does, or there is a bug lurking which will require verbose debug logs for analysis.
You are running an obsolete Docker container ... which is due to the build process when v2.4.21 was released being broken, see #2163 for details. Please can you run the Docker container 'edge' rather than 'latest' and see how this goes in the first instance. |
Ah I have been pulling the Edge but running latest.
ok now running with edge and have turned on debugging, piped to a log file.
Will provide the full log if it fails again. It usually takes a day. I got a lot of files |
Still the same error, I will email you the full log file but here is the error message
|
Please can you test the following PR to further investigate your issue:
As you are also using Docker, you will need to follow the instructions to build a custom Docker image as listed here: https://github.com/abraunegg/onedrive/blob/master/docs/Docker.md#build-instructions When running the PR, your version should be: |
It appears the PR has fixed the issue. Here are the details and build Showing that I am on the right branch
Build
Running that specific tagged docker container
Onedrive has continued working after passing this point which was failing on the edge version
|
@eperry You should be able to use then the updated 'edge' Docker container in a few hours. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Describe the bug
I am having problems with the docker build of Onedrive. I have tried a few different images you have publish
I have purged the sqlite and other files a couple of times. Based on troubleshooting from other tickets I have read of older issues. Since I am using the stock image provided for docker I wanted to see your thoughts before doing anything drastic.
Here is the error, Followed by:
ls -altr inside the docker container
![image](https://user-images.githubusercontent.com/6170692/200455532-72da0c91-1c00-4a6a-9ea4-f120c7b8abf2.png)
ls -altr on the physical system
![image](https://user-images.githubusercontent.com/6170692/200456274-a5afea7a-b528-4a12-bef7-8fa58a09cff8.png)
OneDrive online showing the file is there.
Operating System Details
Client Installation Method
From Distribution Package
OneDrive Account Type
Personal
What is your OneDrive Application Version
Application version: 2.4.20
What is your OneDrive Application Configuration
What is your 'curl' version
Where is your 'sync_dir' located
Local
What are all your system 'mount points'
What are all your local file system partition types
How do you use 'onedrive'
use it as I expect normal usage is, which is to backup files to onedrive
Steps to reproduce the behaviour
provided it above
Complete Verbose Log Output
Screenshots
No response
Other Log Information or Details
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: