Mismatch in timezones causes synchronize to detect change when there is no change to the file :: Support Forum

yashgt
Joined:: 2023-03-22
Posts:: 7
Location:: India

Mismatch in timezones causes synchronize to detect change when there is no change to the file

2023-05-10 16:05

I transferred 2 files successfully using synchronize. I see them on the server as:

-rw-r--r--. 1 ec2-user ec2-user 12838665 Mar 19 07:10 proddata/KTCL-master-data-20230318.xlsx
-rw-r--r--. 1 ec2-user ec2-user 13033878 Mar 20 16:47 proddata/KTCL-master-data-20230321.xlsx

When I run synchronize again:
The WinSCP logs says:

. 2023-05-10 20:23:46.368 Local file 'D:\proddata\KTCL-master-data-20230318.xlsx' [2023-03-19T07:10:12.625Z] [12838665] is modified comparing to remote file 'proddata/KTCL-master-data-20230318.xlsx' [2023-03-19T01:40:12.000Z] [12838665]
. 2023-05-10 20:23:46.369 Local file 'D:\proddata\KTCL-master-data-20230321.xlsx' [2023-03-20T16:47:40.021Z] [13033878] is modified comparing to remote file 'proddata/KTCL-master-data-20230321.xlsx' [2023-03-20T11:17:40.000Z] [13033878]

And then it transfers the files again.

The WinSCP is running on a Win Laptop in IST timezone.
The server uses UTC.
This is on WinSCP 5.21.7.

Reply with quote

martin◆ Site Admin
Joined:: 2002-12-10
Posts:: 41,517
Location:: Prague, Czechia

Re: Mismatch in timezones causes synchronize to detect change when there is no change to the file

2023-05-11

Please post session log file both for the session that transfers the files originally and the session that re-transfers the files again.

Reply with quote

Guest

File transfer logs

2023-05-11 10:12

Here are the logs. I am using SCP protocol.

winscp2.log (29.38 KB)

Description: Second transfer. The same files get transferred again as WinSCP thinks the local files are modified. The local timezone is 4.5 hours ahead of UTC.

winscp1.log (27.93 KB)

Description: First transfer

Reply with quote

yashgt
Joined:: 2023-03-22
Posts:: 7
Location:: India

2023-05-11 11:31

In the remote directory listing, WinSCP sees the timestamp as
2023-03-19 07:10:12

When doing the comparison, it shifts the timestamp of the remote file to 2023-03-19T01:40:12.000Z.

Not sure why this behaviour.

Reply with quote

martin◆ Site Admin

Re: File transfer logs

2023-05-15

Timezone mismatch with SCP is expected. Why are you using SCP in the first place? Use SFTP.
If you want to stick with SCP, configure the timezone offset in session settings.
https://winscp.net/eng/docs/ui_login_environment

Reply with quote

Mismatch in timezones causes synchronize to detect change when there is no change to the file