Synchronization Alerts
Why do you receive these messages?
Synchronization alerts are sent when the system detects a synchronization status change of the node. You receive them when:
- OUT OF SYNC - Node is behind with synchronization (block difference > 5)
- SYNCHRONIZED - Node caught up with the network and is synchronized
⚠️ Note: Synchronization alerts are sent only when the node is ONLINE. If the node is OFFLINE, you won't receive a synchronization alert.
OUT OF SYNC Alert
What does the message contain?
- Status - ⚠️ OUT OF SYNC – Block height differs from governors
- Detection time - Exact timestamp
- Summary - Problem explanation
- Recommended checks:
- Comparison of currentBlock vs lastBlockFromGovernors
- Check connection to governors
- Check if the node is still downloading blocks
- Check logs
How should you react?
- Check block difference - Open the monitoring panel
- Check logs:
journalctl -u redbelly.service -n 100 - Check network connection - Does the node have internet access?
- Wait 10 minutes - If it's a temporary problem, the node should synchronize
- If the problem persists:
- Check if there are network problems
- Check if the node has sufficient resources (CPU, RAM, disk)
- Consider restarting the node
SYNCHRONIZED Alert
What does the message contain?
- Status - 🔄 SYNCHRONIZED – Blocks match governors
- Detection time - Exact timestamp
- Summary - Synchronization confirmation
- Information - No action required
How should you react?
✅ No action required - The node is synchronized and working normally.
Sending Logic
| Element | Details |
|---|---|
| Trigger | Synchronization status change in background_monitor() function |
| Check frequency | Every 15 seconds (each monitoring cycle) |
| Conditions | • Node is ONLINE (is_online == True)• previous_sync_status != is_synchronized• Telegram alerts enabled |
| Synchronization definition | • Block difference ≤ 5: SYNCHRONIZED • Block difference > 5: OUT OF SYNC |
| Format | Text message in Markdown (without image) |
| Duplicate prevention | Alert sent only on status change |