Playbook for Hetzner VMs being reported as unreachable: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
# Check with a separate device that the services being reported as down are unreachable | # Check with a separate device that the services being reported as down are unreachable | ||
# Manually run `traceroute -I` as root from status.delftinfra.net to a VM that is unreachable. | # Manually run `traceroute -I` as root from status.delftinfra.net to a VM that is unreachable. | ||
# Determine whether or not there is a hop in the path that is | # Check the traceroute items already configured on Zabbix to ns1, wouter.dev.delftsolutions.nl and vincent.dev.delftsolutions.nl | ||
# Determine whether or not there is a hop in the path, for any of these traceroutes, that is either the cause of the issue, or a likely contender for further investigation. | |||
Latest revision as of 03:05, 11 March 2024
Playbook for debugging Hetzner issue
- Check with a separate device that the services being reported as down are unreachable
- Manually run `traceroute -I` as root from status.delftinfra.net to a VM that is unreachable.
- Check the traceroute items already configured on Zabbix to ns1, wouter.dev.delftsolutions.nl and vincent.dev.delftsolutions.nl
- Determine whether or not there is a hop in the path, for any of these traceroutes, that is either the cause of the issue, or a likely contender for further investigation.