Clearsync service fails to restart when files changed in /etc/clearsync.d
If a file is changed in /etc/clearsync.d, there is a watcher, /etc/clearsync.d/filewatch-base-clearsync.conf which fires /usr/clearos/apps/base/deploy/syncaction with a parameter clearsync_change_event. This should restart clearsyncd and the following is logged in /var/log/system:
May 11 13:52:41 microserver clearsync: base - event triggered - clearsync_change_event
May 11 13:52:41 microserver clearsync: base - clearsync configuration change detected
May 11 13:52:41 microserver clearsync: base - restarting clearsync
In reality, the PID of clearsyncd does not change between before and after the log messages so it looks like the restart of clearsyncd is failing.
This is important because some apps, when they install, drop files into /etc/clearsync.d/ and the restart of clearsyncd is expected to make them effective. clearsyncd is not restarted as part of the installation script.
Edited by Nick