1. ssh timeout trying to log into nodes

ssh timeout trying to log into nodes

Home Forums FABRIC General Questions and Discussion ssh timeout trying to log into nodes

Tagged: 

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #6551
    susmit shannigrahi
    Participant

      We are trying to create an apache web server- we are following the example playbook. We are able to create the slice and nodes, but not able to ssh into the VMs.

      1. I have create a slice and two nodes attached to it. Everything seems to work fine. Attached screenshot.

      2. Notebook – see attached.

      3. Keys: Verfied all the keys exist and have correct permissions.

      fabric@spring:fabric_config-50%$ ls -al
      total 56
      drwxrwsr-x 3 fabric users 4096 Sep 28 15:30 .
      drwxrwsr-x 18 root users 4096 Feb 11 17:04 ..
      -rw——- 1 fabric users 492 Sep 28 15:29 2023-09-Bastion-Key
      -rw-rw-r– 1 fabric users 180 Sep 28 15:29 2023-09-Bastion-Key.pub
      -rw——- 1 fabric users 492 Sep 28 15:29 2023-09-Silver-Key
      -rw-r–r– 1 fabric users 179 Sep 28 15:29 2023-09-Silver-Key.pub
      -rw-rw—- 1 fabric users 492 Dec 29 2022 fabric-bastion-key
      -rw-rw—- 1 fabric users 121 Dec 28 2022 fabric_config.json
      -rw-rw—- 1 fabric users 972 Feb 11 19:57 fabric_rc
      -rw——- 1 fabric users 492 Dec 28 2022 slice_key
      -rw-r–r– 1 fabric users 173 Dec 28 2022 slice_key.pub
      -rw-rw—- 1 fabric users 396 Sep 28 15:30 ssh_config
      fabric@spring:fabric_config-50%$

      4. The generated ssh commands by the notebook are:

      Tried both from terminal and Jupiterhub

       

      [susmit@brun331-m04 FABRIC]$ ssh -i 2023-09-Silver-Key -F ssh_config ubuntu@205.172.170.100
      Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
      channel 0: open failed: connect failed: Connection timed out
      stdio forwarding failed
      kex_exchange_identification: Connection closed by remote host
      Connection closed by UNKNOWN port 65535

      #6554
      Hussam Nasir
      Moderator

        From looking at the console boot messages of your VM, we observed that you may have changed the default route for the VM which overwrote the gateway IP needed to ssh into your VM. I see that the default gateway is now your FABNETv4 subnet. This would cause you to lose ssh connectivity to your. You have to delete this VM and start over and make sure not to change the default gateway of the VM.

         

      Viewing 2 posts - 1 through 2 (of 2 total)
      • You must be logged in to reply to this topic.