SteelSeries graphs not consistent

Mark - help me here - I went to JPGraph.net and the version there is 4.2.0 which is the one I was using. Am I missing something?

Thanks

Craig

AFAIK 4.2.0 is the latest version.

OK - will try again in the morning.

Thanks

Sorry, but I was pretty sure when I loaded up your test page it didn’t show as version 4.2.0 - I went and checked which version I was using before I posted (which is 4.2.0)

OK, official frustration… #-o

I redid everything and am getting the same results. I am using JPgraph-4.2.0 and wxgraphs off broadstairs site dated 11/20/2016. When the SteelSeries loads, it look fine but the graphs do not resolve consistently, and there are server errors. See attachment. If I call directly any graph, it is created and resolves fine.

Errors start with 'cannot allocate memory:couldn’t create child…

Any thoughts?

Thanks

Craig


Clutching at straws let’s see if there are any php errors, add this line right at the top of one of the graph scripts

error_reporting(E_ALL);

and then run that script

If niko’s suggestion doesn’t throw any light on this, then it sounds like the php fpm (if you are using fpm) needs some more memory allocating to it to me.
I set my script memory limit to 128M which I think may be the default in 7.0?..

memory_limit = 128M

http://php.net/memory-limit

Mark, if you look back at the chart in reply #8 it appears he’s hitting a 1 GB limit :?

Hmm, 1GB is an awful lot of memory, wonder if it is a shared process on a shared hosting server rather than each client getting their own process.

Niko - Mark - put line of code into script and ran it - there were no errors in the server logs and graph resolved properly.

Craig


Yeah, I think there’s something funky on the server side. Many users have installed this graph set over time, in the gauges or standalone, and Craig’s the first one that I can recall getting this issue :frowning:

It would be interesting to see what limits are set in php.ini but I don’t know if Craig has access to that.

Craig

Try running this script:

<?php
print_r(ini_get('memory_limit'));
?>

Niko -Hope I did this correctly - created a new php file in Dreamweaver and put it on the server and call the file - the return was 256M with no errors.

Craig

Yep, that’s OK. No red flag there unfortunately :frowning:

OK - thanks - just sent you a PM.

It’s a problem with jpgraph in general, not specific to the wxgraphs. I set up a test page on Craig’s server using five of the jpgraph examples and it has the same problem :?

Niko - thank you. I also noticed that they had throttled me back since after numerous tests and attempts with high memory usage, so I think it is a pre-programmed reaction that lasts for maybe 24 hours…

Craig

N - I think I have all the pointers going to the correct folders. There are only 3 or 4 places to configure, right?

Craig

I don’t see that as a problem. I think it may be worth trying a different jpgraph version.

I just saw this and decided to try jpgraph 4.2.0 with my copy of the graphs on PHP 7 and it works fine both locally here on my own server and on my live website. So yes the issue is as has been suggested.

Stuart