Rsync does not display 'homes' directory on destination server

[FSC830]

That is, what I did with the first job. Push the data to remote rsync server.
In folder list I was able to select the homes folder at remote site, but I set a different folder as destination.
Is /home at remote NAS an exported folder?

Regards

[m@x1m3]

What I did is slightly different. Like your first picture, but the right side is not the source but destination.
Is you other rsync server just another NAS ? Cause it shows /homes and not /home as a Linux server should do.
There is no remote NAS because NAS is the source. Remote is Almalinux backup server, fresh install no modif.

[FSC830]

What I did is slightly different. Like your first picture, but the right side is not the source but destination.
Is you other rsync server just another NAS ? Cause it shows /homes and not /home as a Linux server should do.
There is no remote NAS because NAS is the source. Remote is Almalinux backup server, fresh install no modif.

That was the piece of information I was missing, the origin home folder of the Linux. I supposed with /home you mean the replicated /home from the NAS.
Unfortuantely I am a bit struggling with AlmaLinux (I did setup v9.0 in a VM).
I can perform rysnc by CLI from NAS to AlmaLinux host and a raspberryPi and vice versa.
But creating a storage space fails with the AlmaLinux, with Pi it succeeds.
No idea, what blocks at the AlmaLinux.
Also checking rsync daemon at AlmaLinux fails from other devices!?

Some examples from CLI:

Code: Select all

++++ CLI at NAS

[master@TS473-01 test03]$ rsync -rdt rsync://192.168.10.27:873
sh: /var/run/rsync-normal.pid: Permission denied
root            PI64 ftp export area
[master@TS473-01 test03]$ rsync -rdt rsync://192.168.10.70:873
sh: /var/run/rsync-normal.pid: Permission denied
rsync: failed to connect to 192.168.10.70: No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(182) [Receiver=3.0.7]


++++ CLI at AlmaLinux host

[root@localhost /]# rsync -rdt rsync://192.168.10.70:873
ftp             ALMA ftp export area
[root@localhost /]# rsync -rdt rsync://192.168.10.27:873
root            PI64 ftp export area

++++ CLI at raspberryPi

root@pi64:/# rsync -rdt rsync://192.168.10.70:873
rsync: [Receiver] failed to connect to 192.168.10.70 (192.168.10.70): No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(137) [Receiver=3.2.3]
root@pi64:/# rsync -rdt rsync://192.168.10.27:873
root            PI64 ftp export area

192.168.10.70 is the AlmaLinux, 10.27 the raspberryPi.
At NAS no rsync host is enabled.

Anyhow, after creating the storage space for the Pi, I can see the /home folder (and others):

rsync_pi.png

So I am wondering, why /home from AlmaLinux should not be seen...?
What did you wrote in rsync.conf for the path information?

Regards

Edit: got it Allowed port 873 in firewall, but did forget port 22

So I was able to create a storage space now with the AlmaLinux too:

rsync_alma.png

And here the directories in /home are not visible!
But at raspberryPi they are visible.
The storage spaces for both devices AlmaLinux and Pi are setup with identical settings, so I am currently rather convinced, this is NOT an issue related to QNAP, but to AlmaLinux which does not allow to see this directories.

Edit 2:
I can transfer files from and to all devices by CLI, but when creating a job in HBS3 it fails every time with an error "module is read-only" !??? Seems, that HBS3 has an issue too.

[m@x1m3]

Ok,
I see you did quite a work here.
=> thx
Astonishing every other machine can list /home on my Alma.
I'll check SELinux and ssh versions tomorrown, and keep you update.

[FSC830]

I noticed another strange issue: as I wrote above I could not create a storage space until allowing port 22 in AlmaLinux hosts firewall.
But I was able to connect from my pc using putty at port 22.
So I wonder, why HBS3 was unable to connect.
It was definitely not a missing entry in known_hosts file, at this time neither the AlmaLinux nor the raspberry Pi was in known_hosts.

Regards

[m@x1m3]

yep, that's the point, from the start: ssh has a strange behaviour from qnap, while all the other machines are connecting and reading ok, out the box.

[FSC830]

Did play a bit more...

Did the same storage space with an ubuntu 20.4 VM and a Linux Mint VM. With both OS the /home folder is browsable. Only at the Almalinux it is not...
Checked also with an older NAS (QTS 4.3.4) and backup station, same behaviour as on TS-473A and QTS 5.0.1, a job does end with an error, but rsync by CLI is possible:

Code: Select all

++++ CLI at NAS

[master@TS473-01 ~]$ sudo rsync ts473.txt johndoe@192.168.10.70:/home/johndoe
johndoe@192.168.10.70's password:

++++ CLI at AlmaLinux

