[Ilya Baldin]

Ok we will create an internal ticket for this and copy you on it. There appears to be some deeper problem here. You will receive an automated email once the ticket is created and will be able to respond to the ticket by replying to that email or our comments on it.

[Ilya Baldin]

There is also ‘cilogon.org’ cookie you may need to clear. To test your access, try starting from incognito/private window, login to the portal then to the Jupyter Hub. If this works, the issue is with the cookies in  your main browser window.

[Ilya Baldin]

Hello,

Not yet. This is a planned feature that hasn’t been implemented yet.

 

[Ilya Baldin]

If the problem is still with OAuth error messages, please go into your browser settings (this is heavily dependent on which browser you use) and clear/delete any cookies that have the name ‘fabric’ in them. Typically there is a ‘Privacy’ section in the settings that lets you see and selectively remove cookies.

After that you will need to re-login to the portal and try to get to the Jupyter Hub again.

[Ilya Baldin]

Hello,

Perhaps the problem is that the Jupyter notebook doesn’t start, i.e. hangs with a progress bar after you completed the login? If so then the problem is that the Jupyter Hub is at capacity and no new containers can be started. We are planning an upgrade next Tuesday (09/13/22) to remove this constraint. Please confirm if this is the problem you are seeing or you actually cannot login.

[Ilya Baldin]

This issue has been resolved, Jupyter Hub is available again.

[Ilya Baldin]

Dear experimenters,

We were able to finish the update early, FABRIC is open for business again. Please look at Release Notes for this release for the new features that are now available. If you had slices and they were extended prior to maintenance, they should still be available to you to continue working on them.

[Ilya Baldin]

I’m sorry but we cannot discuss pricing since each university (system) has its own agreements with Dell that affect the prices and discounts. You need to work this out with your Dell representative. Also ME4084 has reached its end of life (right as we ordered our last sites) and now there is a new ME5084 unit.

[Ilya Baldin]

This error is harmless in this case, but we will streamline our dependencies in the future to avoid these warnings.

[Ilya Baldin]

Can you provide a fuller stack trace to the most recent error with reading/importing the graph?

[Ilya Baldin]

Mason,

Here is a longer explanation of how to properly store your keys and SSH configuration in Jupyter Hub:

The keys in /home/fabric/.ssh/ are not persistent across the container boots. It’s user’s responsibility to upload their keys at a location under /home/fabric/work directory, which is persistent. They can then point FABLib to use that as below:

By default a rc file with the required environment variables is created at /home/fabric/work/fabric_config/fabric_rc

export FABRIC_BASTION_KEY_LOCATION=/home/fabric/work/fabric_config/fabric-bastion
export FABRIC_SLICE_PRIVATE_KEY_FILE=/home/fabric/work/fabric_config/id_rsa
export FABRIC_SLICE_PUBLIC_KEY_FILE=/home/fabric/work/fabric_config/id_rsa.pub

Workflow for SSH:

1. Update /home/fabric/work/fabric_config/ssh_config to reflect the correct keys and bastion user name
   SSH to the VMs using the following command

ssh -F ~/work/fabric_config/ssh_config -i ~/work/fabric_config/id_rsa <username>@<mgmt-ip>

Workflow for Notebooks:

1. Update the environment variables in /home/fabric/work/fabric_config/fabric_rc
2. Import the environment variables in the notebooks as below

fabric_rc_location=os.environ[‘HOME’]+”/work/fabric_config/fabric_rc”
   if os.path.exists(fabric_rc_location):
      with open(fabric_rc_location, ‘r’) as f:
         for line in f:
            if line.startswith(‘export’):
               os.environ[line.split(‘=’)[0].split(‘export’)[1].strip()] = line.split(‘=’)[1].strip()

ssh_key_file_priv=os.environ[“FABRIC_SLICE_PRIVATE_KEY_FILE”]
ssh_key_file_pub=os.environ[“FABRIC_SLICE_PUBLIC_KEY_FILE”]

ssh_key_pub = None
with open (ssh_key_file_pub, “r”) as myfile:
   ssh_key_pub=myfile.read()
   ssh_key_pub=ssh_key_pub.strip()

[Ilya Baldin]

We’ll make a list of useful software. Please add to this thread.

 

[Ilya Baldin]

That is almost certainly it. We will apply a hotfix, but you should try.

[Ilya Baldin]

Nick, I believe your key format is wrong. I need to check why you are not getting an appropriate error message. Please use a format described in this article:

Logging into FABRIC VMs

 

[Ilya Baldin]

Of course there is, but indulge us for a minute  – let’s see if we can figure this out. If you are having this problem, someone else might at some point.

The service runs of https://uis.fabric-testbed.net/ui/

[Author]

Posts