Closed brianshumate closed 9 years ago
For some reason jsch is not using keys and is using root user password — from /var/log/auth.log
on n1:
May 1 14:32:11 debian-800-jessie sshd[1646]: pam_unix(sshd:session): session opened for user root by (uid=0)
May 1 14:34:32 debian-800-jessie sshd[1656]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.122.10 user=root
May 1 14:34:34 debian-800-jessie sshd[1656]: Failed password for root from 192.168.122.10 port 45919 ssh2
May 1 14:34:34 debian-800-jessie sshd[1656]: error: Received disconnect from 192.168.122.10: 3: com.jcraft.jsch.JSchException: Auth fail [preauth]
Setting:
PermitRootLogin yes
in /etc/ssh/sshd_config
on the test nodes solves this issue but might not be the best idea security-wise.
/etc/sshd_config doesn;t exist in each of the created n1..5 lxc containers. Did you create them manually or did I miss something ? If you can provide the steps in order, for any prep before this sshd config fix, it would help. I am still not able to run the test (e.g., the aerospike one) successfully. Same old jsch auth fail error.
The file is actually /etc/ssh/sshd_config
.
Change:
PermitRootLogin without-password
to
PermitRootLogin yes
Ah, ok. I missed that. How did you edit this file since "vi" is not installed, so something like sed ? Also, what does this setting do; I mean do we have to create a password for the root user in each of the nodes n1......5, as well ?
My jepsen_init.yml playbook sets the root user password.
If you're using this project with Vagrant, you can do the following to change it by hand:
vagrant ssh n0
sudo su -
passwd root
On the main console node stuck here currently -> stat: cannot stat '/var/cache/apt/pkgcache.bin': No such file or directory
Despite adding host keys to
known_hosts
for the console node, settingroot
user password to root, installing SSH public key toroot
user'sauthorized_keys
on all test nodes, adding the SSHconfig
, and ensuring the node naming is correct per aphyr's lxc.md, there still remains a persistent error: