Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Disk and network reporting pages do not load

Description

Steps to reproduce:
1. Open reporting page
2. Change report type dropdown to Network or Disk

Expected outcome:
Network and disk graphs display as in previous versions of TrueNAS

Actual outcome:
Network and disk graphs do not load. They stay as blank boxes.
Network page says "Statistics for interface" with a template string.
Unselecting devices or metrics on the disk page does not allow the UI to load

Session ID: 50852337-42ff-eff8-5f15-e0a13fa08e63

Problem/Justification

None

Impact

None

Attachments

1
  • 09 Apr 2025, 01:47 AM

Activity

Show:

Jonathan Schram5 days ago

I spoke too soon, tried one more time and managed to get the network screen to break.

 

If I run the command you gave me (I’m using a bond interface called bond1), it displays a lot of data.

 

Interestingly enough, I have the web UI open in two different Chrome tabs and one displays the network graphs without issue, the other is displayed as above. On the tab where the network graph is broken, I can’t find any way to get it to work again. I’ve tried changing graphs, navigating to other pages (apps, network, datasets, etc.). When doing the same on the functional tab, everything continues to work even when I do the same steps. Really seems like the worst kind of issue to debug. I’ll keep everything the way it is in case there is any information I can provide while I am seeing the problem.

Jonathan Schram5 days ago

Okay I’ve rebooted a handful of times and the reproducibility is much worse than I thought. I’ve had times where all the graphs work just fine, I’ve had times where the transfer rate and temperature of disks won’t show, and times where only the transfer rate will show. I couldn’t reproduce the issue with the network graph. However, I am able to confirm that when none of the disk graphs show, there are no errors or warnings in the developer console.

 

And across all of these reboots, I never saw any issues with the CPU, memory, system, UPS, or ZFS graphs.

Jonathan Schram5 days ago

Hi Ievgen, thanks for the response.

 

I don’t see any errors in the developer console, but I see a lot of warnings such as these:

[Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] Added non-passive event listener to a scroll-blocking <some> event. Consider marking event handler as 'passive' to make the page more responsive. See <URL> [Violation] 'setTimeout' handler took <N>ms [Violation] 'setTimeout' handler took <N>ms [Violation] 'setTimeout' handler took <N>ms [Violation] 'setTimeout' handler took <N>ms [Violation] 'setTimeout' handler took <N>ms polyfills-4GSV3QYD.js:1 [Violation] 'setTimeout' handler took 161ms polyfills-4GSV3QYD.js:1 [Violation] 'setTimeout' handler took 108ms polyfills-4GSV3QYD.js:1 [Violation] 'setTimeout' handler took 206ms polyfills-4GSV3QYD.js:1 [Violation] 'setTimeout' handler took 100ms polyfills-4GSV3QYD.js:1 [Violation] 'setTimeout' handler took 97ms

I see them on the pages that are working so I’m guessing those are unrelated to the issue.

 

As for the other troubleshooting step, I had reverted to TrueNAS Scale 24.10.2 so I could get the graphs back. When I switched to 24.10.2.1 just now, the network graph is working normally, and on the Disks page, only the disk temperature is missing (transfer rate looks fine). When I log out and log back in again, the same graphs have the same problems, so I wonder if the fact that I did a reboot is causing the change. I’ll reboot a couple times to see if the network page ever breaks.

Ievgen Stepanovychlast week

Could you check if you have any errors in your browser console on these pages?

Please also try this in shell:

midclt call reporting.netdata_get_data ' [ { "name": "interface", "identifier": "ens1" } ]' '{ "start": 1744106114, "end": 1744109714 }' | jq

replacing ens1 with the name of your network interface and see if data is returned.

Thanks.

Bonnie Follweilerlast week

Thank you for your ticket submission .
I have moved this ticket into our queue to review now.
An engineering representative will update with any further questions or details in the near future.

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

More fields

Katalon Platform

Created April 5, 2025 at 5:28 PM
Updated 5 days ago