CPU stats not working in 12.0 U4

[Vertigo 7]

Muh threads!

Seriously though, doesn't look like the dashboard is updating. Utilization % remains constant, obviously no per thread util or temp readings are displayed... and 49 threads?? Doesn't look like RAM usage is changing as well.

 

[Vertigo 7]

Disregard RAM not updating. it is, just slowly. but CPU is dead.

 

[c77dk]

Seeing the same (but haven't gone deeper for a cause yet)

 

[sretalla]

I can confirm also on my test system... seems a bug.

 

[Basil Hendroff]

+1

 

[Alecmascot]

+1

 

[emk2203]

+1. To put an end to further +1s: I would say it concerns everyone.

 

[morganL]

Can someone volunteer to report the bug and work with engineering to verify, then post the bug link here.

I assume no-one has it working properly?

 

[Vertigo 7]

Can someone volunteer to report the bug and work with engineering to verify, then post the bug link here.

I assume no-one has it working properly?

I've been trying to loginto Jira but I've been having nothing but problems. I'll be happy to work with whomever but is there an alternate means to file a report or can I pass over logs and have the engineer log it in my stead?

 

[revengineer]

[NAS-110860] CPU widget not working in 12.0-U4 - iX - Bug Tracker (Jira) (ixsystems.com)

 

[ThreeDee]

would this still work to "fix"?

Reddit - Dive into anything

www.reddit.com

 

[Vertigo 7]

i don't think so. looks like that was for a different issue that broke network interfaces, which may have impacted other things on the dashboard as well. This seems to be isolated to the cpu stats only.

 

[ThreeDee]

That might be the wrong link then .. but it was a similar fix when an update broke CPU and Memory widgets not too long ago .. I'll keep digging around

 

[ThreeDee]

Reddit - Dive into anything

www.reddit.com

if you really gotta have the fix NOW!!

 

[Dwarf Cavendish]

+1

And also something that could have easily been spotted...?

 

[revengineer]

I did a hex compare of the patch file posted on reddit and it seems to apply the first commit but not the second. Maybe this would be sufficient in the interim. I am waiting for any developers' updates next week. Hopefully we do not have to wait until August for this fix when U5 is scheduled to be released.

EDIT: Changed my mind, installed the patched file after verifying the patched region, and it works fine. It may not be a perfect or final fix, but it does the job for now. The file posted on reddit included an additional byte at the end which does not seem necessary, so I removed that. I am attaching this version here. If you decide to try it, I suggest that you rename the original file in case you want to revert the patch.

EDIT 2: Given some are having issues installing this, here are the steps:

1. Unzip the archive and transfer main.7827c30e6733c013d061.js.patched to /usr/local/www/webui (this should be a BINARY transfer)
2. Rename original file: mv main.7827c30e6733c013d061.js main.7827c30e6733c013d061.js.orig
3. Rename patch: mv main.7827c30e6733c013d061.js.patched main.7827c30e6733c013d061.js

 

[ChrisRM]

+1

 

[Dwarf Cavendish]

The CPU temperature report is also not working for me, btw.

 

[jlpellet]

Checked bug tracker earlier today & it shows resolved to be addressed in U5, currently scheduled for early August.

 

[sretalla]

The fix posted by @revengineer works and doesn't need a reboot.

The CPU status on the dashboard is a "nice to have", so you should weigh-up the real need and implement the temporary fix if you really can't live without it.