Rsync does not start anymore

[Lieven]

Rsync worked fine when I was testing it, however, then I created the final shares and accounts. And from then I couldn't enable the rsync server anymore. I tried recreating the testaccount, but that didn't work anymore also.

When I tick the box enable and click save, I get the error "Fail: can't update Rsync configuration".

When I click "(re-)start server I get the error "fail: start commend failed15"

Only thing I have to mention: one time shortly before: the disk got full (I put too much on a share). But now I have almost 300Gb free. So this is not a problem anymore.

I searched for a solution, but only strange thing I noticed is rsyncd.conf is empty (0 bytes). Is this normal? I saw in the .finc files the file is filled with these scripts but I couldn't figure out the whole picture.

How can this issue be resolved?
Thank you in advance.

[Jocko]

Hi

I searched for a solution, but only strange thing I noticed is rsyncd.conf is empty (0 bytes). Is this normal? I saw in the .finc files the file is filled with these scripts but I couldn't figure out the whole picture.

It would mean some permissions have been changed or some system linux accounts deleted (Did you make a such action ?)

Please to post

Code: Select all

ls -ld /etc
ls -l /etc/rsyncd.conf
ls -l /tmp/rsyncd-ssh

[Lieven]

It would mean some permissions have been changed or some system linux accounts deleted (Did you make a such action ?)

I think I did deleted some user accounts to clean up in user account --> user management.
Now I have the following accounts:
dummy
netbackup

I didn't delete other accounts in Linux

I also renamed admin-nas to admin
and changed password of root

Code: Select all

root@fvdwsl-base:/ # ls -ld /etc
drwxrwxr-x  18 root sys 5120 2020-01-18 07:32 /etc


Code: Select all

root@fvdwsl-base:/ # ls -l /etc/rsyncd.conf
-rw-r--r--  1 nobody nobody 0 2020-01-14 21:50 /etc/rsyncd.conf


Code: Select all

root@fvdwsl-base:/ # ls -l /tmp/rsyncd-ssh
total 8
-rw-r--r--  1 nobody nobody 1512 2020-01-14 21:50 rsyncd.conf
-rw-------  1 rsyncd rsyncd   19 2020-01-14 21:50 rsyncd.secrets


[Jocko]

Hi

file permissions do not seem to be the issue.

So a new output

Code: Select all

grep 'RSYNCD_GLOBAL_OPTIONS' /etc/inc/global_defs.inc

according with the php script, on error on this constant may explains why you have empty conf files.

and also

Code: Select all

 ls -al /var/run/

[Lieven]

Code: Select all

root@fvdwsl-base:/ # grep 'RSYNCD_GLOBAL_OPTIONS' /etc/inc/global_defs.inc
define('RSYNCD_GLOBAL_OPTIONS',"\n# GLOBAL OPTIONS or COMMON MODULES OPTIONS\n\n\t#Location of the rsyncd motd file\n\tmotd file = ".RSYNCD_MOTD_FILE."\n\n\t#Location of the rsync log file\n\tlog file = ".RSYNCD_LOG_FILE."\n\n\t#Location of the rsyncd pid file\n\tpid file = ".RSYNCD_PID_FILE."\n\n\t#Location of the rsync lock database\n\tlock file = ".RSYNCD_DB_FILE."\n\n\t#Maximum number of simultaneous connections\n\tmax connections = 5\n\n\t#Minimum amount of time the server holds a lock on a rsync resource\n\ttimeout = 300\n\n\t#list\n\tlist = yes\n\n\t#uid\n\tuid = root\n\n\t#gid\n\tgid = root\n\n\t#Chroot the paths\n\tuse chroot = no\n\n\t#Location of the rsyncd secrets file\n\tsecrets file = ".RSYNCD_SECRET_FILE."\n");
root@fvdwsl-base:/ #


Code: Select all

root@fvdwsl-base:/ #  ls -al /var/run/
total 44
drwxrwxrwx  3 nobody nobody 4096 2020-01-14 21:50 .
drwxr-xr-x  8 root   root   4096 2018-01-01 12:00 ..
-rw-r--r--  1 root   root      5 2018-01-01 12:00 dropbear.pid
-rw-------  1 nobody root    138 2018-01-01 12:00 .editpasswd
-rw-------  1 nobody root     67 2018-01-01 12:00 .htpasswd
-rw-r--r--  1 root   root      5 2018-01-01 12:00 httpd.pid
drwxr-xr-x  2 nobody nobody 4096 2020-01-18 07:28 lock
-rw-r--r--  1 root   root      5 2018-01-01 12:00 noflushd.pid
-rw-r--r--  1 root   root      5 2018-01-01 12:01 ntpd.pid
-r--r--r--  1 root   root      0 2018-01-01 12:00 rpcbind.lock
srw-rw-rw-  1 root   root      0 2018-01-01 12:00 rpcbind.sock
-rw-------  1 root   root     19 2020-01-14 21:50 rsyncd.secrets
-rw-r--r--  1 root   root    768 2020-01-18 09:48 utmp
root@fvdwsl-base:/ #


[Jocko]

Nope nothing wrong on this side...

Did you reboot the nas since last tuesday? if yes you should make a new attempt.

Other way, activate the debug mode and try to start rsync server. So
- load the rsync server menu
- start the debug mode

Code: Select all

debugon

- try to start rsync
- stop the debug mode

Code: Select all

debugoff

Then post the content

Code: Select all

cat /var/log/messages

[Lieven]

strange!:

Code: Select all

root@fvdwsl-base:/ # debugon
sed: write error


[Jocko]

So i think you have a corrupted OS on the current partition.

Then the better is to go back to the previous version and make a new upgrade.
if it is the first upgrade:

Code: Select all

cd /lacie-boot
unlink sda1boot

if you made at least two upgrade

Code: Select all

cd /lacie-boot
ls
mv sda1boot sda2boot   (if you see the file sda1boot)
mv sda2boot sda1boot (if you see the file sda2boot)

then reboot the nas
If you use some custom boot scripts I advice to disable them before upgrading again to version 18.2

(note: your changes will be restored except for admin login which will be restored by admin-nas and root password by the default one)

[Lieven]

Downgrade and upgrade worked, now I have a working rsync-server again, thanks a lot!