Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: "Keeping remote directory up to date" sometimes skips uploading a file

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
jtmoonman

"Keeping remote directory up to date" sometimes skips uploading a file

Feature Keeping remote directory up to date... inconsistently uploads a changed file.

Settings


In my case, using WinSCP 5.17.10. WinSCP is monitoring a local Windows 10 NTFS path, synchronized with a remote Linux ext3 path over SSH.
Plenty of free RAM, free CPU, and using a Samsung EVO SSD storage (pretty fast).

The Keeping remote directory up to date... settings:
☑ Update subdirectories
☑ Continue on error
☑ Existing files only

with custom Transfer Settings that ignore dirs .git, .pytest_cache, and files *.pyc.

Observation


Only sometimes does WinSCP upload a local Windows modified file.
Sometimes when I save the file C:\project\path\file1 with inserted or removed contents, the dialog Keeping remote directory up to date... bottom-half log window reads:

    15:00:00 Change in 'C:\project\path' detected

    15:00:01 Watching for changes in 411 directories...
    15:00:02 Change in 'C:\project' detected
    15:00:03 Watching for changes in 413 directories...
    15:00:04 Change in 'C:\project' detected


It fails to upload the file C:\project\path\file1. And the log messages really are 1 second apart.

But sometimes it does correctly upload the file. That log looks like:

    15:00:00 Change in 'C:\project\path' detected

    15:00:01 File 'C:\project\pathfile1' uploaded
    15:00:02 Change in 'C:\project' detected
    15:00:03 Watching for changes in 413 directories...


The pattern is the path changes detected, as reported by the Change ... detected log messages, are inconsistent.

In my real world case, the file is at path depth
C:\Users\user1\path3\path4\path5\path6\path7\foobar.py . WinSCP is watching at local path C:\Users\user1\path3\path4 .