Forum Replies Created
-
Posts
-
Looking at it now. May i please ask which JH container option are you running?
I mean which option did you select when you logged in to JH?
Best,
Komal
- WASH may have enough resources in aggregate, but individual hosts may lack the capacity needed for your requested VMs, resulting in the
Insufficient Resourceserror. - Resources associated with a Closing slice are released, as they are for a Dead slice. Delayed responses to resource closure requests can sometimes leave a slice stuck in the Closing state.
- This may have been a transient error. The slice looks healthy, and all requested resources are now Active.
Best,
Komal
- WASH may have enough resources in aggregate, but individual hosts may lack the capacity needed for your requested VMs, resulting in the
Insufficient Resourceserror. - Resources associated with a Closing slice are released, as they are for a Dead slice. Delayed responses to resource closure requests can sometimes leave a slice stuck in the Closing state.
- This may have been a transient error. The slice looks healthy, and all requested resources are now Active.
Best,
Komal
Hi,
- Your switch request was rejected because the resource was unavailable, as indicated by the error
Insufficient resources: [unit]. We currently have only five Tofino switches, and demand is high. Please check the Resource Calendar in LoomAI for future availability. Because FABRIC is a distributed system, another request may have acquired the switch between the availability check and the processing of your request. I have verified that another slice holds the switch and was created at the similar time when your slice requests were triggered. - All resources associated with slices in the Closing or Dead state are released.
Best,
KomalHi Vakhob,
If you run into a token error, please restart your JH container via
File -> Hub Control Panel -> Stop My Server followed by Start My Server.
Also, to avoid the Unique name error, please restart the Notebook kernel.
If not using already, please consider using the new recommended way of using FABRIC via loomai.net.
Best,
Komal
Hi Romaric,
We may not have the on Portal yet. But if you share which publication needs to be associated with the corresponding project we can update that for now. We will also work to address this on the portal.
Best,
Komal
Hi Stephen,
There was a mismatch in the code for
configurefunction 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
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,
KomalHi Garegin,
Could you please share the error they are encountering?
I verified that the
configure_and_validate.ipynbnotebook 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
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
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
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
- WASH may have enough resources in aggregate, but individual hosts may lack the capacity needed for your requested VMs, resulting in the
