RNRecoverNodeServer resilience

Technical architecture

Two perspectives. Separate authority. Safer recovery.

RecoverNode separates observation from disruptive recovery so a broken monitoring path cannot automatically power-cycle a healthy server.

01

RecoverNode Observer

Runs on a separate Ubuntu host and monitors multiple servers and services.

  • Local and public DNS expectations
  • HTTP status, redirects, latency and content
  • TLS chain, hostname and expiration
  • TCP services including SSH, HTTP, HTTPS and application ports
  • Escalating alerts, recovery notices and persistent state
Evidence
not authority
02

RecoverNode Guard

Runs on the protected Linux server and makes decisions from local evidence.

  • Local HTTPS test using the production hostname and SNI
  • Nginx configuration validation
  • Restart, retest and guarded reboot escalation
  • Exponential backoff, cooldown and action budgets
  • Persistent lockout after unsafe repetition

Decision model

Recovery stops when the system cannot make a sane decision.

Healthy locallyNo action
Nginx failed locallyValidate, restart, retest
Persistent local failureApply cooldown and recovery budget
Ambiguous or invalid configurationFail open, lock out, alert
Operating system freezeHardware watchdog resets host
Observer cannot reach targetAlert only—no remote reboot

What it is not

RecoverNode is guarded recovery, not traffic failover.

It does not currently replicate application data, elect a primary server, move a floating IP, or update DNS to a standby host. Those capabilities belong to clustering and high-availability platforms.

Assess my environment