System Health Report
Warnings Detected
Uptime: 14d 15h 44m
Load: 0.32 / 0.24 / 0.14
Swap: None
Alerts: 0
Anomalies: 0
📊 System Metrics
CPU Usage
2.9%
Avg today · Peak 3.67% at 00:00
Memory
22.5%
3,604 MiB / 15,997 MiB
Disk Usage
3%
24 GB / 985 GB · 911 GB free
Network (Latest)
↓ 26.9 kbps
↑ 5.7 kbps
Peak: ↓ 124.2 kbps at 00:00
Disk I/O (Latest)
R: 53.0 KiB/s
W: 244.6 KiB/s
Normal levels throughout day
Anomaly Detection
✓ No ML anomalies detected
0 alerts · 0 warnings · 0 critical
🔧 Service Status
NginxActive
MosquittoActive
SupervisorActive
GunicornActive
MySQLActive
Celery BeatActive
Celery WorkerWarning
DjangoWarning
⚙️ Per-Process Breakdown
Top CPU Consumers
| Process | CPU % | |
|---|---|---|
| go.d.plugin | 1.44% | |
| netdata | 0.79% | |
| supervisord | 0.63% | |
| apps.plugin | 0.63% | |
| packagemanager | 0.27% | |
| rabbitmq | 0.21% | |
| mysqld | 0.19% | |
| mosquitto | 0.01% | |
| nginx | 0.00% |
Top Memory Consumers
| Process | MiB | |
|---|---|---|
| mysqld | 1,482 | |
| rspamd | 582 | |
| unicorn | 552 | |
| desktop | 468 | |
| supervisord | 287 | |
| netdata | 214 | |
| gdm3 | 194 | |
| php-fpm7.4 | 157 | |
| mailmanctl | 154 | |
| manage | 137 |
📋 Error Logs
Django Errors 946 errors
▶
All 946 errors are DST timezone conversion failures (pytz.exceptions.NonExistentTimeError).
Cause: Israel DST transition on 2026-03-27 — clocks skip 02:00→03:00, so times between 02:00-02:59 don't exist.
Impact: Non-critical. Invalid timestamps are skipped; MQTT data ingestion continues normally.
Sample:
2026-03-27 05:00:53,347 [ERROR] django: Skipping invalid timestamp 1774576807.0
pytz.exceptions.NonExistentTimeError: 2026-03-27 02:00:07
2026-03-27 05:00:53,348 [ERROR] django: Error converting epoch to UTC: 2026-03-27 02:05:06
pytz.exceptions.NonExistentTimeError: 2026-03-27 02:05:06
Pattern repeats for timestamps 02:00 through 02:55 across multiple controller data batches.
MQTT processing confirmed working — messages queued, ACKed, and saved successfully.
Celery Worker Warnings 9 warnings
▶
Benign startup warnings across 9 rotated worker log files (worker-error.log.2 through .10):
[2026-03-27 05:00:13,627: WARNING/MainProcess] No communication channel selected
[2026-03-27 05:00:13,565: WARNING/MainProcess] No communication channel selected
...repeated in each worker log rotation
This is a standard Celery message when no result backend is configured. Non-critical.
Gunicorn
▶
No errors found today (2026-03-27). ✓
Celery Beat
▶
No errors found today (2026-03-27). ✓
Mosquitto
▶
No errors found today (2026-03-27). ✓
Nginx Permission Denied
▶
Cannot read /var/log/nginx/error.log — Permission denied for svcmon_w7k user.
Service is confirmed active via systemctl. Log access requires permission fix.
Supervisor
▶
No errors found today (2026-03-27). ✓
Note: supervisorctl status returned permission error for read-only user, but systemd confirms service is active.
🗄️ Database Summary
| Database | Tables | Status |
|---|---|---|
| c1waterokdb | 44 | Accessible |
| dbispconfig | 77 | Accessible |
| phpmyadmin | 19 | Accessible |
| roundcube | 15 | Accessible |
155 tables total · Query time: 28ms
💡 Recommended Actions
Medium Priority
Fix DST handling in Django. Replace
pytz with zoneinfo (Python 3.9+) or dateutil to handle non-existent times during DST transitions. This will eliminate ~946 error log entries per DST switch. The current code in the MQTT data handler tries to localize epoch timestamps to Israel time but crashes on the skipped hour.Low Priority
Grant nginx log read access to svcmon_w7k. Add the monitoring user to the
adm group or adjust /var/log/nginx/error.log permissions so the health check can read nginx errors.Low Priority
Celery "No communication channel selected". Configure a result backend (e.g., Redis or RabbitMQ) or suppress this warning in Celery settings if result tracking is not needed.