Repository navigation
Troubleshooting and Support
Start with these read-only commands on the Unraid host:
/etc/rc.d/rc.vnstat status
/etc/rc.d/rc.vnstat database_path
vnstat --config /etc/vnstat/vnstat.conf --iflist
vnstat --config /etc/vnstat/vnstat.conf --dbiflist
vnstat --config /etc/vnstat/vnstat.conf --showconfig| Symptom | Check |
|---|---|
| No traffic rows | Service enabled, correct interface, vnStat records, visibility/filter settings, and time for new data. |
| Threshold unavailable | Invalid input, missing period/interface data, configuration error, or backend failure. |
| Unexpected RX/TX | Observation point: physical NIC, bridge, or virtual peer. |
| Missing workload labels | Matching enabled, discovery succeeds, interface still exists. Virtual names can change. |
| Action did not run | Correct switch, valid limit/target, actual transition, rule outcome, and syslog. Repeated states are not retries. |
| Traffic marked stale | Last successful refresh, service/query errors, and connectivity. The retained value is an older sample. |
| History missing after reboot | Persistence, backup validity/path/checksum, effective DatabaseDir, and shutdown backup execution. |
| Images missing | Try text metrics and check image-generation support. |
| Save failed | Inspect error, runtime/persistent files, flash space, permissions, and recovery copy before retrying. |
Log tags include dvm-notify, dvm-user-actions, and dvm-gui. Transport failures
can leave earlier UI numbers visible; check backend state rather than treating
unchanged numbers as a fresh sample.
Issues should include plugin version/branch, Unraid version, reproduction steps, expected/actual behavior, relevant settings, and sanitized logs. Remove credentials and private server/workload details. Review any settings directory or traffic database before sharing it.
An older build or missing/invalid installed release metadata can show an unknown release. Do not infer the installed channel from a GitHub tab, the repository default branch, or an old install URL. Check the installed manifest and update to a newer announced build of the intended channel. Report the exact observed version and channel when requesting support.
Reload the plugin/settings page after installation. GitHub raw branch endpoints can be cached; distinguish a branch-cache delay from a failed publication by checking the published commit and package checksums. Do not repeatedly uninstall or reset data to work around a display/update-cache issue.
Data Volume Monitor · Issues · License
Stable and Development share the dvm identity. Keep independent backups; manual host-acceptance items remain pending until observed.
- Home
- Installation and channels
- First-time setup
- Thresholds and notifications
- Docker, VM, and custom actions
- Reports and displays
- Editor and scripts
- Backup and recovery
- Original-plugin migration
- Reset, purge, and uninstall
- Troubleshooting and support
- vnStat backend
- Development and releases
- Host acceptance