Bisync missed syncing changed file - no error, no warning

[nielash (Niel)]

@vtcifer

2023-08-23 19:55:31 INFO  : Synching Path1 "gdrive{qOqdu}:lichswarm/" with Path2 "/data/lichswarm/"
2023-08-23 19:55:31 ERROR : Bisync critical error: cannot find prior Path1 or Path2 listings, likely due to critical error on prior run

This one is happening because --drive-pacer-min-sleep is a backend-specific flag, which is adding {qOqdu} to the name of your gdrive remote (because Rclone detects an overridden config). Bisync is therefore looking for a listing file named gdrive{qOqdu}_lichswarm..data_lichswarm.path1.lst and not finding it because it's actually named gdrive_lichswarm..data_lichswarm.path1.lst (without the {qOqdu}).

To fix this, you can either:

• Run a --resync (which will regenerate the listing files with the {qOqdu} it wants)
• Use the pacer_min_sleep config parameter instead of the --drive-pacer-min-sleep command flag. (This should remove the {qOqdu} since you are no longer overriding the config.)

Or as a third option, you could manually rename your existing .lst files to include the {qOqdu}, then try again.

More info in the new beta docs.

@vtcifer

2023-08-23 19:56:12 INFO  : Checking access health
2023-08-23 19:56:12 ERROR : Access test failed: Path1 count 0, Path2 count 0 - RCLONE_TEST
2023-08-23 19:56:12 ERROR : Bisync critical error: check file check failed

This one is happening because you included --check-access but Bisync can't find your RCLONE_TEST check-files. Do they exist?