sw_dm
/
openClaw_agent_dm
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
33 Commits
1 Branch
0 Tags
1.2 MiB
Tag: Branch: Tree: 887ae0593c
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '887ae0593c'
${ noResults }
openClaw_agent_dm/systemd/openclaw-agent-monitor.service

42 lines
863 B
Raw Normal View History Unescape

feat: Complete system architecture upgrade with auto-healing, notifications, and rollback - Added systemd services for system-level persistence (gateway + monitor) - Enhanced agent-monitor.js with auto-healing and Telegram notifications - Created deploy.sh for one-click deployment and management - Updated CORE_INDEX.md with complete architecture documentation - Updated MEMORY.md with implementation details and usage guide - All memory files now tracked in git for version control and rollback Features implemented: ✓ System-Level: Services auto-start on boot, survive logout/reboot ✓ Auto-Healing: Crash detection, auto-restart with rate limiting ✓ Multi-Layer Memory: Core (CORE_INDEX.md) + Long-term (MEMORY.md) + Daily (memory/) ✓ Git Rollback: ./deploy.sh rollback / rollback-to <commit> ✓ Telegram Notifications: Alerts on stop/error/restart events
1 month ago
[Unit]
Description=OpenClaw Agent Health Monitor
Documentation=https://docs.openclaw.ai
fix: User-level systemd configuration with linger support Critical fix for VPS/server deployments: - Gateway now uses user-level systemd (~/.config/systemd/user/) - Agent monitor uses system-level systemd (/etc/systemd/system/) - Added loginctl enable-linger requirement for persistence - Set XDG_RUNTIME_DIR and DBUS_SESSION_BUS_ADDRESS env vars - Updated deploy.sh with proper environment setup - Enhanced health check to verify linger and runtime dir - Updated agent-monitor.js with reliable gateway detection Documentation: - Added comprehensive systemd troubleshooting guide to MEMORY.md - Documented user-level vs system-level service architecture - Created deployment checklist for new servers - Added best practices for multi-agent deployments Files changed: - systemd/openclaw-gateway-user.service (new) - systemd/openclaw-agent-monitor.service (updated) - deploy.sh (complete rewrite of service management) - agent-monitor.js (improved gateway status checks) - MEMORY.md (added systemd troubleshooting guide)
1 month ago
After=network-online.target
feat: Complete system architecture upgrade with auto-healing, notifications, and rollback - Added systemd services for system-level persistence (gateway + monitor) - Enhanced agent-monitor.js with auto-healing and Telegram notifications - Created deploy.sh for one-click deployment and management - Updated CORE_INDEX.md with complete architecture documentation - Updated MEMORY.md with implementation details and usage guide - All memory files now tracked in git for version control and rollback Features implemented: ✓ System-Level: Services auto-start on boot, survive logout/reboot ✓ Auto-Healing: Crash detection, auto-restart with rate limiting ✓ Multi-Layer Memory: Core (CORE_INDEX.md) + Long-term (MEMORY.md) + Daily (memory/) ✓ Git Rollback: ./deploy.sh rollback / rollback-to <commit> ✓ Telegram Notifications: Alerts on stop/error/restart events
1 month ago
Wants=network-online.target
[Service]
Type=simple
User=root
WorkingDirectory=/root/.openclaw/workspace
Environment=NODE_ENV=production
fix: User-level systemd configuration with linger support Critical fix for VPS/server deployments: - Gateway now uses user-level systemd (~/.config/systemd/user/) - Agent monitor uses system-level systemd (/etc/systemd/system/) - Added loginctl enable-linger requirement for persistence - Set XDG_RUNTIME_DIR and DBUS_SESSION_BUS_ADDRESS env vars - Updated deploy.sh with proper environment setup - Enhanced health check to verify linger and runtime dir - Updated agent-monitor.js with reliable gateway detection Documentation: - Added comprehensive systemd troubleshooting guide to MEMORY.md - Documented user-level vs system-level service architecture - Created deployment checklist for new servers - Added best practices for multi-agent deployments Files changed: - systemd/openclaw-gateway-user.service (new) - systemd/openclaw-agent-monitor.service (updated) - deploy.sh (complete rewrite of service management) - agent-monitor.js (improved gateway status checks) - MEMORY.md (added systemd troubleshooting guide)
1 month ago
Environment=HOME=/root
Environment=XDG_RUNTIME_DIR=/run/user/0
Environment=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/0/bus
feat: Complete system architecture upgrade with auto-healing, notifications, and rollback - Added systemd services for system-level persistence (gateway + monitor) - Enhanced agent-monitor.js with auto-healing and Telegram notifications - Created deploy.sh for one-click deployment and management - Updated CORE_INDEX.md with complete architecture documentation - Updated MEMORY.md with implementation details and usage guide - All memory files now tracked in git for version control and rollback Features implemented: ✓ System-Level: Services auto-start on boot, survive logout/reboot ✓ Auto-Healing: Crash detection, auto-restart with rate limiting ✓ Multi-Layer Memory: Core (CORE_INDEX.md) + Long-term (MEMORY.md) + Daily (memory/) ✓ Git Rollback: ./deploy.sh rollback / rollback-to <commit> ✓ Telegram Notifications: Alerts on stop/error/restart events
1 month ago
# Monitor process
ExecStart=/usr/bin/node /root/.openclaw/workspace/agent-monitor.js
# Auto-healing configuration
Restart=always
RestartSec=5
StartLimitInterval=300
StartLimitBurst=10
# Resource limits
MemoryLimit=512M
CPUQuota=20%
# Logging
StandardOutput=journal
StandardError=journal
SyslogIdentifier=openclaw-monitor
# Security
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=read-only
ReadWritePaths=/root/.openclaw/workspace/logs
[Install]
WantedBy=multi-user.target