JarvisOS HomeLab status
No signal

Recover: Home1

No signal critical

Primary home compute node. Runs the JarvisOS control plane, the Postgres primary and internal DNS.

Owner
homelab-operator
Target RTO
30m
Last heartbeat
never
Dependent entities
6
Recovery readiness50/100
← Back to status

Procedure

Read fully before acting.
  1. Confirm mains power and UPS state at the home rack.
  2. If unreachable, check the switch port LED and `tailscale ping uk-james-home1` from VIN — the mesh is the only administrative path in.
  3. Power-cycle via the UPS-managed outlet only after confirming the host is not mid-write on the Postgres primary.
  4. On boot, verify service start order: postgres-primary -> jarvisos-control-plane -> internal-dns.
  5. If Home1 stays down past the 30 minute RTO, promote postgres-replica on VIN (see the postgres-primary recovery page).

Bring-up order

Dependencies first — starting out of order is a common second incident.
  1. Home1 Node target

Failover targets

mode: manual

What this affects

Impacted if this stays down, or while you restart it.
Downstream JarvisOS Control Plane Postgres (primary) Redis (cache / queue) Internal DNS JarvisOS Worker (VIN) JarvisOS Auth (SSO)

Readiness breakdown