Maxim Usatov
2024-Nov-15 16:08 UTC
Errors with program diagnostics (code 13) after rsync upgrade
Dear All, Having weird rsync issues after upgrading FreeBSD from 13.2 to 14.1 and rsync along with it. I cannot find any solution. Setup: doing rsync backup from the root ZFS to an SSD mounted to /media/da0p1. The rsync is initiated as root using /etc/crontab. The log: 2024/11/15 08:30:01 [61842] building file list <... a few hundred files listed here - no error messages! ..> 2024/11/15 08:30:41 [61842] sent 15069073 bytes? received 77859 bytes? total size 104786993196 2024/11/15 08:30:41 [61842] rsync error: errors with program diagnostics (code 13) at log.c(245) [sender=3.3.0] I assume code 13 is related to permissions, but given rsync is started as root, why would this happen? The same rsync commands worked on all previous versions of FreeBSD. It also fails with the same error to a remote SSH host. If I run my rsync backup scripts manually as root then everything works fine, so the issue appears only when the script is initiated by cron. /etc/crontab entry: 30??? *??? *??? *??? *?????? root /home/blackhaz/scripts/rsync-to-external-drive rsync command in the script: if mount | grep $TARGET_DISK; then ?????? nice rsync --log-file=$RSYNC_LOG_FILE \ ?????? --archive --hard-links --delete --delete-excluded --sparse --xattrs --numeric-ids --acls --progress \ ?????? / /media/$TARGET_DISK/freebsd-backup Would appreciate any pointers. Tried without--hard-links and getting the same error. Regards, Maxim Usatov
crateman.universalistic356 at aceecat.org
2024-Nov-15 17:42 UTC
Errors with program diagnostics (code 13) after rsync upgrade
On Fri, Nov 15, 2024 at 04:08:27PM GMT, Maxim Usatov via rsync wrote:> I assume code 13 is related to permissions, but given rsync is > started as root, why would this happen? The same rsync commands > worked on all previous versions of FreeBSD. It also fails with the > same error to a remote SSH host. If I run my rsync backup scripts > manually as root then everything works fine, so the issue appears > only when the script is initiated by cron.> if mount | grep $TARGET_DISK; then > nice rsync --log-file=$RSYNC_LOG_FILE \ > --archive --hard-links --delete --delete-excluded --sparse --xattrs > --numeric-ids --acls --progress \ > / /media/$TARGET_DISK/freebsd-backupThis is just a very wild and uneducated guess, but I would try it without the nice. Also: without the xattrs and acls. So 3 things to try :-P -- Ian
Possibly Parallel Threads
- Errors with program diagnostics (code 13) after rsync upgrade
- Errors with program diagnostics (code 13) after rsync upgrade
- Errors with program diagnostics (code 13) after rsync upgrade
- insufficient access rights / denied / DNS
- could not initialise lsa pipe - unable to join domain