[root@localhost johndoe]# ls -al
total 48
drwx------. 15 johndoe johndoe 4096 Oct  5 09:52 .
drwxr-xr-x.  3 root    root      21 Oct  4 13:13 ..
-rw-------.  1 johndoe johndoe  833 Oct  4 17:50 .bash_history
-rw-r--r--.  1 johndoe johndoe   18 Mar 30  2022 .bash_logout
-rw-r--r--.  1 johndoe johndoe  141 Mar 30  2022 .bash_profile
-rw-r--r--.  1 johndoe johndoe  492 Mar 30  2022 .bashrc
drwxr-xr-x.  9 johndoe johndoe 4096 Oct  4 13:14 .cache
drwxr-xr-x.  9 johndoe johndoe  190 Oct  4 17:50 .config
drwxr-xr-x.  2 johndoe johndoe    6 Oct  4 13:14 Desktop
drwxr-xr-x.  2 johndoe johndoe    6 Oct  4 13:14 Documents
drwxr-xr-x.  2 johndoe johndoe    6 Oct  4 13:14 Downloads
drwx------.  4 johndoe johndoe   32 Oct  4 13:14 .local
-rw-rw-r--.  1 johndoe johndoe   26 Oct  5 09:34 mint.txt
drwxr-xr-x.  4 johndoe johndoe   39 Oct  4 12:58 .mozilla
drwxr-xr-x.  2 johndoe johndoe    6 Oct  4 13:14 Music
drwxr-xr-x.  2 johndoe johndoe    6 Oct  4 13:14 Pictures
drwxr-xr-x.  2 johndoe johndoe    6 Oct  4 13:14 Public
drwx------.  2 johndoe johndoe   25 Oct  4 15:33 .ssh
drwxr-xr-x.  2 johndoe johndoe    6 Oct  4 13:14 Templates
-rw-r--r--.  1 johndoe johndoe   52 Oct  4 15:37 test01.txt
-rw-r--r--.  1 johndoe johndoe   22 Oct  4 16:18 test.txt
-rw-r--r--.  1 johndoe johndoe   25 Oct  5 09:52 ts473.txt
-rw-rw-r--.  1 johndoe johndoe   46 Oct  5 09:33 ubuntu.txt
drwxr-xr-x.  2 johndoe johndoe    6 Oct  4 13:14 Videos
-rw-------.  1 johndoe johndoe  783 Oct  4 15:31 .viminfo

Clearly seen, the file was copied.

Regards

[FSC830]

New findings here... .

After setting up the storage with the option "Use encryption port" the /home directory is not shown any longer at each rsync destination!
But job runs now without errors to any destination (i.e. /tmp).

When removing the "Use encryption port" option /home is visible again, but job fails.
No idea if the reason for failing is a wrong destination (/home) or the missing encryption port. .
Checked now multiple times: without the encryption the job fails with:

Code: Select all

Warning	2022-10-05	13:00:36	admin	127.0.0.1	Hybrid Backup Sync	Job Status	[Hybrid Backup Sync] Failed to complete Sync job: "raspberryPi". Encountered error "ERROR: module is read only" Attempting to retry. Error code: 1.

So my guess only QNAP can tell us, why encryption is mandatory!?

Regards

[chrismaffey]

Some issue here using HBS 3 to sync from a remote Ubuntu Linux box, cannot see the /home directory on the linux box, permissions are the same as other directories which are shown

[proletentoaster]

Same problem here with Debian 11 on the remote ssh server.
On HBS3 i can browse the whole directory structure on my remote server, but can't see the home directory here.
It's just a standard installation.
If it's by design, don't understand why.

[loonytoon]

Same issue (I think...) with Hetzner Storage Box as remote Rsync server (storage space).

Initial setup of the storage space on my TS-453D in HBS3 goes well. Connection test and speed test are both successful:

StorageSpace_1.png

StorageSpace_2.png

While creating the job in HBS3 and when trying to select the destination folder, it stays like this forever (well, I left it there for a couple of hours):

CreateSyncJob.png

What bothers me is that the connection test is successful, yet the listing of the remote space is not successful. There's no firewall for the outgoing connections that could potentially limit the connection. Manual rsync from the QNAP works fine:

manualRsync.png

Choosing FTP instead of rsync works fine in a sync job for the same destination. But it itches me to set it up with rsync

[HennyN]

Same issue (I think...) with Hetzner Storage Box as remote Rsync server (storage space).

Initial setup of the storage space on my TS-453D in HBS3 goes well. Connection test and speed test are both successful:

StorageSpace_1.png
StorageSpace_2.png

While creating the job in HBS3 and when trying to select the destination folder, it stays like this forever (well, I left it there for a couple of hours):

CreateSyncJob.png

What bothers me is that the connection test is successful, yet the listing of the remote space is not successful. There's no firewall for the outgoing connections that could potentially limit the connection. Manual rsync from the QNAP works fine:

manualRsync.png

Choosing FTP instead of rsync works fine in a sync job for the same destination. But it itches me to set it up with rsync

The same problem here. Do you have the solution for using rsync.
I asked Hetzner for help to solve this....
But ik looks like it is a QNAP problem.
Should we ask QNAP to find a solution for this RSYNC problem in HBS 3

[FSC830]

You can try this (create a ticket).
QNAP does not come here.
But dont expect a quick solution.

Regards

[HennyN]

You can try this (create a ticket).
QNAP does not come here.
But dont expect a quick solution.

Regards

I made a support ticket at QNAP referring at this topic....:

++++++++++++++++++++++++++++++++++++++++++++
HBS 3 Rsync does not display 'homes' directory on destination server.

The problem is described in this forum topic: viewtopic.php?t=167873&start=15

I used HBS 3 to backup my photos on my QNAP NAS to MiHos cloud environment. However, Mihos has discontinued the cloud environment.

I have switched to a cloud environment at Hetzner.

If I want to set this up in HBS 3 I need to be able to browse to a folder on my cloud environment at Hetzner where I want to store my backup. It doesn't seem possible (it was possible at MiHos). In the forum topic I read that several users have such problems with HBS 3, while making backups from the CLI with rsync does work. The forum topic therefore concludes that it does not work from HBS 3.

I would like to know why this is not working and what is the solution? It worked with MiHos though.

I also see that from HBS 3 it is possible to choose the could environment of HiDrive. Perhaps such a solution can also be made in consultation with Hetzner. I'm happy to test if you tell me what to do.

I do need a solution to this problem.

Regards, Henny Nekkers

++++++++++++++++++++++++++++++++++++++++++++
Waiting for an answer...

Regards, Henny Nekkers

[bigornoo]

Hello,
I've exactly the same problem : Ubuntu 20.04.6 LTS & QTS 5.1.1.2491. I can't see /home with ssh encryption in rsync job.