BackupCreations/SuperFlexible Shared Forum

Hi,

I try to use Syncovery on my Linux server. Using cronjobs it works very well but I have no idea how to use the scheduler.

In your description you wrote it could be started using "./SyncoveryCL &" which is correct if you start it in the current user session. But I want to let the server start syncovery on bott using /etc/init.d/ script.

I tried tmux, screen and directly using "./SyncoverCL &" to be executed in a script. Everytime it tries to start but freezes at the line "23:37:22 Initiating interprocess communication as server".

Is there any documentation how to use the service? e.g. how to configure it using a startup script?

Yours
Stefan

Hello,
it depends very much on the Linux distro. I think you have to start it later in the boot process if it doesn't work where you put it.

But cronjobs are surely better.

I haven't tried launching the scheduler at boot time myself yet.

Hello,

it is not depending on boot sequence. I created a new /etc/init.d script and executed it at runtime but it was not possible to ger the scheduler running.

I am switching now to cronjobs but if you want to check if it is a software fault or an os fault (it is a quick and dirty test - so please do not blame me about the paths ):

Code: Select all

#! /bin/sh
### BEGIN INIT INFO
# Provides:          syncovery start stop restart
# Required-Start:
# Required-Stop:
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: seafile cloud service
# Description:       Starts/stops syncovery scheduler
### END INIT INFO
# Author: Stefan Ruepp

# Aktionen
case "$1" in
    start)
        /root/syncovery/SyncoveryCL >> /var/log/syncovery.log 2>> /var/log/syncovery.log &
        ;;
    debug)
        /root/syncovery/SyncoveryCL /TGCP >> /var/log/syncovery.log 2>> /var/log/syncovery.log &
        ;;
    stop)
        /root/syncovery/SyncoveryCL /STOPTIMER
        ;;
    status)
        /root/syncovery/SyncoveryCL /STATUS
        ;;
    restart)
        /etc/init.d/syncovery stop
        sleep 5
        /etc/init.d/syncovery start
        ;;
esac

exit 0

You can put it anywhere and try it by executing it with param "start" or "stop". e.g. ./syncovery start

If I can be helpful, try the following command to start Syncovery scheduler :

Code: Select all

start-stop-daemon --start --quiet --background --pidfile /var/run/syncovery.pid --make-pidfile --stdout /var/log/syncovery.log --stderr /var/log/syncovery.err --exec SyncoveryCL

And the following command to stop :

Code: Select all

start-stop-daemon --stop --pidfile /var/run/syncovery.pid

You should see SyncoveryCL running

Code: Select all

ps ax | grep SyncoveryCL

and SyncoveryCL /STATUS must return something like that

22:45:54 Communication established
22:45:54 Waiting a bit more
22:45:54 Scheduler is running. Using config file /root/.Syncovery/Syncovery.cfg

Thank you very much for your informatione. I switched now to cronjobs. As soon as I have time I am going to test your solution.

Thanks for all this info. I am working on creating a Debian installation package with such scripts now.

I believe the latest Linux version fixes possible hangs like the one you originally mentioned.