PHP Cache Memory

[CranialBlaze]

This seemed like the most relevant place to put this.

Got a joomla site and a few weeks ago it gave some warning about the php cache memory being too high (stupid i know) anyway our server admin decreased it, problem is with this low limit I am unable to extract zip files within the CMS, well above about 1.5mb, I had completely forgotten that we had made the change and I need to run a pretty important and BIG upgrade on the site but with this memory limit the installer is unable to extract some of its zip files.

Asked him about it Tuesday and he remembered the cache memory that had been changed and said its most likely the cause. I have been through the php.ini about 5 times already, online and off and cannot for the life of me find where to increase this limit and our admins been ignoring me since then.

Could anyone tell me where I need to change this memory limit to get around my problem.

Thanks in advance...

 

[koffiejunkie]

Exactly what was the error, and exactly which setting did he change?

The two that relates to uploads are:

upload_max_filesize = 2M
post_max_size = 8M

depending on how Joomla handles the upload. It may also be affected by your memory_limit (the maximum amount of memory a script may consume) but be careful you don't set this too high.

 

[CranialBlaze]

Exactly what was the error, and exactly which setting did he change?

The two that relates to uploads are:

upload_max_filesize = 2M
post_max_size = 8M

depending on how Joomla handles the upload. It may also be affected by your memory_limit (the maximum amount of memory a script may consume) but be careful you don't set this too high.

Thats the problem, I cannot remember as it was done over a month ago and we only saw the problems this week. When I mentioned it to him he said we need to increase the PHP Cache Memory as we had decreased that.

UMF and PMS are set at 30mb and Mem limit is 128mb yet any zip file with an uncompressed size of over 2mb fails and the error suggested we set this limit to 2mb and I have been up and down that ini file and cannot find any valid reference to cache or memory or anything of 2M or 2MB.

I am very green on this, been workign with this server only a few weeks and putty still pretty new to me, pretty much grasp the basics, thank goodness I used DOS back in the day.

 

[koffiejunkie]

Depending on how your box is configured, it may be that it has more than one php.ini file and you're not editing the right one. Put a phpinfo in your document root, and load that via a browser

<?php echo phpinfo(); ?>

Compare the settings there.

 

[CranialBlaze]

Depending on how your box is configured, it may be that it has more than one php.ini file and you're not editing the right one. Put a phpinfo in your document root, and load that via a browser

<?php echo phpinfo(); ?>

Compare the settings there.

Checked within joomla, it actually which ini file is being loaded, keep forgetting where it is so its actually nice to have that.
So I do know I am working in the rite one, besides I have made changes to it myself before and all my changes are in their too.

 

[koffiejunkie]

Ask your server admin what he changed.

 

[CranialBlaze]

Ask your server admin what he changed.

If only that worked, has not been replying in 4 days, hence my jump to an open community.

 

[koffiejunkie]

Well, there's no such thing as a "php cache memory" setting, and your problem is rather low on details. Have you looked at your logs? What happens when you try to upload? If error_reporting is set to something sensible, it will give you an error when the update fails.

 

[CranialBlaze]

Well, there's no such thing as a "php cache memory" setting, and your problem is rather low on details. Have you looked at your logs? What happens when you try to upload? If error_reporting is set to something sensible, it will give you an error when the update fails.

Mostly low due my lack of knowing what I am talking about, should be quite obvious by the "php cache memory" still am not able to get through to the admin and the only cache I find bellow 2m in the php information is the apc set at 1m.

Error reporting is set to E_ALL & ~E_NOTICE, I enabled logging and defined the log file I know the path is correct but nothings being logged and I know the jumble sale this site is so I find it hard to believe nothing is being logged so ya.

Guess I will have to wait until he eventually decides to reply, no point tying to find a new admin seeing as he is probably just as unlikely to know what I am talking about.
All i know is its messing with my ability to extract not so large zip files and every memory setting I fund (apc the exception) is 30mb or greater.

Thanks anyway guys.

 

[koffiejunkie]

The error log will be the apache error log. You need to do at least a graceful apache restart after changing the PHP settings, otherwise you'll still be running with the old settings. Make a phpinfo.php to check:

<?php
phpinfo();
?>

~E_NOTICE means "don't show E_NOTICE." Change iet to just E_ALL so that you see everything. Anything that's a notice becomes a warning in future versions of PHP, and eventually a fatal error, so it's worth paying attention to these too.

Look in your vhost configuration, there should be a line starting with "ErrorLog" - if you have shell access to the server, ssh into it and run (substitute your error log):

tail -f /path/to/error_log

Tail follows the log and will print out any new lines added to it. Now try the upload again. It should give you some warning or error when it fails.

 

[CranialBlaze]

The error log will be the apache error log. You need to do at least a graceful apache restart after changing the PHP settings, otherwise you'll still be running with the old settings. Make a phpinfo.php to check:

<?php
phpinfo();
?>

~E_NOTICE means "don't show E_NOTICE." Change iet to just E_ALL so that you see everything. Anything that's a notice becomes a warning in future versions of PHP, and eventually a fatal error, so it's worth paying attention to these too.

Look in your vhost configuration, there should be a line starting with "ErrorLog" - if you have shell access to the server, ssh into it and run (substitute your error log):

tail -f /path/to/error_log

Tail follows the log and will print out any new lines added to it. Now try the upload again. It should give you some warning or error when it fails.

Restart is on the short list of things I know how to do, my skill level sits around the tinkering level. At least the more I use it the better acquainted I get and googles a good help most of the time.

Tail worked but the log only has 1 line in it and I tried uploading the zip in Joomla twice for good measure and the only thing is a warning from a config file from at just after 4pm. Its most likely as the problem is within joomla and not on the server itself, I can extract the archives fine via ssh which normally would be my way around this but as the component I need to install runs a 2 tier install it needs to extract the 2nd set of archive files itself in order to complete. Even set joomlas reporting to max and nothing, so whatever it is not serious enough for it to actually error beyond "Unable to open archive"

Starting to contemplate shooting my server admin, still looking for the vhosts file too. Need to fix a mistake he made with the rewrite string. Times like this I miss my WHM CPanel, sometime a GUI is useful.

 

[koffiejunkie]

Its most likely as the problem is within joomla and not on the server itself

Probably