Syncovery Support Forum

I'm in the process of transferring the backups for my QNAP NAS from a Windows 10 PC instance of Syncovery to a QNAP-native instance. I'm having a few issues but first and foremost logs are not generating after a profile run (whether successful, unsuccessful or incomplete).

I tried changing the default log location from /../.qpkg/SyncoveryCL/Logs to / the admin account home directory and 1 other location but that fails also. The default Syncovery log folder as well as the 2 test folders I tried all have full r/w perms.

Hello,
a good location for the log folder is usually:
/share/CACHEDEV1_DATA/.qpkg/SyncoveryCL/Logs

After changing the folder, please run a job "With Preview" and check if a log file is available when the job is finished or canceled.

Syncovery generally won't write a log file if there is almost no disk space remaining.

If it still doesn't work, you can try a reboot or use some SSH commands (such as via PuTTY).

For example:
cd /share/CACHEDEV1_DATA/.qpkg/SyncoveryCL
./SyncoveryCL /RUNX="Profile Name"

That should write something to the Console about logging.

Thanks for the suggestions Tobias. Unfortunately, none of these worked, the Logs file is still empty and I see "No Data To Display" in the Web GUI under Logs. There are several TB of free space on the volume hosting .qpkg so that should be no issue.

I have tried executing the profile in several ways-
1. from the GUI running unattended
2. from the GUI running attended w/ preview
3. from the command line as you suggested above

If you have any other ideas please let me know.

Hello,
what are you logging settings on the Logs tab sheet of the Program Settings dialog?

They should look something like this: And can you install the latest version v9.12 for QNAP from our web site?

When you run a job with the command line, Syncovery will also mention the log folder that is uses. The only known reason for no log file is if the settings are not like the screenshot, or if the folder is nearly full.

I will add additional diagnostics capability regarding logging in a future version. But this is really the first report of this kind that I get.

Thanks Tobias. My settings did not quite match your screenshot, I have modified them to be exactly the same. I also have upgraded to 9.12 (previously I was on 9.11). I still do not get logs unfortunately. I do however see an error about disk space when running from command line:

-----------------------------------------------------------------------------------------------
17:06:40 Log folder: /share/CACHEDEV3_DATA/.qpkg/SyncoveryCL/Logs
...
...
17:06:40 Not logging because the volume with the log folder is nearly full.
-----------------------------------------------------------------------------------------------


That volume has many terrabytes of free space though:

Filesystem Size Used Available Use% Mounted on
none 400.0M 377.4M 22.6M 94% /
devtmpfs 1004.5M 64.0k 1004.5M 0% /dev
tmpfs 64.0M 7.1M 56.9M 11% /tmp
tmpfs 1015.3M 1.1M 1014.1M 0% /dev/shm
tmpfs 16.0M 0 16.0M 0% /share
tmpfs 16.0M 0 16.0M 0% /mnt/snapshot/export
/dev/md9 499.5M 158.2M 331.0M 32% /mnt/HDA_ROOT
cgroup_root 1015.3M 0 1015.3M 0% /sys/fs/cgroup
/dev/mapper/cachedev3 20.3T 9.7T 10.6T 48% /share/CACHEDEV3_DATA
/dev/md13 417.0M 274.0M 143.0M 66% /mnt/ext
tmpfs 48.0M 768.0k 47.3M 2% /share/CACHEDEV3_DATA/.samba/lock/msg.lock
tmpfs 16.0M 0 16.0M 0% /mnt/ext/opt/samba/private/msg.sock
/dev/mapper/vg2-lv1312 2.2G 2.6M 2.2G 0% /mnt/pool2
/dev/mapper/cachedev3 20.3T 9.7T 10.6T 48% /lib/modules/4.2.8/container-station

Hi,
apparently Syncovery can't determine the free space for this volume correctly. Maybe it's too big.

Do you have another, smaller one you could try?

The path should start with /share

It's working now, thanks very much Tobias!

Ultimately I placed them in /mnt/HDA_ROOT/SyncLogs, I could not get it working in the multiple other locations I tried under /share.

Thanks for the info!

The next update will actually ask the user in this situation and allow to turn off the free space detection for logging.

Thanks again for getting it sorted out, much appreciated and for the feature add to toggle off the free space detection. I'll give that a try once implemented and re-configure the logging back to the /share vol.