Forum Replies Created
-
Posts
-
Hi,
I looked at logs on one of the failed nodes and found that the last command before the node failed was
“sudo /usr/sbin/ldconfig /home/ubuntu/openssl/build/lib64/”
This command results in the breaking of the sshd daemon running on the machine, thus causing you to loose your ssh connection. A reboot would fix the ssh because the library you built is not loaded.
Thank you for the feedback. We truly appreciate your input. We will work on updating these images and let you know.
Yes i understand that. But as i mentioned in my post https://learn.fabric-testbed.net/forums/topic/kali-machine-failing-on-post_boot_config/#post-8105 . You will have to do those modifications to get it to work.
Hello Nirmala,
I believe you missed providing some details regarding the above setup. Guessing from the output you pasted above I think you are trying to install frr using instructions from https://deb.frrouting.org/ . The error you posted above is because that package does not have a release for Kali Linux. All the repos point to Debian or Ubuntu. When you run teh setup commands mentioned on the FRR webpage , it creates a apt repo file in /etc/apt/sources.list.d/frr.list. The name of the OS in that file is shown as “kali-rolling” .
I am guessing Kali Linux is based off debian 12 (bookworm) . So if you replace the word kali-rolling with bookworm, you apt commands to install the packages should work.
Hello Nirmala,
We have corrected the image at the WASH site and are updating all other sites with the corrected image. This process should be done by EOD today. You can start using WASH in the meantime
Hello Nirmala,
I believe we have a faulty disk image for Kali. Please bear with us while we get this resolved. It may be a few days before we get back to you.
what is the Ip of the machine you are trying to ssh into. From the first post i see 1.2.3.4 which is not a valid IP
Aha. The cuplrit is the group ownsership on your home folder. This must have been changed somehow.
drwxrwx— 12 ubuntu root 4096 Dec 2 18:17 /home/ubuntu
run the command
sudo chown -R ubuntu:ubuntu /home/ubuntu
That should fix the issue.
Thats not the right machine . We want the output from 00954b21-57cf-40e2-86c2-0d7b7269fecb-classifier node
Can you please post the output of
ls -lad /home/ubuntuls -la /home/ubuntu/.ssh
The can see from the ssh log that the ownership of home directory is the issue
Dec 02 18:07:16 00954b21-57cf-40e2-86c2-0d7b7269fecb-classifier sshd[60744]: Connection closed by authenticating user ubuntu 2001:400:a100:1030::51 port 52118 [preauth]
Dec 02 18:07:16 00954b21-57cf-40e2-86c2-0d7b7269fecb-classifier sshd[60744]: Authentication refused: bad ownership or modes for directory /home/ubuntu
Dec 02 18:07:09 00954b21-57cf-40e2-86c2-0d7b7269fecb-classifier sshd[60742]: Connection closed by authenticating user ubuntu 2001:400:a100:1030::51 port 52104 [preauth]
Dec 02 18:07:09 00954b21-57cf-40e2-86c2-0d7b7269fecb-classifier sshd[60742]: Authentication refused: bad ownership or modes for directory /home/ubuntu
Dec 02 18:06:35 00954b21-57cf-40e2-86c2-0d7b7269fecb-classifier sshd[60740]: Connection closed by authenticating user ubuntu 2001:400:a100:1030::51 port 50056 [preauth]
Dec 02 18:06:35 00954b21-57cf-40e2-86c2-0d7b7269fecb-classifier sshd[60740]: Authentication refused: bad ownership or modes for directory /home/ubuntuCan you please grab the logs using
sudo journalctl -r -u ssh >/tmp/ssh.log
and then email help@fabric-testbed.net with the ssh.log file attached .If pullout the file is not possible then just run
sudo journalctl -r -u ssh
and copy the few recent lines that will help us debug the issue.
