jFed Feedback #2501: Connectivity Issue: Node 2 unreachable

[jfedbug...@ilabt.imec.be]

The jFed Experimenter GUI sent feedback for user gil...@wall2.ilabt.iminds.be

Feedback:
Type: Connectivity Issue
Related testbeds: urn:publicid:IDN+wall1.ilabt.iminds.be+authority+cm

Description:
I can't connect via ssh to node 2 (node2.giwer.wall2-ilabt-iminds-be.wall1.ilabt.iminds.be) in my experiment. I have restarted this node but that did not seem to resolve the issue. I am using a vpn of idlab-igent to connect to the cluster, this worked before. The other nodes are still reachable.

The nodes run a kubernetes cluster with node 2 being one of the three worker nodes. It could be that the node had a high resource usage but I can't confirm since using the kubectl describe command shows me "unknown" for node 2 due to these connection issues.

[Brecht Vermeulen]

Hi,

indeed, the node keeps closing the ssh connection.

And we lost also the IPMI remote management link (probably unrelated issue), so not much we can do remotely currently I'm afraid.

Brecht

--
You received this message because you are subscribed to the Google Groups "fed4fire-experimenters" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fed4fire-experime...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fed4fire-experimenters/1030124061.24.1617983968909%40flsmonitor-api.atlantis.ugent.be.