search

cjnaz / rclonesync-V2

A Bidirectional Cloud Sync Utility using rclone
MIT License
355 stars 39 forks source link

Occasional googleapi error 401 thwarts subsequent syncs #50

Closed 3ter closed 4 years ago

3ter commented 4 years ago

Right before the error I had successful syncs

Mai 29 07:48:54 dristar perl[9030]: 2020-05-29 07:48:54,280:  >>>>> Successful run.  All done.

But then after the following error no more syncs were executed

Mai 29 07:53:59 dristar perl[9192]: 2020/05/29 07:53:59 Failed to lsl: couldn't list directory: googleapi: Error 401: Invalid Credentials, authError
Mai 29 07:53:59 dristar perl[9168]: 2020-05-29 07:53:59,967:    WARNING  rclone lsl try 1 failed.            -
Mai 29 07:54:00 dristar perl[9202]: 2020/05/29 07:54:00 Failed to lsl: couldn't list directory: googleapi: Error 401: Invalid Credentials, authError
Mai 29 07:54:00 dristar perl[9168]: 2020-05-29 07:54:00,467:    WARNING  rclone lsl try 2 failed.            -
Mai 29 07:54:02 dristar perl[9211]: 2020/05/29 07:54:02 Failed to lsl: couldn't list directory: googleapi: Error 401: Invalid Credentials, authError
Mai 29 07:54:02 dristar perl[9168]: 2020-05-29 07:54:02,337:    WARNING  rclone lsl try 3 failed.            -
Mai 29 07:54:02 dristar perl[9168]: 2020-05-29 07:54:02,337:    ERROR    rclone lsl failed.  Specified path invalid?  (Line 324) -

As I read the script this error handling is on purpose. I think this error could be due to intermittent Internet connection (mine is shaky at the moment) so I don't think it should hinder subsequent syncs from being executed.

Can I just delete those two ERROR files created in the working directory?

3ter commented 4 years ago

It most probably has been an issue with the time. Funny thing I had this problem a few days ago already and I didn't have to reauthenticate, it just worked again, after I did a --first-sync. This time though, even rclone didn't want to talk to the remote anymore so I did that part of rclone config again and the --first-sync afterwards and it seems fine now.

I have to watch the issue with the time, though. I suspect that it's the dual boot system I'm using. I should have run timedatectl set-local-rtc 1 --adjust-system-clock earlier I suppose...