-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1333) [sender=3.2.3] #202
Comments
It's look like you have ACL on your logs how cannot be write on the HDD mount point. |
I have the same issue on ubuntu 22.04 lts. dist-upgraded since ubuntu 16 error seems it could not do something with log2ram.log it was deleted or not created. never the less it is up and running. I have created log2ram.log manually in /var/hdd.log and /var/log with sudo touch |
Same error on a fresh RaspberryPi OS Bullseye. sudo touching those files made the error go away though (thank you @vincentstans). |
It seems to be a bug in rsync 3.2.3, updating to 3.2.7 solved the issue for me. |
Would this also work on a promox server? I have a problem with some of my backups at the moment. |
Don't know, could be permission errors as well but version 3.2.3 is 2 years older than 3.2.7 so I would suggest giving it a go. |
Thanks, Strange thing is it worked till 2 weeks ago, now i have problems with 2 of my containers... |
This worked also to update rsync on my proxmox setup. Thanks! |
Great, glad it worked :) |
same error on rsync 3.2.7-1 for me |
yea same issue with raspbian-bullseye. tried using rsync 3.2.7 and get the same errors on /var/log/journal files |
This is on a plain up to date debian 11, as installed per your instructions. The funny thing is: There were no 'previous errors'.
Not that I can find anyway. A search in google tells me this has to do with dir permissions being wrong somewhere.
The text was updated successfully, but these errors were encountered: