Project

General

Profile

Actions

Bug #16302

closed

Thermal Sensor date range not correct

Added by Anil Kumar 2 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
Diagnostics
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
24.11
Affected Architecture:

Description

Thermal Sensor date range is NOT correct. When we select a date range 6 months, it always shows data of Year 2023


Files

Actions #1

Updated by Sayed Mohammad Badiezadegan 2 months ago

  • Status changed from New to Rejected

I checked this feature and confirmed that there is no problem with the latest firmware, even if I set it for 6 months.

Actions #2

Updated by Nathan Skoglund 2 months ago

As of Jul 8, I can reproduce this bug.
Status > Monitoring > defaults to processor utilization. Set to 1 year. Update graphs.
Shows 2024/07/09 - 2025/07/09 correctly.

Select thermal sensors; change nothing else, update graphs.

Actions #3

Updated by Nathan Skoglund 2 months ago

This is clearly not a release stopper; but it is a bug and we have at least 2 screenshots. Please re-open for tracking purposes

Confirm still problematic on 25.07.b.20250707.2346

Actions #4

Updated by Steve Wheeler 2 months ago

  • Status changed from Rejected to Feedback
  • Priority changed from High to Low

Check that the thermal data is still being updated:

[25.07-BETA][admin@m470-2.stevew.lan]/root: ls -ls /var/db/rrd/system-sensors.rrd 
672 -rw-r--r--  1 nobody wheel 686792 Jul  9 16:57 /var/db/rrd/system-sensors.rrd

If the number of thermal sensors available changes it will stop updating and the graphs will always show the old data.

Actions #5

Updated by Kris Phillips 2 months ago

  • Status changed from Feedback to New
Actions #6

Updated by Anil Kumar 2 months ago

Please find the output for command "ls -ls /var/db/rrd/system-sensors.rrd"

873 rw-r--r- 1 nobody wheel 2331368 Jul 9 16:19 /var/db/rrd/system-sensors.rrd

Actions #7

Updated by Kris Phillips 2 months ago

  • Status changed from New to Incomplete

Resetting the RRD data resolved this issue. It's possible there was corrupted or damaged RRD data and resetting it seems to have fixed it.

Setting this as Incomplete for now, but please reply here if the issue recurs and can be reproduced. I tested on my system and wasn't able to reproduce this.

Actions #8

Updated by Steve Wheeler 2 months ago

  • Status changed from Incomplete to Resolved
Actions

Also available in: Atom PDF