On Wed, 23 Oct 2019, wes wrote: > I suspect that it's been treating the local vault as remote all along, and > it used to work because the SSH key pair was enabled for root on the old > system. The easiest solution would be to enable the key pair on the new > system. You would need to put the public key from the pair you generated > recently into /root/.ssh/authorized_keys
Wes, Put root's public key in salmo:/root/.ssh/authorized_keys? I don't think that's how the old host was set up, but that was ~20 years ago so I don't remember. Did this. No different result. > The "correct" solution would be to instruct dirvish that the vault and the > backup target are on the same system, to keep it from trying to create a > remote connection. I don't know enough about how dirvish works to tell you > how to do that. And I don't see in the HOWTO how to do it, either. Regards, Rich _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
