Barney
December 5, 2021, 2:01pm
#1
I'm running Openwrt 21.02.1 on an Archer C7 V5. Everything okay so far.
I've installed zram-swap to ease the small amount of RAM (128 MB). In order to watch the usage of the swap device I installed collectd-mod-swap.
But nothing happened. Under Statistics/Setup there's no entry for the swap plugin nor under Statistics/Graphs a graph.
As next step I created the file /etc/collectd/conf.d/swap.conf with the following content:
LoadPlugin swap
<Plugin swap>
ReportByDevice true
</Plugin>
Now the swap plugin is loaded,
Dec 5 14:42:39 daemon.err collectd[7905]: plugin_load: plugin "swap" successfully loaded.
but furthermore I have no entry under Statistics/Setup nor a graph under Statistics/Graphs.
I verified, that collectd is collecting data for the swap device,
-rw-r--r-- 1 root root 70604 05.12.2021 14:54:30 /tmp/rrdata/H2O-PIANO/swap-dev_zram0/swap-free.rrd
-rw-r--r-- 1 root root 70604 05.12.2021 14:54:30 /tmp/rrdata/H2O-PIANO/swap-dev_zram0/swap-used.rrd
but there is no graphical representation.
I suspect, that I'm missing something, but I don't know what. Can anybody give me a helping hand?
hnyman
December 5, 2021, 2:29pm
#2
Support for that plugin has never been implemented in LuCI statistics.
It is so rare.
hnyman
December 5, 2021, 3:57pm
#4
You can try adding support for it.
The addition requires in practice that you have the swap plugin database for testing, and you have it now.
Here is example, how I added chrony plugin a while ago.
committed 03:50PM - 22 Dec 20 UTC
Add initial support for chrony statistics.
At this point introduce time offset a… nd stratum stats.
There is something strange with the host option.
Anything else than 'localhost' or '127.0.0.1' causes an error at
collectd start, even when /tmp/collectd/conf is directly edited
Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
Barney
December 7, 2021, 4:36pm
#5
I tried to follow the link, but get an error, when accessing it:
NET::ERR_CERT_INVALID
Is github being hacked? Or is there any other reason?
hnyman
December 7, 2021, 5:23pm
#6
No idea what you are talking about. The page opens quite normally...
Barney
December 7, 2021, 5:45pm
#7
Same here with firefox, the error appeared in chromium.
Thanks for your feedback.