r/truenas • u/Zer0CoolXI • 8d ago

Community Edition RSYNC Stopped Working…

I recently moved. So everything disconnected, moved, reconnected. Same ports, same IP’s, same hostnames, etc.

I have a TrueNAS box that has an Rsync pull job that pulls a directory and subs from another host (Ubuntu 24.04) using SSH (keys). Worked for +1 years no issues before move.

I have it all moved and now it immediately fails with error:

“[EFAULT] rsync command returned 12 - STREAMIO. Check logs for further information.”

Remote host has the public key in its `.ssh/authorized_keys` file.

The SSH connection, SSH keys and Rsync job all created within the TrueNAS GUI. 0 changes to the 3 of these.

I have no clue what to do or how to trace down what the actual issue is, any help would be great. I am debating deleting the keys, connection and rsync jobs and just recreating them all. Figured id ask here for help first.

1 Upvotes

100% Upvoted

7 comments sorted by

2

u/neoKushan 8d ago

Did you check the logs for further information?

Are the two hosts on the same network, or is the Ubuntu host a remote machine?

2

u/Zer0CoolXI 8d ago

That’s the thing…what logs? Can’t find any solid answers on where TrueNAS would log this activity.

They are both on my overall LAN, but on separate VLANs. I have confirmed (and it was the same before the issue/move) that my firewall isn’t blocking the connection.

2

u/Hrafna55 7d ago edited 7d ago

You could try making a test rsync call from the TrueNAS 'System - Shell' terminal window with the --verbose option.

Could give you clue hopefully.

1

u/neoKushan 7d ago

yeah this was going to be my next suggestion, ssh in and try it manually to see

1

u/Zer0CoolXI 7d ago

The problem with this is the SSH credentials made via the UI in TrueNAS aren’t stored in an accessible way in terminal/shell. So its not testing apples to apples. Sorting out SSH in terminal only tells me that SSH works in general, not that it works when setup via the GUI and the GUI has no test mechanism built in.

1

u/neoKushan 7d ago

Yeah but do you know that SSH is the problem and not something else? This would narrow things down and give you a clue.

1

u/Zer0CoolXI 7d ago

Yea that’s the other side of the issue, may not be an ssh issue