Pb with rsync server and upgrade to FW18.3

[chrislev7]

Hi Mister,
Some difficulties after upgrade my whitebox to FW1.3.
I use differents backups from qnap NAS using HBS 3 interfaced with the rsync plugout (QNAP-> plugout).
Allways same result, after the completed execution of the backup from QNAP NAS, the QNAP hang on at 100% and impossible to finish the job.
Setup : Whitebox LACIE with last FW and samba 4.10 extension, disk 4T0. 2 servers plugout and same pb.
Could you help me please ? :dontknow
Best regards
Chris

[Jocko]

Hi

We need more detail on what backup actions you made.

So confirm these points :
- you enable rsync server on cloudbox
- on QNAP you backup files toward cloudbox by
* mounting a cloudbox share on QNAP (NFS or samba mount point ?)
* using rsync server

note : on version 18-3, there is no change on rsync server if you used version 18.2 patched and rsync does not use samba 4

What information do you have in rsync server log (of course if you use it )

[chrislev7]

Thanks you for your quick answer :
Here is my respond :

So confirm these points :
- you enable rsync server on cloudbox -> yes I confirm this point
- on QNAP you backup files toward cloudbox by
* mounting a cloudbox share on QNAP (NFS or samba mount point ?)
* using rsync server : I use only rsync server between the two NAS

What information do you have in rsync server log (of course if you use it )
Log of plugout rsync srv with SSH port 22 and rsyncd user for QNAP NAS access :

Code: Select all

[ssh] 2024/03/21 08:31:45 [3439] connect from NAS-SUMMOP86.local (192.168.2.22)
[ssh] 2024/03/21 08:31:45 [3439] module-list request from NAS-SUMMOP86.local (192.168.2.22)
[ssh] 2024/03/21 08:31:46 [3442] connect from NAS-SUMMOP86.local (192.168.2.22)
[ssh] 2024/03/21 08:31:46 [3445] connect from NAS-SUMMOP86.local (192.168.2.22)
[ssh] 2024/03/21 08:31:46 [3445] module-list request from NAS-SUMMOP86.local (192.168.2.22)
[ssh] 2024/03/21 08:31:46 [3448] connect from NAS-SUMMOP86.local (192.168.2.22)
[ssh] 2024/03/21 08:31:50 [3451] connect from NAS-SUMMOP86.local (192.168.2.22)
[ssh] 2024/03/21 08:31:50 [3451] rsync: [Receiver] setgid 0 failed: Operation not permitted (1)
[ssh]

Job hangs on 100%.
Thanks in advance

[Jocko]

So you access the rsync server through a SSH tunnel.
There is a change on this feature previously you have to use two accounts one to get access to the ssh access and the 2d access to connect to the rsync server. We implement it in patch02 for version 18.2 (jan. 2021)

Rsync server:
Affected device: all nas

New feature: you can reuse the Linux user account 'rsyncd' to connect to modules when you connect to it over a ssh access (more detail: viewtopic.php?f=27&t=3230)

- On version 18.2, did you make your backup with a patched version (or just patched 18.2 to be able to upgrade fvdw-sl)?
- check if you have set access (write permissions) for the user rsyncd on the destination module

[chrislev7]

Thanks you Jocko for your support,
I tried to implement the patch 5 in 18.2 with the FW 18.3 -> No way. box return : incompatible with 18.3.
I have to downgrade manualy the FW to 18.2 et patch just before.
Where can I found the 18.2 FW please ?
Thanks you !

[Jocko]

Hi

Your current version is 18.3, so that means when you used 18.2 you had patched the version 18.2 to be able to upgrade to version 18.3.
If I understand well, you had version 18.2 not patched up to you updated the firmware. In this case your issue is linked with the change included in patch02 but not detected by you as long as you did not update the firmware
Please can you post

Code: Select all

mkdir /tmp/sda1 /tmp/sda2
mount /dev/sda1 /tmp/sda1
mount /dev/sda2 /tmp/sda2
cat /tmp/sda1/etc/patch_log
cat /tmp/sda1/etc/patch_log
umount /tmp/sda1
umount /tmp/sda2

[Jocko]

No need to investigate more. I found where is the issue... I can reproduce it !

Code: Select all

root@Acrab:/ # /usr/sbin/rsync -8 --password-file="/rw_fs/etc/.passwd-acrab:rsyncd" -e "/usr/bin/dbclient -y -l "rsyncd" -p 8080 -i '/rw_fs/etc/dropbear/dropbear_rsa_host_rsynckey'"  rsyncd@ACRAB::x86-64/'

Host 'ACRAB' key accepted unconditionally.
(ecdsa-sha2-nistp521 fingerprint md5 c3:eb:ea:43:51:32:7b:be:88:77:f4:cd:01:66:14:2f)
Welcome on the rsync ACRAB server
@ERROR: setgid failed
rsync error: error starting client-server protocol (code 5) at main.c(1828) [Receiver=3.2.4pre2]

and in log I get

Code: Select all

[ssh] 2024/03/21 11:46:12 [6693] connect from Acrab.local (127.0.0.1)
[ssh] 2024/03/21 11:46:12 [6693] module-list request from Acrab.local (127.0.0.1)
[ssh] 2024/03/21 11:46:14 [6702] connect from Acrab.local (127.0.0.1)
[ssh] 2024/03/21 11:46:14 [6702] rsync: [Receiver] setgid 0 failed: Operation not permitted (1)

The issue is linked with rsync version :
from patch02 for version 18.2 and 18.3 rsync version is 3.2.4pre2 where as the former version was 3.0.9. If I reuse this version I do not get this error

Code: Select all

root@Acrab:/ # /usr/sbin/rsync -8 --password-file="/rw_fs/etc/.passwd-acrab:rsyncd" -e "/usr/bin/dbclient -y -l "rsyncd" -p 8080 -i '/rw_fs/etc/dropbear/dropbear_rsa_host_rsynckey'"  rsyncd@ACRAB::x86-64/

Host 'ACRAB' key accepted unconditionally.
(ecdsa-sha2-nistp521 fingerprint md5 c3:eb:ea:43:51:32:7b:be:88:77:f4:cd:01:66:14:2f)
Welcome on the rsync ACRAB server
drwxrwxrwx        4096 2024/03/09 18:12:07 .
drwxr-xr-x        4096 2021/01/16 14:13:07 bin_cab
drwxr-xr-x        4096 2024/03/09 10:41:14 etc
drwxrwxr-x        4096 2024/03/10 18:33:35 motionV2
drwxrwxr-x        4096 2024/03/09 10:57:26 usr


So it is a change made by rsync developer which occurs it. I go to post you rsync version 3.0.9 to fix your issue and later we need to understand why version 3.2.4 needs to send this gid command !

[Jocko]

So to restore former rsync version, do

Code: Select all

unlink /usr/sbin/rsync
plugout download 7255
tar -xf /tmp/rsync_3.0.9.tgz -C /usr/sbin


You should have now this output

Code: Select all

root@Acrab:/ # ls -al /usr/sbin/rsync*
lrwxrwxrwx  1 root root      9 2024-03-21 12:20 /usr/sbin/rsync -> rsync.182
-rwxr-xr-x  1 root root 361800 2013-06-09 22:06 /usr/sbin/rsync.182
-rwxr-xr-x  1 root root 441648 2022-01-17 21:23 /usr/sbin/rsync.183


---edit---

Sorry ! I made an error on the tar command. Now it is ok

[chrislev7]

Thanks Joko,
I'm not an expert like you.
How can I start the console.
I tried fvdw-sl console but is not a linux session...
Edit : sorry, I actived the console web in SSH menu but my login is invalid. bad user , I use root and the psw reseted no way...

[Jocko]

You may install Putty on a windows OS to open a shell window (SSH) or use directly the web console available from fvdw-sl web-interface :

From the setup menu of SSH access, you have to enable it and go to the menu "Web console", default login is root admin and pwd giveit2me

Please to note these menus are available only from your LAN

---edit---
Oups made a confusion

Edit : sorry, I actived the console web in SSH menu but my login is invalid. bad user , I use root and the psw reseted no way...

After upgrading the fvdw-sl root pwd is always reset, so should be giveit2me unless you set a new one after upgrading