1. Node active but not able to ssh

Node active but not able to ssh

Home Forums FABRIC General Questions and Discussion Node active but not able to ssh

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #4040
    Meng Wang
    Participant

      In my project I created a slice that contains 2 nodes. I was originally able to ssh into both nodes. But today when I tried again, I couldn’t ssh into one of the 2 nodes even though they both appear active.

      Error message:

      (base) fabric@jupyter-mwang231-40asu-2eedu:~/work$ ssh -i /home/fabric/work/fabric_config/slice_key -F /home/fabric/work/fabric_config/ssh_config ubuntu@132.249.252.174
      Warning: Permanently added ‘bastion-1.fabric-testbed.net,128.163.180.149’ (ECDSA) to the list of known hosts.
      channel 0: open failed: connect failed: No route to host
      stdio forwarding failed
      kex_exchange_identification: Connection closed by remote host

      Slice Name: mwang231_0000056064mengw231-fabric-ndn-copy2

      Node ID: 7d3607d3-c382-4587-8621-2f4522cc5c55

      Node Management IP: 132.249.252.174

      #4041
      Mert Cevik
      Moderator

        This problem was caused by a transient problem on the hypervisor, and VM was forcefully stopped. VM is restarted and accessible. We will work on the root cause of the problem internally, but you should be able to continue your work on the VM.

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