archy/neode-ui/stop-dev.sh

68 lines
1.8 KiB
Bash
Raw Normal View History

release(v1.7.41-alpha): post-OTA auto-rollback so a bad release cannot strand the fleet Closes failure mode FM5 from docs/bulletproof-containers.md: the v1.7.38 + v1.7.39 rollouts left every affected node on an unreachable UI (nginx 500) with no recovery path short of SSH. This release adds a self-check guardrail to the update flow. What changed: - apply_update() writes a pending-verify marker with old+new version and a 150s deadline immediately before scheduling the service restart. - verify_pending_update() runs from main.rs startup. If the marker is present and within its freshness window, the new binary waits 15s for nginx + backend to settle, then probes https://127.0.0.1/ every 5s for up to 90s (self-signed certs accepted). - On any probe success within the window, the marker is cleared and nothing else happens. - On window-exhaust, the new binary: 1. Moves the broken /opt/archipelago/web-ui to web-ui.failed.<ts> (quarantined, not deleted, so we can post-mortem). 2. Restores web-ui.bak on top of web-ui. 3. Calls rollback_update() to restore the previous binary. 4. Updates state.current_version to reflect the rollback. 5. systemctl --no-block restart archipelago so the OLD binary boots. - Markers older than 10 minutes are treated as stale and cleared without probing, so a crashed-during-startup marker from weeks ago cannot spontaneously roll back a healthy node on a later reboot. - rollback_update() binary copy now goes through host_sudo instead of tokio::fs::copy, so it escapes the service's ProtectSystem=strict mount namespace. Without this, the rollback silently failed with EROFS on /usr/local/bin and orphaned the rollback - the exact opposite of what auto-rollback is for. Tests: 4 new unit tests in update::tests covering marker round-trip, absent-marker noop, no-panic on verify_pending_update with nothing to verify, and an invariant assert that the 90s probe window stays below the 600s stale threshold. All passing. Side fix: scripts/create-release-manifest.sh was dying with exit 141 (SIGPIPE from tar tvzf pipe head pipe awk) under set -euo pipefail. Replaced with a single awk NR==1 that doesn't short-circuit the upstream pipe, so the release-build flow is idempotent again.
2026-04-22 16:14:35 -04:00
#!/usr/bin/env bash
# Neode Development Server Stop Script
# This script stops all running Neode dev servers
# Colors for output
RED='\033[0;31m'
GREEN='\033[0;32m'
YELLOW='\033[1;33m'
BLUE='\033[0;34m'
NC='\033[0m' # No Color
echo ""
echo -e "${YELLOW}🛑 Stopping Neode Development Servers...${NC}"
echo ""
# Function to kill processes on a port
kill_port() {
local port=$1
local name=$2
if lsof -ti:$port > /dev/null 2>&1; then
echo -e "${BLUE} Stopping $name on port $port...${NC}"
lsof -ti:$port | xargs kill -9 2>/dev/null || true
echo -e "${GREEN}$name stopped${NC}"
else
echo -e "${YELLOW} $name not running on port $port${NC}"
fi
}
# Stop all node processes related to Neode
echo -e "${BLUE}🔍 Finding Neode processes...${NC}"
echo ""
# Kill by port
kill_port 5959 "Mock Backend"
kill_port 8100 "Vite Dev Server"
kill_port 8101 "Vite Dev Server (alt)"
kill_port 8102 "Vite Dev Server (alt)"
echo ""
# Kill any remaining concurrently processes
if pgrep -f "concurrently.*mock-backend" > /dev/null; then
echo -e "${BLUE} Stopping concurrently processes...${NC}"
pkill -f "concurrently.*mock-backend" 2>/dev/null || true
echo -e "${GREEN} ✅ Concurrently stopped${NC}"
fi
# Kill any remaining node processes running mock-backend or vite
if pgrep -f "mock-backend.js" > /dev/null; then
echo -e "${BLUE} Stopping mock-backend.js...${NC}"
pkill -f "mock-backend.js" 2>/dev/null || true
echo -e "${GREEN} ✅ Mock backend stopped${NC}"
fi
if pgrep -f "vite.*neode-ui" > /dev/null; then
echo -e "${BLUE} Stopping vite...${NC}"
pkill -f "vite.*neode-ui" 2>/dev/null || true
echo -e "${GREEN} ✅ Vite stopped${NC}"
fi
echo ""
echo -e "${GREEN}✅ All Neode development servers stopped!${NC}"
echo ""
echo ""