Trial run for Rsync job works, but not the actual job

  • I want to sync 2 folders containing movies with Rsync, but I encounter the following message when running the job:


    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; export SHELL=/bin/sh; sudo --shell --non-interactive -- /var/lib/openmediavault/cron.d/rsync-42d2c383-8a39-418d-84f0-df25d70e6d1f 2>&1' with exit code '1':


    Looking at the logs, here is what I can see around the time of the error:
    Feb 21 13:17:01 openmediavault CRON[6921]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
    Feb 21 13:17:01 openmediavault CRON[6920]: (root) CMD (/var/lib/openmediavault/cron.d/rsync-42d2c383-8a39-418d-84f0-df25d70e6d1f >/dev/null 2>&1)
    Feb 21 13:17:01 openmediavault rsync-42d2c383-8a39-418d-84f0-df25d70e6d1f: Please wait, syncing </srv/2be572a5-1ead-4ea8-a94f-ec017a71163b/Media/Movies/> to </srv/20c912db-7dc6-418f-b91d-fd51a7a3f5b9/Movies> ...\n
    Feb 21 13:18:01 openmediavault CRON[7004]: (root) CMD (/var/lib/openmediavault/cron.d/rsync-42d2c383-8a39-418d-84f0-df25d70e6d1f >/dev/null 2>&1)
    Feb 21 13:18:47 openmediavault omv-engined[7344]: Failed to write to socket: Broken pipe
    Feb 21 13:19:01 openmediavault CRON[7352]: (root) CMD (/var/lib/openmediavault/cron.d/rsync-42d2c383-8a39-418d-84f0-df25d70e6d1f >/dev/null 2>&1)
    Feb 21 13:20:01 openmediavault CRON[7421]: (root) CMD (/var/lib/openmediavault/cron.d/rsync-42d2c383-8a39-418d-84f0-df25d70e6d1f >/dev/null 2>&1)


    Is anyone spotting anything odd already maybe?


    - As mentioned in the title of this thread I was able to run a trial. It all looked fine. Once I unselect trial within the job settings, then it doesn't work and I get the message above.
    - I am using OMV 4.0.19
    - the Rsync job is a local type, the source drives are directly attached to the OMV machine MoBo, the destination drives are attached to a Mac via Thunderbolt and USB. This job setting used to work. I deleted this job and recreated multiple times yesterday and today to try to make it work again
    - I created another job a couple of days ago and all went fine. The job syncs different folders (documentaries this time) which are located on the same source and destination drives. I ran the job again now and...it works


    I am a bit puzzled... Thanks for any direction or help you may give!

    Asrock J3455 - 8GB ram - 1x4TB WD RED + 1x2TB WD Green
    OMV 4.1.26-1 - Kernel 4.19

  • After rebooting my OMV machine, the Rsync job started to work... I had left it enabled (big green dot) after acknowledging the error message described in my previous post.
    A few seconds after reboot, I can see traffic coming in on my mac and, indeed, files that didn't exist start to be copied.


    A few remarks:
    - I would prefer to disable the Rsync job and run it manually. If I leave it enabled, the job will run at regular interval, am I correct..?
    - It would be nice to add some sort of live transfer log in the OMV interface under Rsync in Services, like a separate tab. I had to reboot and can't see what it is being transferred now. Is there a command line that would allow to view that maybe?
    - Rebooting OMV from its interface (top right arrow) brought my machine to a halt. I had to reboot manually by physically pressing the power button of my NAS. I am not sure this is related, the issue appeared at the same time though.


    If you have any thought about what could be the problem, please share them!

    Asrock J3455 - 8GB ram - 1x4TB WD RED + 1x2TB WD Green
    OMV 4.1.26-1 - Kernel 4.19

  • - A cronjob is meant to run at the scheduled times. Sometimes I need a manual run of the job as well. That's why I usually don't use the plugin but a shell script. That can be put into cron and run manually. And you can do lots more (Check disk space on backup device, wake-up and send to sleep the source etc.)
    - Don't know how to achieve that in OMV. As workaround it is possible to send the commands output to your email address or write it into a logfile. Commands would be -v --stats --progress
    -

  • Thank you Stramm for your suggestions, I will try them.


    Just before reading your message, I launched an Rsync job manually through the plugin and it seemed to work fine. This job had failed yesterday. After reading your message I stopped it and went into editing to select the output to email address option. After applying the changes, I tried to run the job and got an error message... I unselected the output to email address option after, but the result was still the same: that failed to execute command.


    I am puzzled by how random it seems to be. I can't see patterns. These settings used to work. Anyone experiencing these error messages with Rsync in OMV 4.0.19?
    It's always possible that this is not an Rsync issue.

    Asrock J3455 - 8GB ram - 1x4TB WD RED + 1x2TB WD Green
    OMV 4.1.26-1 - Kernel 4.19

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!