- This topic has 7 replies, 3 voices, and was last updated 1 year, 3 months ago by
.
-
Posts
-
I am suddenly unable to login into VMs and am getting the following error:
ubuntu@205.172.170.76: Permission denied (publickey).
I have tried on a couple of VMs and reran the configure scripts. I can provide the verbose messaging from SSH but it is a bit wordy.
Hello Bruce,
Inside this VM (205.172.170.76), an ssh public key identified as “fabric@localhost” is present under user account ubuntu.
VM is accessible with SSH from public internet. With the right ssh key and ssh client configurations as described on https://learn.fabric-testbed.net/knowledge-base/logging-into-fabric-vms/ you should be able to login to the VM.On the other hand, as you mention you are suddenly unable to login to the VMs, it could be a related to a change with the SSH key inside the VM. Can you confirm the ssh key that I mentioned above is the one that’s supposed to be present in the VM?
Hi Mert – I’m not sure I follow you. I have the bastion and slice keys but I do not think I have access to or control of the VM key you mentioned.
This is a very recent problem as I have been playing with the VMs for a couple of weeks although I am not ruling out an error between the keyboard and the chair.
Not sure if it’s related but I am getting other errors too. When running
#L3 fabnet auto
from ipaddress import ip_address, IPv4Address, IPv6Address, IPv4Network, IPv6Network
import ipaddressfrom fabrictestbed_extensions.fablib.fablib import FablibManager as fablib_manager
fablib = fablib_manager()I get the following error:
SliceManagerException: b'{\n “errors”: [\n {\n “details”: “error: Core API error occurred status_code: 404 message: b\'{\\\\n \\”errors\\”: [\\\\n {\\\\n \\”details\\”: \\”No match for Project with uuid = \\\\\’b55cc265-97af-4597-8c2f-c38b0618d3e\\\\\’\\”,\\\\n \\”message\\”: \\”Not Found\\”\\\\n }\\\\n ],\\\\n \\”size\\”: 1,\\\\n \\”status\\”: 404,\\\\n \\”type\\”: \\”error\\”\\\\n}\’, refresh_token: NB2HI4DTHIXS6Y3JNRXWO33OFZXXEZZPN5QXK5DIGIXTINJXGAYGEMLCG42WGZTFMU4DEODGMY2GCYRXGAZTEOBSGQ4GINB7OR4XAZJ5OJSWM4TFONUFI33LMVXCM5DTHUYTMOJSGAZTONZZG42DCNRGOZSXE43JN5XD25RSFYYCM3DJMZSXI2LNMU6TQNRUGAYDAMBQ”,\n “message”: “Internal Server Error”\n }\n ],\n “size”: 1,\n “status”: 500,\n “type”: “error”\n}’
@Bruce – It looks like Fablib was unable to refresh your token. Could you please Restart your JH container and try again?
You can stop your container via File -> Hub Control Panel -> Stop My Server; logout and login again.Thanks,
KomalRegarding SSH problem, if the
Configure EnvironmentNotebook was ran again assuming the same file name was used for the sliver keys, the sliver private/public keys got overwritten. So the SSH keys in~/work/fabric_config/are now different than what is in the VM and thus resulting in SSH failures.You can verify by
ls -ltr ~/work/fabric_configThanks,
Komal
- You must be logged in to reply to this topic.