Closed DIYglenn closed 5 years ago
I tried logging out, and logging in again. I wrote the same device name, and added the smallest path I'm backing up, which was approx 20GB. It now did the exact same thing - sync all files (but not actually upload anything) come to a finish with "Up to date!" and immediately restart the process... I can hear the drives being accessed constantly, so it is definitely checking the files over and over again, never finishes.
I've stopped the service for now. I can't have it hammering the drives like this.
What could the reason be for this? It's as if Jotta-CLI sees that everything is up-to-date, but still initiates a full re-sync on the last folder it was working on.
I tested some more, and it seems to keep continuing in a loop with rechecks once it's finished. Are there any files JottaCloud writes its status to that it might not have permissions for?
This is on a Ubuntu 16.04 LXC on a QNAP NAS. I found someone else who's having the same issue: http://forum.jotta.no/jotta/topics/jottaclou-cli
Found the log file, here are some snippets. Please bear in mind that all files ARE uploaded and in backup, but it just keeps retrying in a loop.
pid:62 2019/02/04 13:12:49 Error uploading {
"Name": "05 Fly From Here Part IV - Bumpy Rid.mp3",
"Path": "/Musikk/Music/Yes/Fly From Here/05 Fly From Here Part IV - Bumpy Rid.mp3",
"Size": 5415316,
"Modified": "2012-06-08T15:58:48Z",
"Created": "2019-01-16T07:42:49.976722261Z",
"Checksum": "",
"State": "Added"
} => Post https://api.jottacloud.com/files/v1/allocate: dial tcp: lookup api.jottacloud.com on [::1]:53: read udp [::1]:51665->[::1]:53: read: connection refused
pid:62 2019/02/04 13:12:49 Error uploading {
"Name": "01 Fly From Here - Overture.mp3",
"Path": "/Musikk/Music/Yes/Fly From Here/01 Fly From Here - Overture.mp3",
"Size": 4546708,
"Modified": "2012-06-08T15:58:39Z",
"Created": "2019-01-16T07:42:49.976722261Z",
"Checksum": "",
"State": "Added"
} => Post https://api.jottacloud.com/files/v1/allocate: dial tcp: lookup api.jottacloud.com on [::1]:53: read udp [::1]:39342->[::1]:53: read: connection refused
pid:62 2019/02/04 13:12:49 Error uploading {
"Name": "02 Fly From Here Part I - We Can Fly.mp3",
"Path": "/Musikk/Music/Yes/Fly From Here/02 Fly From Here Part I - We Can Fly.mp3",
"Size": 14413552,
"Modified": "2012-06-08T15:58:42Z",
"Created": "2019-01-16T07:42:49.976722261Z",
"Checksum": "",
"State": "Added"
} => Post https://api.jottacloud.com/files/v1/allocate: dial tcp: lookup api.jottacloud.com on [::1]:53: read udp [::1]:40778->[::1]:53: read: connection refused
pid:62 2019/02/04 13:12:49 Error uploading {
"Name": "03 Fly From Here Part II - Sad Night.mp3",
"Path": "/Musikk/Music/Yes/Fly From Here/03 Fly From Here Part II - Sad Night.mp3",
"Size": 16049500,
"Modified": "2012-06-08T15:58:44Z",
"Created": "2019-01-16T07:42:49.976722261Z",
"Checksum": "",
"State": "Added"
} => Post https://api.jottacloud.com/files/v1/allocate: dial tcp: lookup api.jottacloud.com on [::1]:53: read udp [::1]:43769->[::1]:53: read: connection refused
pid:62 2019/02/04 13:12:49 Unable to refresh : Post https://api.jottacloud.com/auth/v1/token: dial tcp: lookup api.jottacloud.com on [::1]:53: read udp [::1]:40679->[::1]:53: read: connection refused
pid:62 2019/02/04 13:12:49 Error uploading {
"Name": "04 Fly From Here Part III - Madman A.mp3",
"Path": "/Musikk/Music/Yes/Fly From Here/04 Fly From Here Part III - Madman A.mp3",
"Size": 12652324,
"Modified": "2012-06-08T15:58:46Z",
"Created": "2019-01-16T07:42:49.976722261Z",
"Checksum": "",
"State": "Added"
And the last ones:
pid:62 2019/02/04 13:12:51 Error uploading {
"Name": "04 Buddy Holly.mp3",
"Path": "/Musikk/Music/Weezer/Weezer (Blue Album)/04 Buddy Holly.mp3",
"Size": 5142528,
"Modified": "2012-04-07T18:14:18Z",
"Created": "2019-01-16T07:42:49.977722261Z",
"Checksum": "",
"State": "Added"
} => Invalid statuscode 401
pid:62 2019/02/04 13:12:51 Error uploading {
"Name": "03 The World Has Turned and Left Me.mp3",
"Path": "/Musikk/Music/Weezer/Weezer (Blue Album)/03 The World Has Turned and Left Me.mp3",
"Size": 8341504,
"Modified": "2012-04-07T18:14:18Z",
"Created": "2019-01-16T07:42:49.977722261Z",
"Checksum": "",
"State": "Added"
} => Invalid statuscode 401
pid:62 2019/02/04 13:12:51 Error uploading {
"Name": "02 Back To the Shack.m4a",
"Path": "/Musikk/Music/Weezer/Everything Will Be Alright In the End/02 Back To the Shack.m4a",
"Size": 6830763,
"Modified": "2016-02-20T09:59:15Z",
"Created": "2019-01-16T07:42:49.977722261Z",
"Checksum": "",
"State": "Added"
} => Invalid statuscode 401
pid:62 2019/02/04 13:12:51 Error uploading {
"Name": "02 No One Else.mp3",
"Path": "/Musikk/Music/Weezer/Weezer (Blue Album)/02 No One Else.mp3",
"Size": 5951488,
"Modified": "2012-04-07T18:14:18Z",
"Created": "2019-01-16T07:42:49.977722261Z",
"Checksum": "",
"State": "Added"
} => Invalid statuscode 401
pid:62 2019/02/04 13:12:57 Updating account info
pid:62 2019/02/04 13:14:55 Deferring scan of /Musikk while waiting for previous queue to finish
pid:62 2019/02/04 13:15:05 Running scan of /Musikk
pid:62 2019/02/04 13:17:15 Deferring scan of /Musikk while waiting for previous queue to finish
pid:62 2019/02/04 13:17:25 Running scan of /Musikk
pid:62 2019/02/04 13:19:35 Deferring scan of /Musikk while waiting for previous queue to finish
pid:62 2019/02/04 13:19:45 Running scan of /Musikk
pid:62 2019/02/04 13:21:55 Deferring scan of /Musikk while waiting for previous queue to finish
ubuntu@JottaCloud:~$
Interesting! I think I figured it out - I took a closer look at the dates, and noticed they were an hour off! The LXC had the wrong timezone, and this probably makes the connection invalid (although it still has uploaded my files...?)
Running this command:
sudo dpkg-reconfigure tzdata
And choosing the correct continent + city has resulted in:
------------------------------------------------------------------------------
Path : /Musikk
Files : 2457 files / 18.70GiB
Status : Up to date!
------------------------------------------------------------------------------
OK
I'll add my other folders and confirm. Hopefully my files ARE actually backed up correctly though...
I also want to add; I'm using 2FA (2-factor authentication) which I know some services has struggled with - but it seems to work fine.
All directories added and synced. “Up-to-date!”
Anyone else experiencing the same issue, double check date and time zone with the command
date
This solved this issue.
Make sure you are running the latest version of jotta-cli before reporting an issue.
jotta-cli release (
jotta-cli version
): 0.4.4986 Description of problem: I have 4 paths added, and the last of them is approx 3TB. After it finished uploading, it's been "reuploading" the files ever since. It goes through the whole folder, taking hours, but no data is actually uploaded. When it's finished and I check the status, it says "Up to date" but immediately starts another sync. Expected: All paths should be uploaded and synced, and say "Up to date"jotta-cli status (
jotta-cli status
):Relevant logs for the issue (
cat ~/.jottad/jottabackup.log
)Traceback
Additional info: