Dashboard cpu update 10 seconds just hangs

johnpoz · Dec 20, 2011, 4:24 PM

Ok so noticed my dashboard cpu usage is not updating.

I just ran a gitsync this morning, and even rebooted after

Currently running
2.1-DEVELOPMENT (i386)
built on Fri Nov 25 17:45:38 EST 2011
FreeBSD 8.1-RELEASE-p6

I have flushed my cache, tried a different browser, tried different themes. Found this thread
http://forum.pfsense.org/index.php/topic,41768.msg218637.html#msg218637

That talks about sajax.js, I don't have that file only ajax.js

Just sits there – but Diagnostics: System Activity works fine, and the processor graph in RRD is working as well.. Just the dashboard hangs. I have tried removing and re adding the widget and that produced this crash report, which I submitted

PHP Errors:
[20-Dec-2011 10:18:03] PHP Fatal error: Call to undefined function get_uptime() in /usr/local/www/widgets/widgets/system_information.widget.php on line 160

Which does not seem related to cpu usage - but could be related? I think that crash was not quite right either, since the uptime on the dashboard seems to be working to me.

tix · Dec 23, 2011, 6:21 AM

I'm also having the same problem after the update. It isn't CPU utilization for me as I'm at 0% most of the time. Not that big of an issue as the RRD graphs work as you said.

johnpoz · Dec 23, 2011, 1:43 PM

Yeah I agree its not that big of a deal, other than hey something broke it because it use to work ;)

tix · Dec 23, 2011, 5:32 PM

I just did a clean install of 2.0, upgraded to 2.0.1 and then sync'd to github and the dashboard works. Hmm, going to do some further digging and see why my existing install broke….....

But it is something that was/is working and breaks on upgrade. LOL

johnpoz · Dec 23, 2011, 6:29 PM

Nice clean install with gitsync from 2.01 might be a good project for next week since off, etc.

but everything seems to be working great! Hate to do something for no reason, cpu widget not working needs to be fixed - but not really a priority type item. More of curiosity sort of thing on why is it not working ;)

jimp · Dec 27, 2011, 4:25 PM

Would probably be easy for someone familiar with debugging web apps to spot if you had firebug or something similar running and watching for errors.

Last time I saw that it was an old/invalid javascript file that was being included (sajax.js) but I haven't seen it happen since.

2.1 also includes various changes moving from Prototype to jQuery so there is potential for issues there as well.

Comparing the output of:

find /usr/local/www/

Between a working and non-working box would also be useful.

johnpoz · Dec 27, 2011, 7:04 PM

here is output from mine that doesn't work, now just need one from one that does ;)

list.txt

Cino · Dec 29, 2011, 4:36 PM

i was going to post this issue awhile ago (thinking it started almost 2 months ago) but was going to wait till 2.1 is final. i think it has to do with jQuery because it has broken a few other things in 2.1.

johnpoz · Dec 29, 2011, 7:34 PM

Cino if that was the case, then why this statement from tix

"I just did a clean install of 2.0, upgraded to 2.0.1 and then sync'd to github and the dashboard works."

Would seem to me if something was broken in the code it should not work no matter how you got to the code - be it multiple git syncs or fresh install, etc.

If works from clean install and then gitsync – what happened, and how to fix so don't have to do a clean install, etc.

jimp · Dec 29, 2011, 8:12 PM

If it works on a clean install, but not an upgrade, there must be a file still on your box under /usr/local/www/ somewhere that is getting read in (most likely some JS) and conflicting.

You could try to rm -rf /usr/local/www and then do a gitsync, but that's a bit extreme and wouldn't really help solve the problem in the long run.

johnpoz · Dec 29, 2011, 8:39 PM

well I posted the contents of my www folder – anything jump out at you?

Maybe we could get cino to post the content of his.

jimp · Dec 29, 2011, 8:40 PM

Nothing jumped out, but I haven't really paid close attention to what the new files are since the jQuery changes.

