btsync

[firwareslut]

Start a new thread in the development section with regards to what you want to talk about it. then everyone can see it and a history is kept.

[firwareslut]

The NTP server being set to the wrong time zone is causing a problem with my sync. My main servers are set to CET and display the right time. However, because the NAS doesn't support the daylight saving I have to set the clock to GMT. The times are correct on the devices but it appears that btsync is also checking the time zone and refusing to sync. It says that the time difference is greater than 600s (even though it is not).

[Jocko]

:scratch

I don't think that the issue is the daylight offset but with the current version the firmware doesn't handle rightly the hardware time and the system time. Currently, the kernel waits an UTC hardware time but wrongly the firmware tries to set it in local time.

So maybe it is why btsync finds an offset bigger than 2 hours :scratch

With version 15.1, now the hardware time is always set as an UTC time and system time is in local time. We can hope that this resolves this issues.

Could you try to use the GMT as local time on the NAS and see if you can sync your folders?

Note: currently, we use it without issue between Fvdw and me to manage a development folder but we already uses the version 15.1. :mrgreen:

[firwareslut]

How would i set this with command line? I can log in remotely using ssh and test it now.

I can always upgrade 15.1 if you give me the package :D

[Jocko]

In setup menu:
* select the GMT+0 as time zone and disable the ntp server
make now a submit to get.
hwtime=systemtime and both in UTC.
* you can again start NTP server.

About version 15.1, how the firmware handles the hwtime and system with a new NTP server is the first change in version 15.1. So since this change, these files may have been also modified with other improvements and I have to check them to see if they can run with your version 15.0 already patched with the btsync feature :dry (for btsync I already had to write some new files version for you)

So it will be not handy...

If the trick doesn't fix your issue, next week we can try to make a full firmware image version beta to test if you have still this behaviour.

[firwareslut]

Yes that has fixed the issue! Now the hw and system clock match the program syncs correctly. Thanks!

[Jocko]

:applause

Firwareslut, it's a good new because this means that btsync will run correctly with version 15.1

[firwareslut]

I am back to this problem of the sync not working again since the clocks have changed. It's on GMT 0 , the time is correct and I have turned off the NTP. HW time matches the system time. I can't get it to sync again. Have tried GMT+1 also...the clocks are set to AM which is correct (as of testing now).

[Jocko]

Hi firwareslut,

The previous trick to reset the hardware time is valid only for version 15.0.

Currently, with version 15.2, hardware time is always is UTC (localtime -tz offset) and system time in local time. So you shouldn't have again this issue :scratch .

But maybe now is the DST offset the issue...

Currently, to understand well what happens :
What is the right timezone for you ? How do you set it in the setup menu and if you have a DST offset how do you fix it ?

Note: with fvdw we use a sync folder for the firmware development and we don't have this issue :scratch

[Jocko]

Note:

We succeeded to implement the DST offset for the next firmware version. :-D