keep losing lsl file #10
Comments
|
Yes please. Run with --verbose on both the --first-sync run and the second
run. Also please carefully read troubleshooting.md and readme.md.
Cjn
…On Thu, Sep 6, 2018, 9:40 PM silenceleaf ***@***.***> wrote:
When I sync my dropbox with rclone, first time running everything works
great, but second time it remind me missing lsl files, and let me using
--first-run parameter.
do you need more detail log?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOKq4RlTv354bOKMNedLZZIn5iu2e7Jaks5uYfi4gaJpZM4WeK1s>
.
|
|
**log is here ** Sep 11 23:16:07 server1 systemd[1]: Started Rclone Sync Dropbox. <after this "can not connect to dropbox error" all the sync become "losing lsl file" > Sep 12 17:17:50 server1 systemd[1]: Started Rclone Sync Dropbox. |
|
I couple interesting things here. It looks like your prompt ( rclone is generating the error when trying to get the file list (lsl) for dropbox:. The problem is likely in the setup of rclone, or a temporary problem with dropbox. What version of rclone are you using? Please run and copy/paste I also ran with the latest beta without errors: Try running the rclone lsl manually from the command line: When you figure this out, please post the root cause and solution. |
|
Any news? Did you get this resolved, and may I close this issue? If so, what was the issue, for others' benefit. |
|
No, the service running very smooth for coupe of days, the loosing lsl file error go back! Background: The rclonesync is scheduled by systemd-timer, running every 4 hour Seems error happens when connect to dropbox failure, and then all afterwards sync attempts will be failure(Must manually run --first-sync to recover.). As my understand, for a robust system, one time failure should not affect afterwards operation. log is here: Sep 22 12:28:09 server1 systemd[1]: Started Rclone Sync Dropbox. |
|
Ah. Turn on the check access feature. You will need to place one or more
RCLONE_TEST files in your sync tree. See the documentation. This feature
is intended to address the intermittent cloud service access issue
gracefully. If the run fails to find the test files it will abort and try
again next time. I run this script every 30min for months without a
critical abort, fyi.
|
|
Any luck with --check-access? Can I close this issue? fyi, new version 2.3 just posted. |
|
Sorry for the late response! I think that's not a big deal, you can close this thread. |
|
I have a small change request here: if I use "--check-access" option, rather than make the file name strictly "RCLONE_TEST", let's make it contains "RCLONE_TEST". such as I want to use ".RCLONE_TEST"(make it hidden file) or "RCLONE_TEST.txt" (write something inside) Thanks for this handy tools, thanks for your effort! |
|
Good idea. Alternatively, I might add a switch to allow selection of the
test filename, overriding the current default. or wildcarding the filter (*
RCLONE_TEST*) may be cheap enough, but allowing user selection is
most flexible and cheap/easy to implement. Sound reasonable?
|
|
Added |
sounds good! |
|
I'm facing this error now even with v2.4 and using RCLONE_TEST with --check-filename. Which logs would you require? I'll add some here as I get them. EDIT: Logs --first-sync with --dry-run |
|
This current issue (#10) is closed, and the issues in your log are not related to issue #10. |
|
Well, the problem is not actually with the logs. I am actually facing the issue of losing the lsl files in ~/.rclonesyncwd, which seems like it's not getting reflected in the logs. I am also aware of the google docs thing, and I'm fine with them not being synced. How would you suggest to get logs the next time it happens? Because the lsl files are lost at random days (approx. twice a week), I have no idea as to catch the reason for the error when it occurs. |
|
Do you also have |
|
Yup. I added the RCLONE_TEST file in the root directory for all of my cloud storage drives and started using that flag ever since this bug started occurring for me. I have now started logging every sync into a logfile, and I'll report here when I face this issue next. |
|
Just to be sure, post the |
|
The command is this: This is what that line says: |
|
For debug, turn on verbose ( |
|
Did it. Here's the output: |
|
The invocation (command line) looks fine. Let it run with output to the log file until it fails. |
|
Lost the lsl files for two cloud sync setups (Google Drive and Dropbox; Box wasn't affected). Here's the part of the logfile for today (22/11/2018): rclonesync.log I suspect that this happens when rclonesync gets killed, probably when shutting down at a time when the cron job for rclonesync is running. |
|
The first error is that the Path2 You might want to weigh in on #8. The missing Makefile case is missing from the discussion since it doesn't have a risk of data loss, but is not well handled. If you can narrow in on the issue, please open a new issue. |
When I sync my dropbox with rclone, first time running everything works great, but second time it remind me missing lsl files, and let me using --first-run parameter.
do you need more detail log?
The text was updated successfully, but these errors were encountered: