RSYNC with QNAP over SSH - any special tricks to get it going?

TrueNAS General
1

running 25.10.4 - Goldeye - set up a dedicated user, created home dataset with unix permissions, generated and downloaded keys and managed to get a RSYNC task defined based on SSH. Set up the QNAP side and seeded the public key on there. Getting “rsync command returned 12 - STREAMIO. Check logs for further information” but being a newbee (My new nas is operational only since last week) I have no idea where to find that log.

Now am I right assuming that this should work as per the documentation?? Also, can someone point me to how and where to find the logs??

Much appriciated!!

2

OK - after much more digging I found out that QNAP runs a very old version of RSYNC software on their platform - version 3.07 which dates back to 2009. I can only think that this version isn’t good enough to meet the requirements of TN Scale to do modern and hardened secure RSYNC with. Can anybody comment on that??

I also found that there is a community version available for TN that allows unencrypted RSYNC - an app named RSYNCD. The app is in the app store but I cannot get it going as it complains about no available containers. I’m also not sure that this app would still work within Goldeye. Can anyone provide any insight into that plse??

3

I use rsync over ssh to backup to a QNAP every night, and I don’t recall running into any version problems.

I’m running QTSS 5.2.9.3499 on a TS853-A, and TrueNAS Scale 25.10.4

FWIW, I’m running HBS3 (Hybrid Backup Server) to provide an rsync server on the QNAP and I’m using password auth, not public key.

4

That sounds encouraging - would you mind sharing some of the details of how you configured this?? I was trying to get the stock standard Data Protection RSYNC task with SSH - using the “connection from the keychain” You are using passwords stored in the home directory??

thnx

5

Do you see a disclosure button in that alert, and/or might it be scrollable?

rsync error 12 on the client side is kind of an all-around “the server told us to go away” error.

There might be more actionable insight in logs on the listening (QNAP) side. It could be anything from permissions to directory path (and escaping of special characters in the path) and beyond.

1 Like
6

unfortunately both sides are very frugal with providing clues and what is going on. I know things can work as I can do CLI rsync through the shell - be it with providing a password on the prompt. I might have to resort to a couple of CRON jobs to achieve the desired outcome - but that is far from optimal…

7

Apologies, I’ve been away on holiday for the last week. I’ll have a look at my config and provide more detail when I’m back at work in the week :+1:

8

@cdvreede

Sorry, ignore me. I’ve just gone back through my notes and realised I could never get rsync over ssh working. My two hosts (QNAP and TrueNAS) are on the same local network, so I’m just doing a straight rsync with no ssh tunnel. Sorry again, but I don’t have a solution for you :slightly_frowning_face: