- This topic has 4 replies, 2 voices, and was last updated 6 months, 1 week ago by .
Viewing 5 posts - 1 through 5 (of 5 total)
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.
Home › Forums › FABRIC General Questions and Discussion › Lost Access to Node
Hello, I can no longer ssh into one of my nodes.
slice:
ID | 7b2cf6ec-1720-44d7-9ccc-7d36f8e621f3 |
Name | cresco_slice |
Fablib Version | 1.6.2 |
node:
ID | Name | Cores | RAM | Disk | Image | Image Type | Host | Site | Username | Management IP | State | Error | SSH Command | Public SSH Key File | Private SSH Key File |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2177e3d6-53a0-4cc9-b952-4efc359836a8 | node1 | 4 | 8 | 100 | default_ubuntu_22 | qcow2 | salt-w3.fabric-testbed.net | SALT | ubuntu | 2001:400:a100:3010:f816:3eff:febb:5537 |
I am using Jupyterhub.
Error Message:
fabric@spring:cresco-65%$ ssh -i /home/fabric/work/fabric_config/sliver -F /home/fabric/work/fabric_config/ssh_config ubuntu@2001:400:a100:3010:f816:3eff:febb:5537
Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) 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
Connection closed by UNKNOWN port 65535
The FABRIC SALT suffered a power outage last night. We are in the process of recovering the VMs. I will update you once they are up again.
Thanks.
Try now. My colleague Mert Cevik has restored all VMs. But FYI any data-plane interface config that was not persistent may need to be re-created
Checked and it’s back. Thank you!