Troubleshoot Machines

If the Machine has trouble booting, is unresponsive or otherwise stuck, consider the following steps:

Enrollment

If the Enrollment doesn't go through as planned, check the Enrollment Images: Troubleshooting section.

Operations

The Operations tab shows recent or running operations accompanied by detailed logs what's happening. Check them first to see if something is going on or went wrong.

As long as the Machine is still online, you can also apply an older, working revision or reapply the current one (this will trigger a reboot).

Terminal

If the Machine runs and has connectivity to the Nest appliance, you can access a Machine shell by navigating to the Machine's Terminal Tab:

A good starting point to investigate errors is to become root (sudo -i) and check recent systemd logs for errors (journalctl -xe).

Startup Logs

If the Machine runs and has connectivity to the Nest appliance, the startup logs (basically all systemd logs) can be found in the Machine's Info Tab:

Timestamps

In the Info sections are various timestamps which hint at the current state of the Machine:

• Last Boot at: When the Machine had its last successful boot reaching meltcloud
• Agent Heartbeat: When the Machine last fully booted, was able to start the melt-agent and reached meltcloud

If those timestamps are far in the past, the Machine might have lost connectivity to Nest.

Serial console

If the Machine is stuck before it can reach Nest (and you can't access the Terminal or Startup Logs), you can only find the error by accessing the serial console.

Force unassign / delete

When all else fails and you consider your Machine lost, you can Force Unassign and delete the Machine to start from scratch.