Crash on QNAP with v10.7.1

[doogle]

Hi,

I just upgraded from 9.something to 10.7.1 on my QNAP NAS and found that Syncovery wasn't able to start. I was seeing the following output when trying to run manually:

Code: Select all

$ ./SyncoveryCL start /INI=/share/CACHEDEV1_DATA/.qpkg/SyncoveryCL/Syncovery.cfg
An unhandled exception occurred at $0000000000536C61:
ERangeError: Range check error
  $0000000000536C61
  $0000000000536D72
  $0000000000536EC0
  $0000000000417ABC

When running with strace, I saw that this was happening after an 'open("/etc/timezone", ...)' which was succeeding, but a subsequent 'read()' was failing with EISDIR. It turned out that for some reason /etc/timezone was an empty dir instead of a textfile with the timezone name. Removing the dir and creating the correct textfile allowed Syncovery to start up ok.

I'm posting about this as I'm not sure if there will be any knock-on effects from making this change to my /etc/timezone, even if it isn't correct that it's an empty dir. So maybe this is something that (a future reversion of) Syncovery could explicitly handle so it will be possible to restore the empty dir..? I did recently upgrade QTS to v5.1.1.2491 so maybe that has changed something, but my guess would be that /etc/timezone has been a directory on QNAP for a while.

[doogle]

Bump. Any comment on this?
I have found that after a restart, Syncovery won't running as /etc/timezone is recreated as an empty directory, causing the crash on Syncovery startup.

It would be good to hear if this is something that will be addressed in a future version of Syncovery or not.

[tobias]

Hi,
sorry for the delay, yes I will work on it and fix it.

The timezone reading logic was recently upgraded because of new timezone formats being used on Synology NAS devices.

[tobias]

Hello,
the new version 10.9.2 should fix this now.

[doogle]

Hi tobias,

I noticed that Syncovery hadn't been running on my NAS and after seeing that it was the same issue, I went looking for this post to find the workaround... and saw that you posted about the new version a while ago! I must have completely missed a notification email.

Anyway, thanks for the fix! I've installed the new version and it's working again without issues.