Nomad Troubleshooting

Debugging the cluster control plane.

Infrastructure

Steps

If UI is down or jobs failing:

1. SSH Access

ssh root@138.199.222.109

2. Service Status

systemctl status nomad

If inactive/failed:

systemctl restart nomad

3. Cluster Members

Verify server sees clients:

nomad server members
nomad node status

• members: Should be alive.
• node status: Clients should be ready.

4. Logs

journalctl -u nomad -f

Common Issues:

• Disk Space: df -h
• Consul: systemctl status consul

5. Client Debugging

SSH into specific client (e.g., 91.99.17.219).

systemctl status nomad
journalctl -u nomad -n 100

Cluster Restart

Last Resort for inconsistent state:

1. Stop Nomad on all clients.
2. Stop Nomad on server.
3. Start Nomad on server (wait for leader election).
4. Start Nomad on clients.