0

My GCP Compute engine is down. In GCP console it is up and running. It is an Ubuntu 18.04 server with 0.6GB memory(an always free tier compute engine). It was not restarted for more than couple of months. The system usage was around 60% last checked. I have already checked this answer. And none of them seems valid for me(seems so).

  1. Free disk stands at 54%.
  2. SSH perfectly configured.
  3. No firewall issue.

It just seemed the VM stopped responding putting the hosted url down. When I checked Compute engine monitoring tabs, all the graphs were normal without any visible changes. I even checked the logging but no system crash kind of logs were present. I stopped and restarted the compute engine, and it started working perfectly, as nothing happened. In AWS, the VM instance failed System Reachability tests in such scenarios.

Does GCP has something similar like AWS system reachability test?

Any possible logs or something, by which I can understand the reason why the Compute Engine stopped responding?

Improve this question
1
  • Please check Serial port 1 (console) logs and update your question with output. Can restart your VM and collect full startup log from Serial port 1 (console)?
    – Serhii Rohoza
    Commented Jun 8, 2020 at 16:15

1 Answer 1

Reset to default
2

There are different kinds of test with custom scenarios in your project , please find it on reference link [1]

[1] https://cloud.google.com/network-intelligence-center/docs/connectivity-tests/how-to/running-connectivity-tests

Improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.