1. Komal Thareja

Komal Thareja

Forum Replies Created

Viewing 15 posts - 271 through 285 (of 411 total)
  • Author
    Posts
  • in reply to: exception error when reserving resources for a slice #6389
    Komal Thareja
    Participant

      Hi Nirmala,

      Which JH container are you using? This error typically happens due to a version mismatch for Fablib. Please see below:

      Fablib – if you are still using Release 1.5, please update fablib using the command:

      pip install fabrictestbed-extensions==1.5.6

      Also, if you face issues running notebooks on JH, please ensure there are no entries for fabrictestbed-extensions  in fabric_config/requirements.txt. If you have any entries there, Please remove them and restart your JH container.

      Thanks,

      Komal

      in reply to: Maintenance on Network AM – 01/22/2024 (3:00pm-4:00pm EST) #6384
      Komal Thareja
      Participant

        Network model has been updated and maintenance is complete!

        in reply to: Refresh Token Error #6338
        Komal Thareja
        Participant

          @Robin, could you please try to restart your JH container via File -> Hub Control Panel -> Stop My container -> Start My container when you see this error?

          Also, the path to replace the token is /home/fabric/.tokens.json . We will fix this in the documentation of it’s incorrect. Also, could you please let us know which JH container are you using?

          Thanks,

          Komal

          in reply to: Exposing Ports to the Outside World #6334
          Komal Thareja
          Participant

            @Lyod –  Fabnetv4Ext notebook has a bug and configures the route incorrectly. We will fix the notebook, sharing the fix needed to the routes below. Hope this helps!

            Configure Node1 cell in notebook should change the route as below via EXT gateway, ping should work.

            stdout, stderr = node1.execute(f'sudo ip route add 0.0.0.0/0 via {network1.get_gateway()}')

            Configure Node2 cell in notebook should change the route as below via EXT gateway, ping should work.

            stdout, stderr = node2.execute(f'sudo ip route add 0.0.0.0/0 via {network2.get_gateway()}')

             

            Thanks,

            Komal

            in reply to: Unable to use fablib.manager #6331
            Komal Thareja
            Participant

              Hi Shams,

              Could you please remove <> enclosing the project id in /home/fabric/work/fabric_config/fabric_rc and restart your JH container via File -> Hub Control Panel -> Stop Container followed by Start Container?

              Please try your notebook again and let us know if you still observe this error.

              Thanks,

              Komal

              in reply to: Fabric Testbed is open and ready for use! #6271
              Komal Thareja
              Participant

                STAR site has 6 worker nodes each with 128 cores = 768 cores. This is same as the previous release.

                Oversubscription is not enabled on STAR.

                Komal Thareja
                Participant

                  @Nagmat – Your back should be available in your new JH container as fabric_bkp.tgz. Please start your container and let us know if you face any issues accessing the data.

                  Thanks,

                  Komal

                  Komal Thareja
                  Participant

                    @Nagmat – Could you please stop your JH container? I took backup of your old files and would copy it your new container.

                    in reply to: Fabric Testbed is open and ready for use! #6253
                    Komal Thareja
                    Participant

                      Minor correction in the version above, Please update the fablib using the command:

                      pip install fabrictestbed-extensions

                       

                      in reply to: Unable to reserve slice #6187
                      Komal Thareja
                      Participant

                        @Kriti – the hypervisor on wash-w3 was down this morning and was recovered. Issues on WASH should clear now. I also verified TACC is working as well. Please try your slices again and let us know if you still face errors.

                         

                        @Nagmat – there was a leaked service due to timeout from TACC switch. I have cleaned up the leaked services, your slice provisioning should work as well. Please let us know if you still face errors.

                        in reply to: Maintenance on Network AM – 12/11/2023 (3:30pm-4:30pm EST) #6182
                        Komal Thareja
                        Participant

                          Maintenance has been completed!

                          in reply to: Unable to reserve slice #6177
                          Komal Thareja
                          Participant

                            Hi Kriti,

                             

                            There was an issue on new-y2 where your VMs were being provisioned as it had some leaked VMs. We rebooted the worker node, your slices should work on NEWY. We will also check STAR and WASH as well.

                            Thanks,

                            Komal

                            in reply to: Fabric Portal Jupytur Not Finding File #6138
                            Komal Thareja
                            Participant

                              Hello,

                              Could you please check if the file exists at the specified path using the command: ls /home/fabric/work/re_vit/notebooks/animal-blur-canine-551628.jpg ?

                              Thanks,
                              Komal

                              in reply to: Maintenance on Network AM – 11/12/2023 (3:00pm-4:00pm EST) #6089
                              Komal Thareja
                              Participant

                                The maintenance is complete!

                                in reply to: error when attempting to numa_tune #6063
                                Komal Thareja
                                Participant

                                  You are right Greg, this is totally dependent on how much memory is available on the Numa Node on the Host where your VM is launched at the current time.

                                Viewing 15 posts - 271 through 285 (of 411 total)