[Hussam Nasir]

I dont see any issues on your VM.

i tried this in your VM and it seems to do the right thing

ubuntu@e0a0baa2-fbe3-4d6b-92b9-6d1c74b93897-ei11:~$ sudo apt install python3-scapy

[Hussam Nasir]

Which other site are you seeing this ? Can you provide me the IP address of your host/VM ?

[Hussam Nasir]

You do have sudo access on your machine to edit this. But please read online posts regarding editing DNS settings for Ubuntu. UBUNTU 18 and higher use systemd-resolved (or resovectl) to make changes to DNS settings.  Due to a bug at the NCSA site. ubuntu seems to be picking up DNS servers that are restricted by the hosting site(NCSA).

2606:4700:4700::1111, 2620:0:c80:2::1, 2620:0:c80:2::3 these three DNS servers should work, but i am unable to find the right command to overwrite the settings in resolvectl. The commands i have tried just add these servers to the existing list which does not help. Using Rocky Linux or some other FABRIC Site may work.

[Hussam Nasir]

I believe the Issue is with the DNS servers the Ubuntu images at NCSA end up using. Rocky Linux seems to pick up the right DNS servers but Ubuntu image are not at NCSA.

If you switch to using 2606:4700:4700::1111, 2620:0:c80:2::1, 2620:0:c80:2::3 these DNS server, it should work.

I am investigation on a proper fix , but this will be a workaround for now.

[Hussam Nasir]

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.

[Hussam Nasir]

Yes thats the plan. I just updated the Forum page that talks about setting up the environment.

But an FYI, the current names do still work as they are now just CNAMES in DNS pointing to bastion.fabric-testbed.net

• This reply was modified 1 year, 10 months ago by Hussam Nasir.

[Hussam Nasir]

This maintenance is now complete.

[Hussam Nasir]

Dear experimenters,

This outage has been resolved. Please continue using your FABRIC resources and experiments.

[Hussam Nasir]

Regrading 1, you have a typo in the path for your sliver key.

[Hussam Nasir]

The second workaround you mentioned is just a command line representation of the jump instructions in the ~/work/.ssh/config file.

[Hussam Nasir]

the -F is required when using  jupyterHub because ssh looks for its config file in ~/.ssh/config . When using JupyterHub, this is not possible for persistence since the files in ~/ gets reset. Instead the docs talk about saving files that need to be persistent in ~/work. Hence the ssh config directory is stored in ~/work/.ssh/config and thus the need for the -F to tell ssh where the config file resides .

[Hussam Nasir]

If you VM is using an IPv6 address, which is the case with all FABRIC sites except MAX, then sites like github and dockerhub may not be accessible wince they are IPv4 only. A temporary solution is to use a NAT64 as mentioned on https://nat64.net/

[Hussam Nasir]

This maintenance has been completed. Thank you for your co-operation.

[Hussam Nasir]

The issue still exists.  Users will be informed when the site is back online.

[Hussam Nasir]

This issue was been resolved. Please continue your work.

[Author]

Posts