Perhaps, run rsync_bpc manually at the command line. Sometimes this
yields more error verbiage.
On 5/14/25 10:18 PM, Christian Völker via BackupPC-users wrote:
Hi,
there is no sense in deleting the known_hosts on your target systems....
Just to wrap it up: you upgraded your backuppc targets to a new
version, right?
So there might be a new host key on them (although Richard mentioned
it beeing unlikely).
Go to your BackupPC host, switch user context to backuppc user (ie by
"su - backuppc"). Then ssh to your target servers witch "ssh
root@target" and confirm it goes smoothly. If there is a key mismatch
messege you found it. Remove the single key and restart ssh- then you
should be good to go.
Or simply delete the known_hosts from the backuppc user home/.ssh and
re-login to all targets.
In case your installation is running as a different user than
backuppc, use this guy then.
Let us know if it works!
Greetings
/Christian
Am 15.05.25 um 06:31 schrieb John Cusick:
Kenneth and Richard,
Thanks for your replies. Unfortunately, when I discovered the problem
yesterday, this is the first thing I did. There was a problem in that
regard and I had to delete the old entries in the known_hosts files
on the target systems and re-login as the server's backuppc user to
renew the entries in the known_hosts files. I did that successfully
using the backuppc user and ssh'ing into the target systems with no
password required.
When I checked this morning, the same errors were occurring and
that's when I decided to check with the forum users.
The server is setup to use rsync_bpc and on the server backuppc
webpage the error given is:
"rsync error: unexplained error (code 255) at io.c(226)
[Receiver=3.1.3.0]"
And the Backuppc log shows this:
This is the rsync child about to exec /usr/bin/rsync_bpc
Host key verification failed.
rsync_bpc: connection unexpectedly closed (0 bytes received so far) [Receiver]
Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0
sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 198848 inode
rsync error: unexplained error (code 255) at io.c(226) [Receiver=3.1.3.0]
So the error occurs after "/usr/bin/rsync_bpc" is executed and
repeated for each backup'ed directory
Up until I updated from Fedora 41 to Fedora 42, both incremental and
full backups were completed with no problems. And when checking the
syslogs on the clients, pam reports successful logins of the backuppc
user (I checked multiple times on each client).
I'm not too sure how rsync_bpc is supposed to function, it's been a
couple of years since I've had to look at any of this... something I
consider a plus and why I use Backuppc. It has always "just worked".
(Also, I also see this initially in the Backuppc logs -
Executing /usr/share/BackupPC/bin/BackupPC_backupDuplicate -m -h mac17-w
Old package separator used in string at
/usr/share/BackupPC/bin/BackupPC_backupDuplicate line 89.
(Did you mean "$Host\'s" instead?)
- I've always seen this in the logs since Day 1, is this critical?)
But thanks to you both once again for the quick replies.
Regards,
John C.
On Wed, May 14, 2025 at 4:41 PM John Cusick <jcus...@gmail.com> wrote:
Hello all,
After a full update from Fedora 41 to Fedora 42 all client
backups are now failing. The error is mentioned in the subject
line, I've made no changes to the rsyncd.conf or rsyncd.secrets
files
Host key verification failed.
I'm not seeing the problem. I've made no changes to the user
(backuppc) and the user can successfully login to the clients
using ssh as before the update.
The previous lines are:
Running: /usr/bin/rsync_bpc --bpc-top-dir /var/lib/BackupPC/
--bpc-host-name xxxx --bpc-share-name xxxx ...
incr backup started for directory xxxx
Xfer PIDs are now 72054
This is the rsync child about to exec /usr/bin/rsync_bpc
Host key verification failed.
rsync_bpc: connection unexpectedly closed (0 bytes received so far)
[Receiver]
The login itself is successful accordig to the rsyslog messages
file and although I saw no (what appeared to me) selinux errors
I turned off selinux on the client and server and it still fails.
I'm not seeing any errors on the syslog messages file on clients
or server and the server is reporting "rsync error: unexplained
error (code 255) at io.c(226) [Receiver=3.1.3.0]".
I'm stuck and not really sure how to troubleshoot the rsync code
255 error and I'm hoping someone else running Fedora 42 has seen,
and solved, the problem.
Regards,
John C.
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project:https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project:https://backuppc.github.io/backuppc/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
