VMs become unresponsive

[scottyeager]

We are hearing a variety of reports about VMs running on Zos nodes that simply stop functioning. They don't respond to pings or SSH connections. In some cases the cloud console is also simply unavailable. Node logs haven't provided any useful clues yet, but further investigation is needed there.

This is a meta issue to collect info on reports of this kind. Let's use a template like this:

• Node ID
• Contract ID
• Date and time that the VM became unresponsive (best estimate)
• Any further details provided by the user (if applicable)
• Potential clues found in node logs (if applicable)

[RoberL72]

In this instance it happened twice with the same customer. Used Terrform script (one that I use with many customers) to deploy Nextcloud All in One on his node and use our gateway for a URL and access.

• Node ID: 7293 (customer) 6968 (gateway)
• Contract ID: 1226677
• https://casteljohn.tfcloud.eu/ reports Bad Gateway approx June 8th. (Deployment June 3rd)
• Will ask customer for any details...

Certified node 7293 is up and looks healthy.

Update; while looking at the node something suddenly occurs to me; it was a 200 GB deployment but the disk space used shows over 220 GB. Is this Nextckloud behaviour when you load more onto it then the vm size? I noticed before NC is very bad in space management. Any experience here?

[ramezsaeed]

which network interface is not responsive ? Ex. (Myceliym, IP4)