Home › Forums › FABRIC General Questions and Discussion › Slice key issue
- This topic has 3 replies, 2 voices, and was last updated 12 months ago by
Komal Thareja.
-
AuthorPosts
-
March 5, 2025 at 10:44 am #8330
Hi,
it looks like there’s an issue with my slice key since I cannot login to the VM I created.
This is on the FABRIC node at MGHPCC. My UUID is40d793ef-4450-4059-8923-f048fb7a123a Here’s the error message I get:
fabric@winter:fabric_config-80%$ ssh -i /home/fabric/work/fabric_config/slice_key -F /home/fabric/work/fabric_config/ssh_config rocky@2001:48e8:6401:3:f816:3eff:fed9:fa68
Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
mzink_0011417656@bastion.fabric-testbed.net: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
kex_exchange_identification: Connection closed by remote host
Connection closed by UNKNOWN port 65535Thanks,
Mike
March 5, 2025 at 10:49 am #8331Hi Mike,
This could possibly be because your Bastion Key has expired. Could you please try running theĀ notebook
jupyter-examples-rel1.8.1/configure_and_validate/configure_and_validate.ipynbagain?This should renew the keys. If error persists, could you please share if you see any errors in
/tmp/fablib/fablib.logThanks,
Komal
-
This reply was modified 12 months ago by
Komal Thareja.
March 5, 2025 at 11:46 am #8333Thanks, Komal.
I created a new bastion key but totally forgot to run the notebook.
I can run the notebook without any issue but I still cannot ssh into the VM.
Error message is pretty much still the same.
fabric@winter:KNIT10 Demo-80%$ ssh -i /home/fabric/work/fabric_config/slice_key -F /home/fabric/work/fabric_config/ssh_config rocky@2001:48e8:6401:3:f816:3eff:fe17:f0b9
Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
mzink_0011417656@bastion.fabric-testbed.net: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
kex_exchange_identification: Connection closed by remote host
Connection closed by UNKNOWN port 65535Mike
March 5, 2025 at 12:20 pm #8334Hi Mike,
Could you please check following files and ensure they point to the new key and have the right bastion username?
/home/fabric/work/fabric_config/fabric_rc/home/fabric/work/fabric_config/ssh_configAlso, just verified that the VM in question seems to have been deleted.
Thanks,
Komal
-
This reply was modified 12 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.