Forum Replies Created
-
Posts
-
Just to follow up, this issue may take a while to resolve as it involves working with upstream campus network providers too.
Thank you for reporting this. It seems this may be a campus issue. We have notified the local campus to investigate and report back to us. We will inform you when its resolved.
Please try this again now and let us know if this works. We fixed some of the nodes involved in your slice that had errors.
From looking at the console boot messages of your VM, we observed that you may have changed the default route for the VM which overwrote the gateway IP needed to ssh into your VM. I see that the default gateway is now your FABNETv4 subnet. This would cause you to lose ssh connectivity to your. You have to delete this VM and start over and make sure not to change the default gateway of the VM.
Hello Nirmala,
Komal’s reply to your question may not have made it to your inbox as we (admin team) were updating the mailer component of this forum while she replied to you. Hopefully, this repost will make it to you.
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.6Also, if you face issues running notebooks on JH, please ensure there are no entries for
fabrictestbed-extensionsinfabric_config/requirements.txt. If you have any entries there, Please remove them and restart your JH container.Thanks,
Komal
Due to an issue just discovered in newy-w2, we had to reboot the server. Please try your ssh in about 30 minutes. It should be up by then.
Hello,
prin-w2 is currently down. We are currently investigating the issue and will get back to you as soon as we find out the cause.
Hi,
This was due to a service outage this afternoon which has been resolved. See https://learn.fabric-testbed.net/forums/topic/outage-in-credential-manager-services/
Please let us know if your issues are still not resolved.
1 user thanked author for this post.
Again, that is not what Ilya meant by adding the host. What you did by adding “nameserver node1” is that you are telling your node that node1 is your DNS server. That line is incorrect. Please remove that line. Then IPv4 sites should work from this node. As for the “sudo: unable to resolve host Node1: Temporary failure in name resolution” message, it can be safely ignored. It is bound to happen as FABRIC does not provide name resolution for VM hostnames. These messages only pop up in Debian based operating systems. They do not show up on RPM based Operating systems
1 user thanked author for this post.
