Forum Replies Created
-
AuthorPosts
-
Dear Community,
I am facing the same issue. I have followed the steps shown in https://github.com/fabric-testbed/jupyter-examples/blob/master/fabric_examples/complex_recipes/P4_bmv2/p4lang_tutorials.ipynb. I didn’t get any errors. Everything was fine, but I can’t ping from host1 to host2. Inside docker, I can see that switch is receiving the packet but not sending to the other switch as shown in the picture. What may be the issue? What are recommendations to debug it?
Kind regards,
Nagmat
The error “sudo: unable to resolve host a83f476a-af0e-4b07-8a63-7d1cb0f6c300-h1” is normal since there is no name resolution for this.
As for the Ubuntu repositories, There was an issue with some Ubuntu Repos yesterday worldwide. Try this again today. If it still does not work, please post the contents of the /etc/resolv.conf file from your machine.
The issue is still there.
The content of /etc/resolve.conf is :
“# This file is managed by man:systemd-resolved(8). Do not edit.
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
# Run “resolvectl status” to see details about the uplink DNS servers
# currently in use.
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
options edns0 trust-ad
search openstacklocal”
The error I am getting is :
“sudo: unable to resolve host a83f476a-af0e-4b07-8a63-7d1cb0f6c300-h1: Temporary failure in name resolution
W: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/dists/focal/InRelease Temporary failure resolving ‘nova.clouds.archive.ubuntu.com’
W: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease Temporary failure resolving ‘nova.clouds.archive.ubuntu.com’
W: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease Temporary failure resolving ‘nova.clouds.archive.ubuntu.com’
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease Temporary failure resolving ‘security.ubuntu.com’
W: Some index files failed to download. They have been ignored, or old ones used instead.
sudo: unable to resolve host a83f476a-af0e-4b07-8a63-7d1cb0f6c300-h1: Temporary failure in name resolution
E: Unable to locate package python3-scapy”
February 6, 2023 at 3:23 pm in reply to: TicketReviewPolicy: Closing reservation due to failure in slice# #3807Yeah, I deleted the slice and created it again. Now it works fine.
We looked into this and this is not an issue with being banned.
From your error, you have made it through the bastion host but are failing authorization at the VM. This is likely caused by using the wrong VM username or the wrong key. Keep in mind, the key you use in the portal and the key you use in the JupyterHub are likely different. You can make them the same but you would need to manually do that. Are you sure you are using the correct slice/sliver key?
The slice key and the sliver key are different. Shall I make them the same?
I am sure that I am using the correct sliver key since I logged in with it a couple of times.
I attached the configuration of my jupyter hub as an attachment.
” ssh -F ssh_config -i ~/.ssh/nagmat_sliver_key ubuntu@132.249.252.175 ”
Getting :
“Warning: Permanently added ‘bastion.fabric-testbed.net,128.163.180.149’ (ECDSA) to the list of known hosts.
Warning: Permanently added ‘132.249.252.175’ (ECDSA) to the list of known hosts.
Received disconnect from UNKNOWN port 65535:2: Too many authentication failures
Disconnected from UNKNOWN port 65535 ”I made sliver and slice key the same, but still getting the same error.
I think what you have will probably work once the ban is lifted. We did make a small change in order to load balance across the bastions hosts. There is now one bastion name “bastion.fabric-testbed.net”. You might try making ssh_config look something like this (Although I think it would work the way you have it):
Host bastion.fabric-testbed.net User pruth_0031379841 ForwardAgent yes Hostname %h IdentityFile /home/fabric/work/fabric_config/fabric_bastion_key IdentitiesOnly yes Host * !bastion.fabric-testbed.net ProxyJump pruth_0031379841@bastion.fabric-testbed.net:22
I have edited ssh_config file accordingly.
Should I make request for ban lift or will it be removed after some time?
If it removes automatically after some time, how long does the process take?
Kind regards,
Nagmat
Oh, actually this won’t work for you right now. There is still something wrong with your ssh setup but even if you correct it, you have triggered our security policy about failed ssh retries and your IP has been temporarily banned.
Are you able to try this from a different IP?
I uploaded public key of my laptop to fabrictestbed on SSH keys.
Yeah, I tried from another IP but getting :“Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
Warning: Permanently added ‘2607:f018:110:11:f816:3eff:fe56:fe96’ (ED25519) to the list of known hosts.
ubuntu@2607:f018:110:11:f816:3eff:fe56:fe96: Permission denied (publickey).”Ok, my next thought is that the ssh_config file might be wrong or not at the path you specified.
Can you confirm the ssh_config file is in the local dir and post the parts related to the fabric bastion host?
The ssh_config file :
“UserKnownHostsFile /dev/null
StrictHostKeyChecking no
ServerAliveInterval 120Host bastion-?.fabric-testbed.net
User nagmat_0051461802
ForwardAgent yes
Hostname %h
IdentityFile ~/.ssh/nagmat_bastion_key
IdentitiesOnly yesHost * !bastion-?.fabric-testbed.net
ProxyJump nagmat_0051461802@bastion-1.fabric-testbed.net:22″P.S: I have sshed the slices that I have created manually by using this ssh_config file and it was working fine.
- This reply was modified 1 year, 9 months ago by Nagmat Nazarov.
I think you need to use the private key in that ssh command rather than the public one.
Paul
I am using private key infact, but tried the public key just to check if it will work.
When I execute : ” ssh -F ssh_config -i ~/.ssh/nagmat_sliver_key ubuntu@2607:f018:110:11:f816:3eff:fe56:fe96 ”
getting :
“Warning: Permanently added ‘bastion-1.fabric-testbed.net,152.54.15.12’ (ECDSA) to the list of known hosts.
Warning: Permanently added ‘2607:f018:110:11:f816:3eff:fe56:fe96’ (ECDSA) to the list of known hosts.
Received disconnect from UNKNOWN port 65535:2: Too many authentication failures
Disconnected from UNKNOWN port 65535 ”- This reply was modified 1 year, 9 months ago by Nagmat Nazarov.
January 18, 2023 at 11:16 pm in reply to: Getting “(invalid_grant) invalid refresh token” error message on JupyterHub #3638Hello Komal,
I deleted my old configuration and reconfigured it according to this tutorial : https://www.youtube.com/watch?v=ieTr9Mj6uuc
I can ssh my server “ssh -F ssh_config -i nagmat_sliver_key ubuntu@xyz” but still getting :
” Exception: b'{\n “errors”: [\n {\n “details”: “(invalid_grant) invalid refresh token”,\n “message”: “Internal Server Error”\n }\n ],\n “size”: 1,\n “status”: 500,\n “type”: “error”\n}’ ” error.
The issue was :
“export FABRIC_PROJECT_ID=527832fc-c273-***
export FABRIC_BASTION_USERNAME=nagmat_xyz”I removed ‘ sign from the username and project id and it got resolved.
January 18, 2023 at 8:49 pm in reply to: Getting “(invalid_grant) invalid refresh token” error message on JupyterHub #3633Thanks for quick response.
The issue I reported was resolved but got another error:
“Exception: 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 = \\\\\’d2120937-8303-4a00-9ddb-d25aef36335a\\\\\’\\”,\\\\n \\”message\\”: \\”Not Found\\”\\\\n }\\\\n ],\\\\n \\”size\\”: 1,\\\\n \\”status\\”: 404,\\\\n \\”type\\”: \\”error\\”\\\\n}\’, refresh_token: NB2HI4DTHIXS6Y3JNRXWO33OFZXXEZZPN5QXK5DIGIXTOMJVGM3DAMTBGZSGKODCGU4TAYJQGYYGEZBYGYZDOZRZMM4WIYZ7OR4XAZJ5OJSWM4TFONUFI33LMVXCM5DTHUYTMNZUGA4TEOJQHAZDINBGOZSXE43JN5XD25RSFYYCM3DJMZSXI2LNMU6TQNRUGAYDAMBQ”,\n “message”: “Internal Server Error”\n }\n ],\n “size”: 1,\n “status”: 500,\n “type”: “error”\n}'”
I attached the screenshot too for your consideration.
- This reply was modified 1 year, 10 months ago by Nagmat Nazarov.
January 18, 2023 at 5:17 pm in reply to: error in slice submit : `refresh_token` must not be `None` #3628I am getting :
“Exception: b'{\n “errors”: [\n {\n “details”: “(invalid_grant) invalid refresh token”,\n “message”: “Internal Server Error”\n }\n ],\n “size”: 1,\n “status”: 500,\n “type”: “error”\n}'” as shown in the picture.
What am I doing wrong?
-
AuthorPosts