[Komal Thareja]

Hi Stephen,

There was a mismatch in the code for configure function and the actual BFB image on the host. I pushed a fix for this and updated the notebook too. The notebook should work now.

Thank you for sharing your observation and helping us address the issue. Appreciate it!

Best,

Komal

[Komal Thareja]

I’m glad to hear the issue has been resolved! Thank you for sharing the error message. We’ll work on making it clearer and more helpful.

Best,
Komal

[Komal Thareja]

Hi Garegin,

Could you please share the error they are encountering?

I verified that the configure_and_validate.ipynb notebook works without any issues with the latest API.

We also recommend using loomai.net as the new interface for accessing FABRIC. LoomAI is an AI-assisted graphical interface that also provides access to the existing JupyterHub environment.

Also, please try File -> Hub Control Panel -> Stop My Server, followed by Start My Server. This shall restart your Jupyter Hub container and refresh your tokens.

Please let me know if that resolves the issues.

Best,

Komal

• This reply was modified 2 days, 14 hours ago by Komal Thareja.

[Komal Thareja]

Looks like you are using Jupyter Hub. Could you please try File -> Hub Control Panel -> Stop My Server, followed by Start My Server. This shall restart your container and refresh your tokens.

Please let me know if that resolves the issues.

Best,

Komal

[Komal Thareja]

Hi,

Where are you running this Yifang? In jupyter Hub, LoomAI or locally?

It looks like refresh faced because of an invalid refresh token.

Best,

Komal

[Komal Thareja]

Jupyter and LoomAI access has been restored!

Best,

Komal

[Komal Thareja]

Hi Nirmala,

This could be an intermittent issue. Does your slice come up or are you still running into this?

If your slice is up, could you please share your slice id?

Best,

Komal

[Komal Thareja]

There was a bug for POA. Patch deployed and shared the information with Nirmala on the email chain.

Best,

Komal

[Komal Thareja]

Hi Nirmala,

Which JH container are you using?

Best,

Komal

[Komal Thareja]

Hi Kshitij,

Could you please check /home/fabric/work/fabric_config/fabric_rc file?

Please remove any quotes from the FABRIC_PROJECT_ID. I suspect it is set as export FABRIC_PROJECT_ID='<YOUR_PROJECT_ID>'. It should be instead: export FABRIC_PROJECT_ID=<YOUR_PROJECT_ID>

Best,

Komal

[Komal Thareja]

Apologies, Maureen! Unfortunately, I don’t see a way to recover from this error without reformatting.

I also wanted to mention our Ceph-based distributed storage, which supports POSIX volumes and S3 buckets. Although uploading the data will still take some time, the storage can be mounted across multiple VMs and slices.

If this is of interest, please let me know how much storage you would need. I can provision it for your project, attach it to your existing slice, and share instructions for future slices. For new slices, you can attach the distributed storage to any VM by setting storage=True either at the slice level with new_slice() or at the node level with add_node().

Best,
Komal

[Komal Thareja]

Hi Maureen,

API may be broken, I will look at that and post a fix tonight for that. But in the meanwhile, you should be able to use the device name: /dev/vdb.  Apologies for the inconvenience!

I was able to check that from your VM using the following command:

[root@fabric ~]# fdisk -l
Disk /dev/vda: 1000 GiB, 1073741824000 bytes, 2097152000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: BDF64B3C-A8BE-4079-BBEA-1B1AC099BF0A

Device Start End Sectors Size Type
/dev/vda1 2048 204799 202752 99M EFI System
/dev/vda2 204800 2252799 2048000 1000M Linux filesystem
/dev/vda3 2252800 2260991 8192 4M PowerPC PReP boot
/dev/vda4 2260992 2263039 2048 1M BIOS boot
/dev/vda5 2265088 2097151966 2094886879 998.9G Linux filesystem

Disk /dev/nvme0n1: 894.3 GiB, 960197124096 bytes, 1875385008 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/vdb: 9.8 TiB, 10737418240000 bytes, 20971520000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Best,

Komal

[Komal Thareja]

Both slices are in Stable states, node/network names shouldn’t matter. you should be able to reuse them across slices.

Slice Name: Globus Streams Slice ID: 34b37c6a-f1a3-4013-b38b-2f2a657aca88 Project ID: 68a571c9-8f05-4231-a8d3-09cef7537848 Project Name: SciWiT
Graph ID: ed936d11-cd63-4024-8a67-0ce5b64a7b30
Slice owner: { name: orchestrator, guid: orchestrator-guid, oidc_sub_claim: 5ecf7757-59a3-4bd8-b8b9-4e9d89450d99, email: seena@uchicago.edu}
Slice state: StableError
Lease time: 2026-08-13 17:13:55+00:00

Slice Name: Globus – Streams Slice ID: 1dd1fee4-ab1f-4f2d-80bf-e088d398006d Project ID: 68a571c9-8f05-4231-a8d3-09cef7537848 Project Name: SciWiT
Graph ID: 2a1e5b22-53b7-4a3a-865f-f3139e91ed61
Slice owner: { name: orchestrator, guid: orchestrator-guid, oidc_sub_claim: 5ecf7757-59a3-4bd8-b8b9-4e9d89450d99, email: seena@uchicago.edu}
Slice state: StableOK
Lease time: 2026-08-13 17:26:45+00:00

Best,

Komal

• This reply was modified 1 month ago by Komal Thareja.

[Komal Thareja]

Hi Seena,

I have deleted your slice. Could you please share the sequence of steps you followed when creating and using it? This will help us reproduce and address the underlying issue.

Thank you for your help.

Best,
Komal

[Komal Thareja]

Ceph and LLM Services have been restored.

[Author]

Posts