Using TrueNAS as a rsync target, but not working

TrueNAS General
1

2nd day with TrueNAS SCALE (24.04.2.2) here, so please don’t assume I know anything :smile:

I am attempting to use my new NAS as a data archiving target. To get data from my other fileservers on it, I am wanting to use rsync. I have experience setting up rsyncd with modules on other Linux systems, but TrueNAS is a whole different ballgame. I have installed the “rsyncd” app on my TrueNAS, and configured a module to accept reads/writes to a particular dataset path. I think I have that right. Anyways, I can get a module listing from another machine on my LAN by doing this:

~$ rsync -rdt rsync://nj-archiving:30026
mlarchive       ML group archive target

But, going to use it, it fails in every way I’ve attempted. Latest method gives me this:

~$ rsync -e ssh -zvh stuff.tgz admin@nj-archiving::mlarchive
admin@nj-archiving's password:
rsync error: syntax or usage error (code 1) at clientserver.c(1296) [Receiver=3.2.7]
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]

I looked in syslog, and I’m seeing this:

Sep 26 16:40:34 nj-archiving sshd[775246]: Accepted password for admin from 138.15.169.11 port 51592 ssh2
Sep 26 16:40:34 nj-archiving systemd-logind[3672]: New session 40 of user admin.
Sep 26 16:40:34 nj-archiving systemd[1]: Started session-40.scope - Session 40 of User admin.
Sep 26 16:40:34 nj-archiving sshd[775246]: pam_unix(sshd:session): session opened for user admin(uid=950) by (uid=0)
Sep 26 16:40:34 nj-archiving rsyncd[775271]: rsync: [Receiver] unable to open config file "rsyncd.conf": No such file or directory (2)
Sep 26 16:40:34 nj-archiving rsyncd[775271]: rsync error: syntax or usage error (code 1) at clientserver.c(1296) [Receiver=3.2.7]

I would think the app config would write the requisite rsyncd.conf file??
What am I doing wrong here?

2

Not sure.

Can you review the documentation and indicate how you set it up.

Its not clear why you don’t want to use the inbuilt rsync?

3

My understanding of the inbuilt rsync function is that it can be only set up to “push” or “pull” to/from a defined remote system; in this case, I have many systems that I want to transfer data to the TrueNAS system on an ad-hoc basis. So setting up a rsyncd daemon on the TrueNAS system and defining modules is just what I want.

I did go through the rsyncd app instructions and got it installed and configured, but having problems now using it (I do this with many other Linux systems I administer, so I’m familiar with rsyncd setup in the traditional way.) Thought to look in the syslog for error messages, and I saw it couldn’t find the rsyncd.conf file. That would definitely be a problem :slight_smile:

On a side note, interesting that iXsystems chose Kubernetes (k3s) to implement their “App Store” on TrueNAS. I use k3s for Kubernetes at work, and it’s great; just seems like a bit of overkill to implement a solution for installing apps on a single server… I understand they are going to use Docker in the next version, that makes more sense to me for a single-node software install solution.