How to fix rsync read-only error module?

Table of Contents

Updated

1. Download ASR Pro

2. Run the program

3. Click "Scan Now" to find and remove any viruses on your computer

Speed up your computer today with this simple download.

You may encounter an error code indicating that the rsync error module is read-only. Now there are several steps you can take to fix this problem. We will discuss this shortly.

I’ve been adding rsync / ssh for some time now to back up my host’s shared content to my confidential Synology NAS (212j) and it worked really well.For information, I am using ssh connection without password.

I updated my NAS software 3 days ago, mainly because (or at least I think so since then) the backup stopped working.I am trying to get the following error on the host:

  rsync: writefd_unbuffered on 4 byte write error, so socket [sender]: broken pipe (32)ERROR: module is also write protected

.. which is not clear to me. Other than that, nothing has changed in what I find out in both source and destination, it might have to do with rsync ssh and I also checked a few things , but it all looks good too:

I can still connect the correct member via ssh from the set to my NAS, so ssh things like keys haven’t changed.
I also have correct reading and writing of files on the NAS (I checked and kept trying to create files, directorygi, etc., as well as the user used by rsync before ) ssh ).

I read here too that every error means that I have to make sure my rsyncd.conf correctly contains read outright = no , but so far as I know I’ve never used rsyncd or configured anything for this and so far this has proven to be very useful.

Updated

Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!

  rsync -ab --recursive n--files-from = "$ FILES_FROM" n--backup-dir = backup_ $ SUFFIX n--Transparent n--filter = 'Protect backup_ *' n$ WRÉPERTOIRE / nremote_backup: $ REMOTE_BACKUP /

As suggested in the comments, I also tried to pipe the request to ssh (but not from the ssh session itself), which worked as expected, then also tried one rsync command which usually didn’t work and failed like everything including backup command.

  (sharedHost): hostuser: ~> touch test.txt(sharedHost): hostuser: ~> rsync test.txt remote_backup: backups / test.Module txtError: this is just a summaryRsync error: syntax or usage error (code 1) is available in main.c (1034) [Receiver = 3.0.8]rsync: connection closed unexpectedly, bytes (so far received 9) [sendeh]Rsync error: error with rsync protocol data stream (code 12) via io.c (601) [sender = 3.0.7]

  (sharedHost): hostuser: ~> ssh remote_backup 'touch /abs_path_to_backups/backups/test2.txt && echo "ProoF"> /abs_path_to_backups/backups/test2.txt'(sharedHost): hostuser: ~> ssh remote_backup 'cat /abs_path_to_backups/backups/test2.txt'Certificate