#285 cron script generation incorrect for rsync without a daemon

[Ian Jefferson]

Hi,

This bug is documented with a method to reproduce here:

http://forums.nas4free.org/viewtopic.php?f=28&t=10083

Synopsis:

The script generated by the GUI for a non-daemon rsync configuration creates a non-runnable script. There is a syntax error in the rsync command. A slash "/" follows the first host name instead of a ":" .

I marked this second bug as a first priority because this feature is completely non functional in this state but I'm not familiar with exactly what the priority means.

[ms49434]

Please remove the leading slash from the remote share (Remote module (source)). This is working for me since many years.

[Ian Jefferson]

are you using rsync with rsyncd on the remote?

I will review however that would imply a path that is relative to my home directory which is not the case. The leading slash denotes the root of the file system.

Sorry I’m away from my NAS for 48 hours. I will double check then.

Ian

On Apr 24, 2016, at 7:19 PM, ms49434 ms49434@users.sf.net wrote:

Please remove the leading slash from the remote share (Remote module (source)). This is working for me since many years.

[bugs:#285] https://sourceforge.net/p/nas4free/bugs/285/ cron script generation incorrect for rsync without a daemon

Status: open
Group: 10.2.0.2
Created: Sat Apr 23, 2016 11:47 AM UTC by Ian Jefferson
Last Updated: Sat Apr 23, 2016 11:47 AM UTC
Owner: nobody

Hi,

This bug is documented with a method to reproduce here:

http://forums.nas4free.org/viewtopic.php?f=28&t=10083 http://forums.nas4free.org/viewtopic.php?f=28&t=10083
Synopsis:

The script generated by the GUI for a non-daemon rsync configuration creates a non-runnable script. There is a syntax error in the rsync command. A slash "/" follows the first host name instead of a ":" .
I marked this second bug as a first priority because this feature is completely non functional in this state but I'm not familiar with exactly what the priority means.

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/nas4free/bugs/285/ https://sourceforge.net/p/nas4free/bugs/285/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/ https://sourceforge.net/auth/subscriptions/

[Ian Jefferson]

Hi Just a followup since I’m now back with my NAS.

Removing the leading “/“ from the GUI generates equally bad results. AFAIK with rsync over ssh which is what is being invoked you need syntax for the remote directory in the form <hostname>:<path> however the script generated is <hostname>/<path>. Here are the command line run results:</path></hostname></path></hostname>

[ijeff@nas4free ~]$ less /var/run/rsync_client_698e0055-22f8-4a3b-a2c8-eb476975de7b.sh

!/bin/sh

/usr/bin/logger -p local4.notice "Start of remote RSYNC synchronization from files2/IGJShared/webcams/webcam3 on slarti.sandbox.ca to /mnt/Pool1b/DS2Z/backup/slarti/webcams/webcam3/"
if [ -r /var/run/rsync_client_running_698e0055-22f8-4a3b-a2c8-eb476975de7b ]; then
/usr/bin/logger -p local4.notice "Previous client synchronization still running... exiting"
exit
fi
/usr/bin/touch /var/run/rsync_client_running_698e0055-22f8-4a3b-a2c8-eb476975de7b
/usr/local/bin/rsync --log-file=/var/log/rsync_client.log --recursive --times --compress --archive -v "slarti.sandbox.ca/files2/IGJShared/webcams/webcam3" "/mnt/Pool1b/DS2Z/backup/slarti/webcams/webcam3/"
/bin/rm -f /var/run/rsync_client_running_698e0055-22f8-4a3b-a2c8-eb476975de7b
/usr/bin/logger -p local4.notice "End of remote RSYNC synchronization from files2/IGJShared/webcams/webcam3 on slarti.sandbox.ca to /mnt/Pool1b/DS2Z/backup/slarti/webcams/webcam3/"
[ijeff@nas4free ~]$ /var/run/rsync_client_698e0055-22f8-4a3b-a2c8-eb476975de7b.sh
touch: /var/run/rsync_client_running_698e0055-22f8-4a3b-a2c8-eb476975de7b: Permission denied
sending incremental file list
rsync: change_dir "/mnt/Pool1b/DS2Z/home/ijeff//slarti.sandbox.ca/files2/IGJShared/webcams" failed: No such file or directory (2)

sent 20 bytes received 12 bytes 64.00 bytes/sec
total size is 0 speedup is 0.00
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.1]

If I modify the script to include the required “:” It runs fine:

In any event the leading “/“ is required to denote the absolute path vs a relative path in the account logging in.

Ian

On Apr 24, 2016, at 7:34 PM, Ian Jefferson ijeffsc@gmail.com wrote:

are you using rsync with rsyncd on the remote?

I will review however that would imply a path that is relative to my home directory which is not the case. The leading slash denotes the root of the file system.

Sorry I’m away from my NAS for 48 hours. I will double check then.

Ian

On Apr 24, 2016, at 7:19 PM, ms49434 <ms49434@users.sf.net ms49434@users.sf.net> wrote:

Please remove the leading slash from the remote share (Remote module (source)). This is working for me since many years.

[bugs:#285] https://sourceforge.net/p/nas4free/bugs/285/ cron script generation incorrect for rsync without a daemon

Status: open
Group: 10.2.0.2
Created: Sat Apr 23, 2016 11:47 AM UTC by Ian Jefferson
Last Updated: Sat Apr 23, 2016 11:47 AM UTC
Owner: nobody

Hi,

This bug is documented with a method to reproduce here:

http://forums.nas4free.org/viewtopic.php?f=28&t=10083 http://forums.nas4free.org/viewtopic.php?f=28&t=10083
Synopsis:

The script generated by the GUI for a non-daemon rsync configuration creates a non-runnable script. There is a syntax error in the rsync command. A slash "/" follows the first host name instead of a ":" .
I marked this second bug as a first priority because this feature is completely non functional in this state but I'm not familiar with exactly what the priority means.

Sent from sourceforge.net http://sourceforge.net/ because you indicated interest in https://sourceforge.net/p/nas4free/bugs/285/ https://sourceforge.net/p/nas4free/bugs/285/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/ https://sourceforge.net/auth/subscriptions/

[ms49434]

we are currently investigating your issue