Errors in the PHP log

Issue

I see errors in the PHP error log.  What do they mean?

Resolution

PHP's error log is where you will find most of the problems caused by faults in PHP, whether those faults are caused by problems in the code itself, or by the code being unable to function properly due to other issues. Problems you might find include out-of-memory errors (OOM), undefined exceptions, and so on.

While you should ensure that the PHP error log is not overloaded with messages, it's also important to ensure that errors in the production environment are logged in case problems do arise. Failure to log these errors can cripple your ability to troubleshoot an issue. In most cases, disabling NOTICE messages is enough to keep the messages down to critical notifications. To suppress these, place this code into your settings.php file:

if (isset($_ENV["AH_PRODUCTION"]) && $_ENV["AH_PRODUCTION"] == 1)
{ error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT); }

See the PHP page on error_reporting() for more examples. The method of suppression may change between PHP versions, so be sure to test if you update PHP.

Errors

• Allowed memory size of 134217728 bytes exhausted (tried to allocate 19600 bytes) in /mnt/www/html/sitename/docroot/modules/system/image.gd.inc on line 232

  This is a memory exhaustion error and will cause a page load to fail. In this case, it's occurring in the Image module, but it can occur in a number of other modules. This error most often occurs when there's too much data or logic being processed for the standard amount of memory (128 MB) to handle. This is most commonly seen on administrative pages.

  You have two possible approaches to this issue. You can troubleshoot the issue, or if you're an Acquia Cloud customer, you can increase your PHP memory limit in the UI. If you're an Acquia Cloud Enterprise customer, you can open a Support ticket. While it may be easier to just increase your PHP memory limit, this can have negative consequences. Higher memory levels can reduce the number of available PHP processes for handling uncached page requests. As a result of that, you may need to resize your server.

  Acquia recommends that you attempt to isolate the root cause of the higher memory usage, especially if the need for memory begins to exceed 192 MB or 256 MB. Beyond this point, there are usually code or configuration changes that would be more beneficial and cost-effective. If possible, determine what code or configuration changes may have taken place that could cause a jump in memory usage. This may not be the sole culprit, as many pages behave normally until a certain point.

  If you need help with troubleshooting, you may find the Help Center article on Memory consumption tracking tools to be useful.

  Look for resource-intensive queries, modules, views, or functions. Determine if anything has changed in the site's code or configuration that might have caused these alerts to suddenly appear.

Common buffer sizes

For your reference, here's a table of common large buffer sizes that you may encounter in your site's PHP error logs:

Warnings

• [pool sitename] server reached max_children setting (6), consider raising it

  This issue is commonly referred to as skip-spawning or request queueing. This occurs when a request bypasses caching and hits a web server when there are no available PHP processes to handle it. This results in the request getting queued, which means that pages may be slow to load or eventually time out, resulting in a Temporarily Unavailable error on the site and HTTP 503 errors in your request logs.

  You can address this type of issue in a number of ways. Turn on caching, which offloads requests to your load balancers instead of your web servers. You can optimize code and reduce the amount of data loading on a page to allow page requests to complete faster, reducing the likelihood of requests backing up. It's important to balance the need for memory with the number of available PHP processes. If your PHP memory limit is above 128 MB, you are limiting the number of available processes. Consider adjusting the memory limit to best accommodate your site's memory needs with the number of concurrent connections. Finally, if none of the preceding solutions are sufficient or possible, you can upsize your server(s) to gain additional memory and more PHP processes.