Dashboard cpu update 10 seconds just hangs

joe_cowboy · Jan 5, 2012, 1:59 AM

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.

johnpoz · Jan 5, 2012, 1:59 AM

"Also, if you notice your your Interface and Gateway widgets will update now along with other items in the System Infomation widget every 10 seconds now."

Ok great will give it a go then, so like the response time on gateways and interface stats, and uptime will update every 10 seconds? Notice that uptime only updates when you refresh, same with interface stats. I would assume the changes would be put in, or will the next time I git sync or install a new version will it get overwritten?

joe_cowboy · Jan 5, 2012, 2:14 AM

Well, I am not a coder for the pfSense Project. So if it is still broken in the next git sync or update then yes you will have to apply the fixes again. Unless the coders read this section. I don't know any of the guys coding on this project. Sorry..

"Notice that uptime only updates when you refresh, same with interface stats."

I will look into that and see about adding that update to the 10 second javascript loop if you want me to.

-Joe Cowboy

Cino · Jan 5, 2012, 2:42 AM

@joe_cowboy thank you for fixing this. I can comfirm its working on my box also. System Info and Cpu Graphs are displaying data now.

@jimp would it be possible to add these fixes to 2.1 in the near future? including the cpu graph? I don't mind if it stays in the deactivated folder and we have to manually move it over to use it.

johnpoz · Jan 5, 2012, 3:30 AM

ok just copied over the files and not looking like its working, I restarted the webconfigurater..

Let me refresh my browser cache,etc.

edit: ok that worked now looks like everything is working. Interface stats do update, and so does current time and so do ping times to gateways.. And uptime is working as well, before I was looking at current time and it wasn't updating unless refresh.

Looks good man - Thanks!!!

joe_cowboy · Jan 5, 2012, 3:50 AM

"Notice that uptime only updates when you refresh, same with interface stats."

Those are updating just have to wait a while to see changes sometimes. But I did make a tweak to the Up time added seconds so you can see it is updating.

put the functions.inc.php file into /usr/local/www/includes/

remove the .txt extension before uploading to the folder.

-Joe Cowboy

functions.inc.php.txt

joe_cowboy · Jan 5, 2012, 10:23 AM

Ok made another tweak to the System Information Widget for you and added Temperature. Right now just checks the first core or core 0. I will go back and add mulit core temp, CPU Graph and CPU Usage out put to the Web Gui.

coretemp.ko driver download:

AMD64 bit download file:
http://files.pfsense.org/jimp/ko-8.1/amd64/coretemp.ko

i386 download file:
http://files.pfsense.org/jimp/ko-8.1/i386/coretemp.ko

I will go ahead and post all files again here along with other files I modded. Oh yes to answere your question with git sync update you will have to reload theses fixes again still broken:

Remember to remove the .txt extension from the file.

ajax.js.txt
cpu_graphs.js.txt
cpu_graphs.widget.php.txt
functions.inc.php.txt
install_widget_fix.txt
system_information.widget.php.txt

jimp · Jan 5, 2012, 2:58 PM

joe_cowboy - You should sign up on github, fork the repo, commit those changes, and submit a pull request. Then we can import those changes directly into mainline.

joe_cowboy · Jan 5, 2012, 5:50 PM

Here is some good forum thread on getting the Tempurature drivers to work for different boards in freebsd:

http://forums.freebsd.org/showthread.php?t=882

ipmi.ko driver download:

AMD64 bit download file:
http://files.pfsense.org/jimp/ko-8.1/amd64/ipmi.ko

i386 download file:
http://files.pfsense.org/jimp/ko-8.1/i386/ipmi.ko

Another Temp driver if the coretemp.ko driver does not work. Only thing if somebody uses this driver and it uses different ODI then I will need those OID values to add as a check for for those values.

Will need to load the driver just like the other using/creating loader.conf.local in /boot

add this line: ipmi_load="YES"

Also as a check could by typing at the Console System prompt
type this at prompt: kldload ipmi
type this next at prompt: sysctl -a | grep ipmi
If not reboot pfSense box and try those two commands again and see if there are any temp or temperature values and post them here.

Hope this helps. Might need to do some more research on drivers to use and need feedback. Thanks

-Joe Cowboy

Cino · Jan 5, 2012, 7:04 PM

@joe_cowboy nice work! I totally forgot about the temp on the status information page….I had it for while but ended up using a page i created... comes in handy for my box during the summer time ;-)

joe_cowboy · Jan 6, 2012, 1:49 AM

@jimp:

joe_cowboy - You should sign up on github, fork the repo, commit those changes, and submit a pull request. Then we can import those changes directly into mainline.

Ok, did as you suggested signed up on github, commited the changes and did a submit a pull request. I also fixed it now if tempurature not availible will not display the bar graph but that does not mean the system does not support it. Have to add drivers when needed. I will need feed back on the drivers so we can make sure we can pole the sysctl temperature OIDs correctly. Right now I just check for two different ones. So please feed back so I can add the different OID temperature checks in. Unless somebody knows a list of them all that is supported with the current acpi drivers under Freebsd 8.1.

-Joe Cowboy

joe_cowboy · Jan 12, 2012, 2:10 AM

Ok the fixes and tweaks have now been Merged to master branch. You can now update via gitsync with out having to upload the patches. I will work on adding the idea of checking multiple CPU cores.

I am also want to make a package for bind97 with RRD Graphs for pfsense 2.x. Since those are already packaged for Freebsd 8.1. I have just set it up on my pfsense box works great, except the Bind RRD Graphs. Took a few head bangs but got it to work. The wide screen package needs some major fixes too. Jacks the Widget dashboard up. I know there is one guy that made a patch for the menus you have to upload by hand but it still needs some major CSS fixes.

Back on topic. Hope this helps out. Enjoy.

-Joe Cowboy

jimp · Jan 12, 2012, 12:56 AM

After I merged those changes I went through and cleaned up the widget a bit. I have no idea why the original widget creator used tags for displaying data, they were clunky and taking up too much room and I swapped them out for tags instead.

(Another bonus, you can't click in the fields and edit them anymore… that always seemed weird to me)

johnpoz · Jan 12, 2012, 3:32 AM

Joe_cowboy I want to thank you for your fixes!!!! And hopefully see more of your contributions, sounds like your part of the team now if your code has been merged into the master branch??

I am quite sure there is quite bit of clean up that could use your scrutiny.

So you mention bind – I would be very interested in anything you could do to implement bind into pfsense.. I do like unbound and the work being done in that direction... Its a great product for most scenarios where pfsense would be used.. But then again I would much rather run a full bind product for my dns where I have full control and can have duplication of dns services where one box is master and another slave, etc.

I keep wanting to move to the full bind running on my pfsense - but since its not actually a package its kind of a road block...

I have munin running giving me stats on my unbound running on pfsense - it would be sweet as hell to see full bind as an option with stats in an rrd, etc.. Is that somthing your interested in doing??? I would sign up for sure as your #1 beta tester ;)