Cino · Dec 30, 2011, 12:02 AM

i have too many packages and custom stuff to wipe out everything.. I did remove the following folders: widgets, classes, javascript with now luck. Should had mention this before, but cpu_graphs.widget.php stop working the same time system information widget stopped.

chpalmer · Dec 30, 2011, 8:52 AM

I have two boxes in particular…

2.0.1-RELEASE (i386)
built on Mon Dec 12 18:24:17 EST 2011
FreeBSD 8.1-RELEASE-p6 No Gitsync

CPU graph works.

2.1-DEVELOPMENT (i386)
built on Tue Sep 13 17:28:43 EDT 2011
FreeBSD 8.1-RELEASE-p4 Recent Gitsync

CPU graph doesn't work.

Both with widescreen, pfblocker, siproxd, filemanager packages.

In case it helps...

joe_cowboy · Jan 2, 2012, 9:08 AM

OK guys hopes this helps I fixed the 2.1 Development Issue CPU Usage and other widgets not updating:

Testing it right now on couple different boxes with:

2.1-DEVELOPMENT (i386)
built on Fri Nov 25 14:30:42 EST 2011

FreeBSD 8.1-RELEASE-p6

Remove the .txt extension from the files and put them in the proper directories stated in the install_widget_fix.txt file.

Fixed Javascript errors tested on IE 7, IE 9, Firefox 8.0, Safari, Chrome. Don't worry if it stays at 100% load has to do with how they figure load using clock cycles average. It will go back down once Web Gui fully loaded or might take a bit sometimes. It takes 10 seconds to update screen. They use the same exact php code as LCDproc uses to figure CPU Usage.

ajax.js.txt
cpu_graphs.js.txt
cpu_graphs.widget.php.txt
install_widget_fix.txt

chpalmer · Jan 2, 2012, 9:17 AM

Trying it now and seems to be working… Thanks! :)

joe_cowboy · Jan 2, 2012, 9:21 AM

Glad I can be of some help. ;D

jimp · Jan 4, 2012, 7:35 PM

I didn't realize it was the cpu_graphs widget, I thought it was the cpu bar in the system info widget (though I suppose one could have hurt the other)

the cpu_graphs widget was removed a while back due to it being inaccurate on multi-core systems, so it does not exist in 2.1 proper.

johnpoz · Jan 4, 2012, 7:45 PM

Yeah not the graph, its the little bar for me – I posted a screenshot showing it.

It just sits that at updating in 10 seconds -- taunting!!

As already stated the CPU graph in RRD is working, etc. And System Activity under Diag works fine as well showing cpu usage -- just the stupid little bar on the systeminfo widget atleast for me that is what the problem is.

I had grabbed the files he tweaked, but was not ready to test out his few changes - checked diff of his files vs ones on my system, mainly because the one file was in a folder called disabled, and was not ready to pull that out, etc.

joe_cowboy · Jan 5, 2012, 1:59 AM

@johnpoz:

Yeah not the graph, its the little bar for me – I posted a screenshot showing it.

It just sits that at updating in 10 seconds -- taunting!!

As already stated the CPU graph in RRD is working, etc. And System Activity under Diag works fine as well showing cpu usage -- just the stupid little bar on the systeminfo widget atleast for me that is what the problem is.

I had grabbed the files he tweaked, but was not ready to test out his few changes - checked diff of his files vs ones on my system, mainly because the one file was in a folder called disabled, and was not ready to pull that out, etc.

The CPU Graph Widget uses the same code as the CPU Usage bar… They both work. The PHP code is the same as the PHP code that is used in LCDproc CPU usage too. Only reason I added the CPU Graph widget code is because I fixed a javascript error in it too. Also, if you notice your your Interface and Gateway widgets will update along with other items in the System Infomation widget every 10 seconds now. So the fix was not just for the CPU Graph widget it was for a few widgets that use the same javascript to update the web gui output.