JarvisOS HomeLab status
No signal

Recover: JarvisOS Worker (VIN)

No signal important

Executes dispatched tasks in isolated workspaces on the edge node.

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

Procedure

Read fully before acting.
  1. Workers are stateless: restarting is safe once the control plane is reachable.
  2. Check for orphaned workspaces under /var/lib/jarvisos/workspaces before restarting.

Bring-up order

Dependencies first — starting out of order is a common second incident.
  1. VIN / VPS Node
  2. Home1 Node
  3. Postgres (primary) Database
  4. ISP Uplink Dependency
  5. Google OAuth Dependency
  6. Redis (cache / queue) Database
  7. JarvisOS Auth (SSO) Auth
  8. JarvisOS Control Plane Service
  9. JarvisOS Worker (VIN) Service target

Readiness breakdown