Uploaded files to OpenDrive are incomplete?

I used odrive to sync files to my OpenDrive account through the Python CLI tool in linux. I also use it to sync the same files to my Amazon Cloud Drive account.

What I am finding is that while my files are saying they are “complete” and synced to OpenDrive, and when I check my OpenDrive account it shows the files there and the size they are supposed to be, and the correct date and time they were uploaded, when I try to download them, they are NOT complete. I can upload a 1.5GB file, but when I go to download it through odrive, it can not download it. If I go to the OpenDrive website if I download the file, I get maybe 15MB of it and then it stops.

I upload all the same files to Amazon as well(backup cloud) and I do not have the same problem. I can upload to Amazon and when I try to download the file, it works as it should.

Is anyone else experiencing this? This is a little worry some as I’ve uploaded well over a TB of files to OpenDrive through odrive and I am a little concerned that one day when I try to get them back, I will not be able to.

James

Hi @JamesGTRS,
This is definitely odd. Since the size and date are listed as correct in OpenDrive, that would indicate that at least OpenDrive thinks they are fully uploaded. We won’t mark a file synced unless the service has replied that the upload was completed successfully.

Do you see the same behavior when you try to download the file from the odrive web client? ( https://www.odrive.com ).
Are you seeing an error when downloading from OpenDrive, or is the download just dying?

Yes, it definitely odd. Even when I the logs in OpenDrive, it shows the uploads and the correct file sizes. Watching my network traffic on my server also indicates the entire file is being sent to OpenDrive.

I do have files that do not upload and odrive will continue to try and upload them until completed, which happens from time to time.

I see the same behavior when I try to download the file from the odrive webclient, the odrive application to sync it, the OpenDrive Windows application or downloading from the Opendrive webclient. They all download the exact same file size. 15,520kb.

I don’t see an error when download from Opendrive, just that it attempts to download, gets to 15,520kb then just stops like it’s complete. It just dies.

I thought maybe it was my odrive CLI application on my linux server and updated it from version 6xx to the latest 9xx. I restarted the application, reauthorized it, resynced…still had the same issue this morning.

I am going to try and download the files from my server and upload them through the odrive Windows application and see what happens.

Note, the same issue does not happen with Amazon Cloud Drive.

It may be beneficial to also reach out to OpenDrive and have them verify the size of the files in their storage. I am thinking that this is more likely an issue they are hitting on transfer rather than not storing the complete file, but they should be able to tell us for sure.

At the very least I would expect them to provide an exception since they are only transferring a small portion of the size they have recorded.

I tried syncing through Windows on the regular Windows odrive client and came up with the same result.

I am going to try through OpenDrive…if it works through their app, then they will say the problem is with odrive. If it doesn’t work, I will pursue it with OpenDrive.

I am curious to know what you found. odrive is using a different interface than OpenDrive’s native app, so the results may be different there, if the issue is the interface.

Uploading through OpenDrive, then downloading through OpenDrive works as it should. I uploaded a 1.9GB file, then was able to download it through OpenDrive, the full 1.9GB.

I tried to sync the uploaded file with the windows odrive software, and I was able to sync the file back down through odrive…

So the issue is Odrive uploading to OpenDrive. Although it sends the whole file, and I can see it in my logs in OpenDrive that the full file has been uploaded, when I go to download it, I can’t get the whole file back. When I download a file uploaded through odrive, it fails at 15,520kb.

Smaller files seem to be just fine. If it’s only a couple of MB, I can download without an issue. I synced a 4MB image and I could download it and use it just fine.

I got a chance to perform my own testing and I see some definite issues with OpenDrive. I also tested OpenDrive using a standard WebDAV client and I see the same issue. I am using files between 12 and 30 MB in size.

What I am seeing is that, after transferring all of the data up, the connection stalls waiting for a response from OpenDrive. After a refresh OpenDrive reports that the file is there. It is marked as synced (because it is reported to odrive to be the same size and date). Trying to download the file ends up with a truncated file (I am seeing them cut off at around 10MB).

Have you contacted them about this yet? I am going to reach out to them, as well. Something is definitely wrong.

I have had issues with the webdav client from OpenDrive for about 12 months now, which is why I was excited to use odrive.

When I bring up some of those issues I had with the webdav client for OpenDrive, the response I get from OpenDrive is that it is “Beta” so it’s not fully supported. It did work very very well for a long time then in the last 12 months or so things went downhill.

James

Thanks.
I am waiting to hear back from OpenDrive on this issue. I will update this post once I have some news.

Have you heard anything from them? My issue still remains, but I found something else now too.

This is from today after running the odrive python cli agent on my linux box. It logs in all day long.

Time Log Type IP Name File Size Details App
Nov 01, 2016, 08:30pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 08:26pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 08:21pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 08:04pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 08:02pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:56pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:47pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:46pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:30pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:30pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:30pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:30pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:30pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:30pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:30pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:26pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:21pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:02pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:01pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:53pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:46pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:43pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:25pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:20pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:03pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:02pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:00pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:52pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:46pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:39pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:24pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:20pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:02pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:00pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:51pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:39pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:34pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:29pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:29pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:29pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:29pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:29pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:29pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:29pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:24pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:19pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:00pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:59pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:59pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:49pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:39pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:30pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:23pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:19pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:59pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:59pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:48pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:38pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:24pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:22pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:17pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:59pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:58pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:51pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:48pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:38pm USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:21pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:20pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:17pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:58pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:58pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:58pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:58pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:58pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:58pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:51pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:47pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:21pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:16pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:16pm USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 11:58am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 11:50am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 11:45am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 11:34am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 11:19am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 11:16am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 11:11am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 10:58am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 10:57am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 10:46am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 10:45am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 10:31am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 10:18am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 10:16am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 10:07am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 10:01am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 09:56am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 09:56am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 09:44am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 09:44am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 09:31am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 09:17am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 09:15am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 09:01am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 08:56am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 08:44am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 08:44am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 08:31am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 08:16am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 08:13am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:56am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:55am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:44am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:42am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:30am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:16am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 07:13am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:55am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:52am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:43am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:41am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:29am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:15am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 06:11am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:55am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:48am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:41am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:41am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:28am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:12am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:09am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 05:02am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:55am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:44am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:41am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:40am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:28am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:12am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 04:09am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:56am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:40am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:40am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:39am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:28am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:09am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 03:08am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:55am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:48am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:42am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:38am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:37am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:35am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:27am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:07am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 02:07am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:55am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:37am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:37am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:31am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:31am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:27am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:07am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 01:07am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:52am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:37am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:37am USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:27am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:22am USER LOGIN 38.108.185.63 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:09am USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:07am USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Nov 01, 2016, 12:07am USER LOGIN 38.108.185.65 API: 2.0 | APP v1.1.1 WEBDAV
Oct 31, 2016, 11:52pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV
Oct 31, 2016, 11:39pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Oct 31, 2016, 11:39pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Oct 31, 2016, 11:39pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Oct 31, 2016, 11:39pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Oct 31, 2016, 11:39pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Oct 31, 2016, 11:39pm USER LOGIN 38.108.185.62 API: 2.0 | APP v1.1.1 WEBDAV
Oct 31, 2016, 11:37pm USER LOGIN 38.108.185.64 API: 2.0 | APP v1.1.1 WEBDAV
Oct 31, 2016, 11:37pm USER LOGIN 38.108.185.67 API: 2.0 | APP v1.1.1 WEBDAV

I am still waiting to hear back from OpenDrive on this issue. I pinged them again today to ask if they’ve identified the problem.

As for the logins, the Agent is periodically checking OpenDrive for changes. It should be trying to re-use its sessions, but OpenDrive may be expiring them after a while. It seems like multiple threads cause multiple logins on OpenDrive.

You do not see this behavior with the Desktop client?

I have this on a lot of computers…and all the IPs are the same, so I don’t know which is which.

Yeah I noticed that on my testing. OpenDrive seems to report its own IP addresses instead of the clients :confused:

In any case, it is expected behavior as the client will need to login numerous times while it periodically checks the source for changes. If you have multiple clients running then the frequency will increase.

By the way, I am still waiting for a response from OpenDrive. I will be sure to ping this thread once I hear back.

It looks like odrive has completely stopped working with OpenDrive now. In checking logs and any files I’ve put into odrive, they are not showing up in opendrive at all. There isn’t even the attempt to upload.

It shows “File Upload Closed” for all my files that have come through odrive, but not that it was uploaded. When I upload a file through the OpenDrive app, it shows “File Upload” for the file, then “File Upload Closed” for the file.

If odrive is using the webdav system that OpenDrive provides, that could be the reason. I used to use the webdav system provided by OpenDrive previously and it worked great, then they started limiting file uploads and eventually it was just completely broken. odrive did work for a while and was great, but now I can’t use it for OpenDrive.

Amazon Cloud Drive seems to be just moving along no problem.

Hi @JamesGTRS,
Unfortunately I have not gotten much movement on the OpenDrive side after multiple inquiries.

It is my currently recommendation to not use odrive with OpenDrive, at this time.

We are going to remove support for the OpenDrive integration, at least for now. The issues we are seeing there are too troubling to allow to continue and we have no way to combat them or even detect them from our side.

1 Like