-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong x-scale on disc-related statistics #23
Comments
I checked all my stats and x-scale look good. I don't really understand your issue maybe, pasting a screenshot will help to understand. |
I'm suspecting the graph update to be hang. |
Did you try to delete the RRD and let RPi-Monitor recreate them? |
Had no time for systematic checks, yet. Let's leave this issue open until I made some more investigations. |
Hello all. I just signed up to git, to confirm the issue which deMattin discovered. I'm using RPi-Monitor for several weeks but didn't notice that some ticklabels showed the wrong time. As an example the graph for swap is using the lastupdate time from empty.rrd not from swap_used.rrd: the graph for cpu is using the correct lastupdate timestamp from load1.rrd: I used following command on my rpi to see xml-dumps of rrds: There may be some wrong calculation on the client side in js-code for some reason? |
I think i found an easy way to fix this for me. After being created, empty.rrd is never updated again, so the timestamp remains always the one of the creation. What would happen, if it would be updated like all other rrds after every delay? So I tried the following:
Now empty.rrd will be updated after every delay as all other rrds. The value doesn't matter and will always be the same (NaN) but the timestamp is updated. This is a workaround I can live with. 👍 Any comments on this? |
I made some changes and tests but couldn't find another way to fix it. I made this changes too and you don't need to delete the rrds.
Thanks! |
empty.rrd needs to be generated each time a static data need to be drawn into a graph. |
With the newest Version 2.6 of RPi-Monitor I have the bug again and the fix as described from eagle-1 didn't work anymore. It only occurs on graphs which also has a static line. How can that be fixed? |
I do reopen this bug since it looks not fixed... I'll update rpimonitord to generate empty.rrd with the correct ownership. |
Change ownership of empty.rrd to activate on demand regeneration. |
Got bit by this because running with systemd two processes are started as root:root, but a third one as pi:pi. Hence The fix (in my case at least):
/PS: if running as user pi the CPU freq is |
As first mentioned here: #22 (comment) I have an issue with wrong x-scale on some statistics.
This is with all values, that have this static-data in (discs, sd, swap) and memory. The other scales are ok.
The graph is drawn correctly but the x-scale (date/time) has always fixed values.
On day-view it goes from 01:13:30 to 01:13:20 (full day).
It first occurs with version 2.4 but is the same after updating to 2.5 (complete reinstall).
Tried it also with the default configs and with deleting the rrd-files - same problem.
Does anybody have an idea?
Does noone else have this problem?
Especially feedback form users with a very first and clean install of rpimonitor would be very helpfull to me.
The text was updated successfully, but these errors were encountered: