RPi-Monitor on Raspbian OS Bullseye.

[4k3or3et]

Hi All

i just installed RPi-Monitor on Raspbian OS Bullseye. Exactly the same config like on Buster. The problem i am facing on new OS are graphs. For example uptime was always linear. Now it behaves like zig-zag. Very often next value of uptime is represented as lower that previous which does not make sense.

The same is for other values like SOC or RAM voltages where the values all 99% of time at exactly same level.

Anyone have a clue how to fix that?

[gworley]

Hi this doesn't answer your question. I cannot get it to install on my Raspberry Pi running bullseye.

[4k3or3et]

Anyone?

[sborn]

I have it running and behaving normally on Bullseye on 16 pis. I don't imagine that helps you guys, but maybe the bugs have been resolved?

[adi170-alt]

Hi this doesn't answer your question. I cannot get it to install on my Raspberry Pi running bullseye.

oof, it works on mine, but my pi crashed a few times, but that was because I was trying to overclock my pi.
but one problem that I see, and I don't know if it is normal, is that the overclocked MHz just jump to the 600mhz while set to 2000, it is normally at 2000, but it jumps, but like I said Most time it just says 2000mhz.

---

Hi All

i just installed RPi-Monitor on Raspbian OS Bullseye. Exactly the same config like on Buster. The problem i am facing on new OS are graphs. For example uptime was always linear. Now it behaves like zig-zag. Very often next value of uptime is represented as lower that previous which does not make sense.

[image]
[image]

The same is for other values like SOC or RAM voltages where the values all 99% of time at exactly same level.

Anyone have a clue how to fix that?

Hi,
there is kind of a zigzag on my pi, but it isn't that harsh:
Temp: https://ss.adi1708.ga/files/kc6ob.mp4
but I haven't used rpi-monitor much because I just switched a few days ago to 64bit
this is what I have with uptime: https://ss.adi1708.ga/files/xv3rm.mp4

[gilarelli]

Hi,

Got the same trouble with most of my graphs - also after upgrading from buster to bullseye...

As an example, this is a graph that should show the number of IPs banned by fail2ban - it's a simple iptables interrogation that should always return an integer:

dynamic.6.name=banned
dynamic.6.source=iptables -L -n | awk '($1=="DROP" || $1=="REJECT") && $4!="0.0.0.0/0" {print $4}' | sort | uniq | wc -l
dynamic.6.rrd=GAUGE

Here is the result on the status page:

And here on the statistic page:

Detail of the values:

Here is another example, the graph for the root fs use: