Ok I thought I had it solved but no. The error occurs Only when I try to create a new Content Type in Drupal 7, both in my local install in /var/www/html and on the remote server, which tends, I feel, to mean it's a fault in my apache system but I do not know where.
The strange thing is that no matter what I change the error remains verbatim from both systems: *Fatal error*: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16142054 bytes) in */var/www/html/mysite/includes/database/database.inc* on line *2139*
Varying php.ini memory_limit merely changes the (tried to allocate 16142054) up or down a small amount.
I have searched through the whole system, /var/log..... and everywhere else for something that sets a limit to 134217728 bytes. I do note that there is no /etc/php5/php.ini in Fedora 18 even though it is mentioned in documentation.
This error seems to be all too common, with hundreds experiencing it with php, joomla, Wordpress and Drupal. There's a bug somewhere that's been ignored for years.
Thanks Roger
Have you installed the devel module? It might help track the source of the issue.
After changing php.ini did you restart your httpd?
Earnie
On Wed, Feb 6, 2013 at 6:18 AM, Roger arelem@bigpond.com wrote:
Ok I thought I had it solved but no. The error occurs Only when I try to create a new Content Type in Drupal 7, both in my local install in /var/www/html and on the remote server, which tends, I feel, to mean it's a fault in my apache system but I do not know where.
The strange thing is that no matter what I change the error remains verbatim from both systems: *Fatal error*: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16142054 bytes) in */var/www/html/mysite/includes/database/database.inc* on line *2139*
Varying php.ini memory_limit merely changes the (tried to allocate 16142054) up or down a small amount.
I have searched through the whole system, /var/log..... and everywhere else for something that sets a limit to 134217728 bytes. I do note that there is no /etc/php5/php.ini in Fedora 18 even though it is mentioned in documentation.
This error seems to be all too common, with hundreds experiencing it with php, joomla, Wordpress and Drupal. There's a bug somewhere that's been ignored for years.
Thanks Roger
-- [ Drupal support list | http://lists.drupal.org/ ]
Go to:
/admin/reports/status/php
There's a section that tells you where the config file is loaded from. I haven't used Fedora 18 yet, but in earlier versions the php.ini file is located in /etc and then module configs are loaded from /etc/php.d
You can also bump up the memory for Drupal only by putting this in settings.php:
ini_set('memory_limit', '256M');
Jamie Holly http://www.intoxination.net http://www.hollyit.net
On 2/6/2013 6:18 AM, Roger wrote:
Ok I thought I had it solved but no. The error occurs Only when I try to create a new Content Type in Drupal 7, both in my local install in /var/www/html and on the remote server, which tends, I feel, to mean it's a fault in my apache system but I do not know where.
The strange thing is that no matter what I change the error remains verbatim from both systems: *Fatal error*: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16142054 bytes) in */var/www/html/mysite/includes/database/database.inc* on line *2139*
Varying php.ini memory_limit merely changes the (tried to allocate 16142054) up or down a small amount.
I have searched through the whole system, /var/log..... and everywhere else for something that sets a limit to 134217728 bytes. I do note that there is no /etc/php5/php.ini in Fedora 18 even though it is mentioned in documentation.
This error seems to be all too common, with hundreds experiencing it with php, joomla, Wordpress and Drupal. There's a bug somewhere that's been ignored for years.
Thanks Roger
Hi Have you tried playing with the PHP reporting levels? I'm currently working on a frozen code drupal 6 project and having the dev server using PHP 5.3 would produce a WSOD as well, so I had to add this to my settings.php
error_reporting(E_ALL & ~E_DEPRECATED);
good luck
On Wed, Feb 6, 2013 at 10:25 AM, Jamie Holly hovercrafter@earthlink.netwrote:
Go to:
/admin/reports/status/php
There's a section that tells you where the config file is loaded from. I haven't used Fedora 18 yet, but in earlier versions the php.ini file is located in /etc and then module configs are loaded from /etc/php.d
You can also bump up the memory for Drupal only by putting this in settings.php:
ini_set('memory_limit', '256M');
Jamie Holly http://www.intoxination.net http://www.hollyit.net
On 2/6/2013 6:18 AM, Roger wrote:
Ok I thought I had it solved but no. The error occurs Only when I try to create a new Content Type in Drupal 7, both in my local install in /var/www/html and on the remote server, which tends, I feel, to mean it's a fault in my apache system but I do not know where.
The strange thing is that no matter what I change the error remains verbatim from both systems: *Fatal error*: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16142054 bytes) in */var/www/html/mysite/includes/database/database.inc* on line *2139*
Varying php.ini memory_limit merely changes the (tried to allocate 16142054) up or down a small amount.
I have searched through the whole system, /var/log..... and everywhere else for something that sets a limit to 134217728 bytes. I do note that there is no /etc/php5/php.ini in Fedora 18 even though it is mentioned in documentation.
This error seems to be all too common, with hundreds experiencing it with php, joomla, Wordpress and Drupal. There's a bug somewhere that's been ignored for years.
Thanks Roger
-- [ Drupal support list | http://lists.drupal.org/ ]
I believe the problem is in the way Drupal allocates memory for php, or vice versa -but this is only a theory.
I see that the problem has existed for years and is prevalent also in Wordpress. The error message: *Fatal error*: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16142054 bytes) in */var/www/html/mysite/includes/database/database.inc* on line *2139*....Is quite curious.
It varies in file name and amount tried to allocate but remarkably the the error message: *Fatal error*: Allowed memory size of 134217728 bytes exhausted is identical in all cases, is it hard coded somewhere?
There is a workaround. Right at the very end of settings.php include one line: ini_set('memory_limit','-1'); This overrides PHP settings for the particular Drupal install.
Maybe Drupal aficionados and coders could attend to this before Drupal gets to Ver 8
This is not an error with Drupal, Wordpress or any other CMS. This is a misconfiguration of the server. You need to set your configuration files for things like PHP, MySQL and Apache. Setting an unlimited memory amount (as you are doing here) is a dangerous practice. Drupal currently handles it the proper way.
I responded yesterday with how to increase PHP's memory limit. The *Fatal error*: Allowed memory size of 134217728 bytes being identical is exactly how it's supposed to be. That means PHP's INI file is set to a memory limit of 128mb (134217728 bytes = 128mb). A lot of Drupal installations can run on that, but you can also keep adding modules, complex views, panels and a bunch of other stuff that will quickly exhaust that amount of memory. That's why it is up to each site to adjust it to whatever they need.
Jamie Holly http://www.intoxination.net http://www.hollyit.net
On 2/7/2013 1:57 AM, Roger wrote:
I believe the problem is in the way Drupal allocates memory for php, or vice versa -but this is only a theory.
I see that the problem has existed for years and is prevalent also in Wordpress. The error message: *Fatal error*: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16142054 bytes) in */var/www/html/mysite/includes/database/database.inc* on line *2139*....Is quite curious.
It varies in file name and amount tried to allocate but remarkably the the error message: *Fatal error*: Allowed memory size of 134217728 bytes exhausted is identical in all cases, is it hard coded somewhere?
There is a workaround. Right at the very end of settings.php include one line: ini_set('memory_limit','-1'); This overrides PHP settings for the particular Drupal install.
Maybe Drupal aficionados and coders could attend to this before Drupal gets to Ver 8
installations can run on that, but you can also keep adding modules, complex views, panels and a bunch of other stuff that will quickly exhaust that amount of memory. That's why it is up to each site to adjust it to whatever they need.
There could also be bugs in one of the contributed or custom modules that is causing memory demands to go beyond reasonable limits. So hitting memory limits is a good reminder to review everything.
Thanks Anoop
|-- | Zyxware Technologies | http://www.zyxware.com |-- | Be the change you wish to see in the world, M. K. Gandhi |--