Pipe Network (Devnet) - Monitor
📊 Monitoring Pipe PoP Node
After your node is installed and running via systemd, here are several ways to monitor its health and performance.
✅ Check if the node is active
sudo systemctl status pop.service
Should return active (running)
🔁 Check logs
sudo journalctl -u pop.service -f
Add --since "1 hour ago" or --since "7 days ago" to filter logs.
📈 Check metrics
Make sure you're in the working directory (usually /var/lib/pop):
cd /var/lib/pop
pop --status
This will show the node ID and if it's registered properly.
💬 Generate referral code
pop --gen-referral-route
🔧 Must be run in the same folder as
node_info.json
🔁 Refresh your node info manually
pop --refresh
🔄 Auto-Restart Protection (Optional)
You can create a CRON job to auto-restart the node if it stops:
*/5 * * * * systemctl is-active --quiet pop.service || systemctl restart pop.service
You can also run a health check script (included in this repo):
*/10 * * * * /usr/local/bin/check_pop_node.sh
📁 Backup your node ID
Your identity and rewards are tied to the file node_info.json. Always keep a backup:
cp /var/lib/pop/node_info.json ~/node_info.backup
Store it safely offline.
📡 Check your node on Pipe Dashboard
Visit:
https://dashboard.pipenetwork.com/node-lookup
Paste your node ID (from pop --status) to see uptime, egress score, historical reputation and more.
If your uptime = 0% despite logs showing activity, it's often:
- Node restarts (auto-updates, weekly maintenance, cron?)
- Incomplete registration or RPC issues
- Time needed to accumulate stats
🧠 Tips:
- Avoid restarting the node too often — let it build a clean historical score
- Ensure ports 80, 443, and 8003 are always open via UFW or firewall
- Use a static IP or configure DDNS if you have dynamic IP
Stay synced, stable, and helpful to the network 🚀
