SOLVED Most reports are blank, TrueNAS-SCALE-22.12.1

[SmurfHunter]

 

[remer]

Under /var/db/system, do you have multiple rrd-* directories?

I'm having a similar issue. The dashboard cards are updating but the reports are displaying "null" for all values.

I do have multiple rrd-* directories. One of the is empty, and the other is populated.

I tried all suggestions in this thread. Should remove the empty rrd-* directory? Any advise would be greatly appreciated.

 

[Samuel Tai]

Please don't revive necro threads, but start your own.

That said, do you also have multiple configs-* and syslog-* directories? You'll want to delete the directories that aren't associated with the current running system.

 

[djonas]

Another datapoint, I was able to resolve my null report issue by setting my server BIOS time to UTC.

Running OS Version:TrueNAS-SCALE-22.12.1

 

[Aren]

Another datapoint, I was able to resolve my null report issue by setting my server BIOS time to UTC.

Running OS Version:TrueNAS-SCALE-22.12.1

you solved my problem. I had accidently changed the bios date, 1 day off. all counters were NULL, even after removing rdd databases and several reboots.. after correcting, all worked again.

 

[StevesTechShed]

After doing an upgrade I got an error on the report graphs "The reporting database is broken". I clicked 'Fix Database' but it didn't do anything, just nulls on the graphs. Then I realised my time and date were really messed up:

root@truenas[/var/db/system]# timedatectl Local time: Sun 2022-08-07 14:58:00 BST Universal time: Sun 2022-08-07 13:58:00 UTC RTC time: Sun 2012-01-01 00:42:15 Time zone: Europe/London (BST, +0100) System clock synchronized: no NTP service: n/a RTC in local TZ: no

Fixed it:

root@truenas[/var/db/system]# timedatectl set-time "2023-04-14 16:00" root@truenas[/var/db/system]# timedatectl Local time: Fri 2023-04-14 16:00:01 BST Universal time: Fri 2023-04-14 15:00:01 UTC RTC time: Fri 2023-04-14 15:00:02 Time zone: Europe/London (BST, +0100) System clock synchronized: no NTP service: n/a RTC in local TZ: no

Now my graphs have immediately started working.

 

[firewelltech]

After doing an upgrade I got an error on the report graphs "The reporting database is broken". I clicked 'Fix Database' but it didn't do anything, just nulls on the graphs. Then I realised my time and date were really messed up:

root@truenas[/var/db/system]# timedatectl Local time: Sun 2022-08-07 14:58:00 BST Universal time: Sun 2022-08-07 13:58:00 UTC RTC time: Sun 2012-01-01 00:42:15 Time zone: Europe/London (BST, +0100) System clock synchronized: no NTP service: n/a RTC in local TZ: no

Fixed it:

root@truenas[/var/db/system]# timedatectl set-time "2023-04-14 16:00" root@truenas[/var/db/system]# timedatectl Local time: Fri 2023-04-14 16:00:01 BST Universal time: Fri 2023-04-14 15:00:01 UTC RTC time: Fri 2023-04-14 15:00:02 Time zone: Europe/London (BST, +0100) System clock synchronized: no NTP service: n/a RTC in local TZ: no

Now my graphs have immediately started working.

Thanks everyone! @StevesTechShed 's suggestion solved the issue for me.

I'm on my first TrueNAS build running off of a used Supermicro X10SRA board I purchased from a third party. I neglected to check the time settings in the BIOS before I installed TrueNAS Scale. Turns out the BIOS date was several years off. Even after I corrected the time in the BIOS, the reports were still showing null. In the shell from the TrueNAS GUI, I ran sudo timedatectl set-time "[current date/time]" and reporting data immediately populated.

The X10SRA BIOS does not have a distinction for time zones. I did not try @djonas and @Aren 's suggestions above. Regardless, timedatectl now reports the correct local and UTC time, and the graphs are working, so good work everyone!