Troubleshooting¶
Common issues and their solutions.
Alerts Not Received¶
1. Verify configuration¶
2. Test alert providers¶
# Test all providers
tinymonitor test-alert
# Test specific provider
tinymonitor test-alert --provider ntfy
3. Check provider-specific issues¶
Ntfy¶
- Verify the topic URL is correct and accessible
- If using a private topic, ensure the token is valid
- Check if the ntfy server is reachable
SMTP / Email¶
- Gmail: Requires App Password, not your regular password
- Check spam/junk folder
- Verify port: 587 for TLS, 465 for SSL
- Ensure
use_tls = truefor secure connections
Gotify¶
- Use the Application Token, not Client Token
- Verify the URL ends without trailing slash
- Check if the Gotify server is accessible
Webhook¶
- Verify the URL is accessible from your server
- Check required headers (Authorization, etc.)
- Test with curl:
curl -X POST -H "Content-Type: application/json" -d '{}' YOUR_URL
Google Chat¶
- Webhook URLs expire if not used
- Regenerate the webhook in Google Chat settings
Service Won't Start¶
Check logs¶
# systemd (Linux)
sudo journalctl -u tinymonitor -n 50
# Direct run to see errors
tinymonitor -c /etc/tinymonitor/config.toml
Common causes¶
Invalid configuration¶
Permission issues¶
# Check config file permissions
ls -la /etc/tinymonitor/config.toml
# Should be readable (at least -r--r--r--)
sudo chmod 644 /etc/tinymonitor/config.toml
Binary not found¶
which tinymonitor
# Should return: /usr/local/bin/tinymonitor
# If not found, reinstall
curl -sSL https://raw.githubusercontent.com/Gu1llaum-3/tinymonitor/main/install/install.sh | bash
Configuration Errors¶
TOML syntax errors¶
Common mistakes:
# Wrong: missing quotes for strings with special characters
topic_url = https://ntfy.sh/topic # Error!
# Correct:
topic_url = "https://ntfy.sh/topic"
# Wrong: using = in section headers
[alerts.ntfy = true] # Error!
# Correct:
[alerts.ntfy]
enabled = true
Invalid threshold values¶
# Wrong: percentage over 100
warning = 150 # Error!
# Correct: must be 0-100 for percentages
warning = 80
Missing required fields¶
When a provider is enabled, certain fields are required:
Metric Not Reporting¶
Load Average on macOS¶
Load average works on macOS but values are interpreted differently than Linux. A load of 4.0 on a 4-core Mac is equivalent to 100% utilization.
Reboot Required¶
This metric only works on Debian/Ubuntu and derivatives. It checks for the file /var/run/reboot-required.
On other systems, this metric will always report "OK".
Filesystem Exclusions¶
Some paths are automatically excluded:
/snap/*(Snap packages)- Docker overlay filesystems
- Virtual filesystems (
/proc,/sys,/dev)
To exclude additional paths:
Disk I/O¶
If I/O metrics seem wrong:
- Ensure the system has actual disk activity
- Check if thresholds are set correctly (bytes vs. MB)
High CPU/Memory Usage¶
TinyMonitor is designed to be lightweight (<10MB RAM, <1% CPU). If you see high usage:
-
Increase refresh interval (minimum recommended: 5 seconds)
-
Disable unused metrics
-
Check for disk issues - slow disks can cause delays
Update Issues¶
Permission denied¶
Network issues¶
Check connectivity to GitHub:
Manual update¶
If automatic update fails:
After updating¶
Don't forget to restart the service:
Getting Help¶
If you can't resolve your issue:
- Search existing issues
- Open a new issue with:
- TinyMonitor version:
tinymonitor version - OS and architecture:
uname -a - Relevant log output
- Configuration (remove sensitive data like tokens/passwords)