On Wed, Oct 23, 2019 at 3:05 PM Rich Shepard <rshep...@appl-ecosys.com> wrote:
> $ ping salmo.appl-ecosys.com > PING salmo.appl-ecosys.com (192.168.55.1) 56(84) bytes of data. > 64 bytes from salmo.appl-ecosys.com (192.168.55.1): icmp_seq=1 ttl=64 > time=0.023 ms > 64 bytes from salmo.appl-ecosys.com (192.168.55.1): icmp_seq=2 ttl=64 > time=0.035 ms > etc. > > Ok, that's odd... it thinks salmo is the router. I am guessing the local system's IP address is not 192.168.55.1? Check your /etc/hosts file to see if anything odd shows up in there. On Wed, Oct 23, 2019 at 3:10 PM Rich Shepard <rshep...@appl-ecosys.com> wrote: > 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. > Yes. And its private key goes in /root/.ssh/id_rsa You should be able to become root, and then ssh localhost and get a new login prompt without any other interaction. If that doesn't work, dirvish isn't going to work. -wes
_______________________________________________ Dirvish mailing list Dirvish@dirvish.org http://www.dirvish.org/mailman/listinfo/dirvish
