OFFLINE Alert (Node Not Responding)

Why do you receive this message?

The OFFLINE alert is sent when the system detects that the node stopped responding to HTTP queries. You receive it when:

• The node doesn't respond to the /status query (timeout or connection error)
• Status changes from ONLINE to OFFLINE
• The system tried to connect to the node and didn't receive a response

⚠️ This is an important alert! The node is not working and requires your attention. If the node doesn't return to operation within 5 minutes, manual intervention is recommended.

What does the message contain?

• Alert image (IMG_0495.png) - Sent as the first message
• Status - ❌ OFFLINE – Node not responding
• Detection time - Exact timestamp of problem detection
• Summary - Explanation of what happened
• Possible causes:
  • Node crash or unexpected termination
  • System restart
  • OOM kill (out of memory)
  • Network failure
  • Full disk or I/O stall
  • Firewall or routing problem
• Recommended actions - Specific commands to check

How should you react?

1. Check service status:

   systemctl status redbelly.service

2. Check system logs:

   journalctl -u redbelly.service --since "15 minutes ago"

3. Check application logs:

   ls -la /var/log/redbelly/rbn_logs/

4. Check if the system restarted:

   last -x reboot | head

5. Check system resources:

   uptime
   top
   free -h
   df -h

6. If the node is not working, restart the service:

   sudo systemctl restart redbelly.service

7. After restart, check synchronization and peer count

Sending Logic

Element	Details
Trigger	Status change from ONLINE → OFFLINE in background_monitor() function
Check frequency	Every 15 seconds (each monitoring cycle)
Conditions	• previous_online_status != is_online • is_online == False • Telegram alerts enabled • Saves last_down_at = datetime.utcnow()
Format	First image (IMG_0495.png), then text message in Markdown
Duplicate prevention	Alert sent only on status change, not on every check