Fed up with Drupal 7 Fatal error: Allowed memory size....
My heart just sank into oblivion. I am sooooo sad and fed up with the latest and incessant: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 9331811 bytes) in ...... when I try to add a Content Type in Drupal 7. Months of research, lots of help from this list community and carefully inspecting files apparently achieved nothing. I think I solved it on Fedora 18 on a local copy, do not know how though, but just now, working on the server in my local Fedora 18 and testing on Fedora 16 and Ubuntu 12.10 all with latest updates, except for F16 which is end of life but a good static test platform because it does not have the latest php updates. All of them give the same error. For heavens sake can't the Drupal experts please do something to stop trying to allocate inappropriate bytes, or at least create a comprehensive easy to work through tutorial about this ghastly debilitating error, highlighting all of the reasons it occurs and how to fix it. There's a lot of pages about it on the web but it's still not permanently solved and it's unfair that we have to search long and hard to find possible answers. After all said and done, it's probably a php fault or a php/apache fault and not Drupal at all, so please Drupal move to Ruby with it's inherent security and alternative web servers and get away from php entirely. My apologies for this very disheartened rant. I do not wish to offend those who love and understand php but from what I've read lately, it is old hat nowadays and struggling to keep up appearances, at least that's my take on it after a lot of reading on pro's and con's. Apologies for a convoluted rant, I'm in a hellava bind and not thinking straight at the moment. Roger
<snip> My heart just sank into oblivion. I am sooooo sad and fed up with the latest and incessant: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 9331811 bytes) in ...... </snip> Hi again. Ok so I can't create a content type due to Fatal error messages, but maybe I can make a view and display that in an existing page or block. Problem is I have png images in a number of directories in the /defaults/files/images/Seminar database. Images are png and jpg. I have no idea how to tell a view how to get images from certain directories. For some reason the view I create gets images only from the /images directory and no other. I could not even figure out how to filter on directory names. If it can be solved how to get only png images from different directories /images/Seminar/2011, /2012, /2013, /2014 file tree this would be of great assistance and maybe bail me out temporarily.
Thank you for any assistance, it will be greatly appreciated. Roger
just jumping in here....Can you explain what you're trying to achive, why are you trying to access the images directly? have you increase the memory limit in the php settings? Idan On Thu, Apr 4, 2013 at 10:08 AM, Roger <arelem@bigpond.com> wrote:
<snip> My heart just sank into oblivion. I am sooooo sad and fed up with the latest and incessant: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 9331811 bytes) in ...... </snip> Hi again. Ok so I can't create a content type due to Fatal error messages, but maybe I can make a view and display that in an existing page or block. Problem is I have png images in a number of directories in the /defaults/files/images/Seminar database. Images are png and jpg. I have no idea how to tell a view how to get images from certain directories. For some reason the view I create gets images only from the /images directory and no other. I could not even figure out how to filter on directory names. If it can be solved how to get only png images from different directories /images/Seminar/2011, /2012, /2013, /2014 file tree this would be of great assistance and maybe bail me out temporarily.
Thank you for any assistance, it will be greatly appreciated. Roger -- [ Drupal support list | http://lists.drupal.org/ ]
On 04/04/13 15:08, Roger wrote:
<snip> My heart just sank into oblivion. I am sooooo sad and fed up with the latest and incessant: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 9331811 bytes) in ...... </snip> Hi again. Ok so I can't create a content type due to Fatal error messages, but maybe I can make a view and display that in an existing page or block. Problem is I have png images in a number of directories in the /defaults/files/images/Seminar database. Images are png and jpg. I have no idea how to tell a view how to get images from certain directories. For some reason the view I create gets images only from the /images directory and no other. I could not even figure out how to filter on directory names. If it can be solved how to get only png images from different directories /images/Seminar/2011, /2012, /2013, /2014 file tree this would be of great assistance and maybe bail me out temporarily.
Thank you for any assistance, it will be greatly appreciated. Roger
Unless I were developing Drupal core or modules or themes I'd not touch PHP5.4. The recommended release of PHP for D7 is 5.3, and I'd stay right there for hosting. If you're deploying to Fedora for production, well I know a lot of folk do, but I think it's silly for these reasons: 1. Despite what advocates say, Fedora isn't a well-tested product. It's built from the latest versions of everything, and while their developers say they're stable, in reality they are most likely to contain serious bugs. It's not unknown for Fedora kernels to just not boot on some hardware, for example If you still think that upstream's claim that their software is stable and bug-free, just consider your experience with D7, and see how many releases of it there have been. 2. Any release of Fedora won't be around for very long. I think F18 expires shortly after F20's release, is that right? 3. I have some experiences of broken Fedora systems. Right now, I have two F17 systems that won't boot. Well, I did until I deleted one yesterday. One is broken because it started out as F7 or thereabouts and as it's been upgraded from time to time it seems to have become flakey. Dramatic changes to a (non-standard) filesystem layout and replacements to init/sysinit didn't help. I'd not want those problems on a production money-earning server. btw Much the same applies to Ubuntu and friends, LongLife editions excluded. I use Debian in preference to Ubuntu - _all_ its software is supported - although its release cycle is shorter than Red Hat's. I use and recommend CentOS, CentOS is the latest and will be around for years, as long as Red Hat supports RHEL6. Since you're experienced with Fedora, I suggest you use CentOS too. CentOS6 has PHP 5.3.3. I have D7 running (for testing purposes) on several CentOS and Debian systems, and have too few problems to make me fed up with it. Your memory problems could be caused by Drupal or by PHP, but your own configuration is the most probable cause, and more so should you test on CentOS6 and the latest PHP 5.3. These days you can easily run up any OS you like (and are licensed for!) inside a virtual machine, so running CentOS6 doesn't preclude your use of Fedora on your desktop if that's what you prefer. To find out what your webserver is doing, you can use the strace command. Something like this: strace -f -e trace=file \ $(ps xa | awk '/httpd/ {print "-p " $1}') -o /tmp/apache "-e" tells strace what system calls to track. Probably, you want open,access rather than file. That should tell you what directories it's accessing. btw selinux can give grief including stuff magically not working. Probably not your memory problems, but it can prevent httpd from accessing files Linux permissions say it can, and it also limits TCP and UDP access.
As previously stated, PHP 5.4 and Drupal isn't the best combination. 7.22, which just came out last night, addresses some problems: http://drupal.org/drupal-7.22-release-notes Another thing to check is if you're running a contrib cache solution, like memcache. Make sure that is actually working, or you can have problems like this. Creating content types is pretty intensive. It does a full cache clear, including menu rebuild. If you have a bunch of modules on your installation, or even one problem module, that can start causing out of memory errors. I've got a Drupal 7 site running with 60 contrib modules and about a dozen custom modules. I got the memory limit set to 128mb and never run out of memory. This is on CentOS6 and PHP 5.3.23. There are also countless other Drupal 7 sites running out there with no problem. But you can pretty much break anything with the wrong configurations and/or modules. For the images, if you aren't letting Drupal manage them, then Drupal doesn't know about them. You can try overriding the output of fields in views and use some tokens to replace values, but you really aren't giving enough information here. Also, you can do custom view templates and run a bit of logic in there to grab the fields. Look under the advanced part of your view. Jamie Holly http://www.intoxination.net http://www.hollyit.net On 4/4/2013 3:08 AM, Roger wrote:
<snip> My heart just sank into oblivion. I am sooooo sad and fed up with the latest and incessant: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 9331811 bytes) in ...... </snip> Hi again. Ok so I can't create a content type due to Fatal error messages, but maybe I can make a view and display that in an existing page or block. Problem is I have png images in a number of directories in the /defaults/files/images/Seminar database. Images are png and jpg. I have no idea how to tell a view how to get images from certain directories. For some reason the view I create gets images only from the /images directory and no other. I could not even figure out how to filter on directory names. If it can be solved how to get only png images from different directories /images/Seminar/2011, /2012, /2013, /2014 file tree this would be of great assistance and maybe bail me out temporarily.
Thank you for any assistance, it will be greatly appreciated. Roger
On 05/04/13 00:28, Jamie Holly wrote:
I've got a Drupal 7 site running with 60 contrib modules and about a dozen custom modules. I got the memory limit set to 128mb and never run out of memory. This is on CentOS6 and PHP 5.3.23. There are also countless other Drupal 7 sites running out there with no problem. But you can pretty much break anything with the wrong configurations and/or modules.
In contrast, I just created a site with a few modules and themes, and without adding so much as any new content type or content, I did get memory problems I'm using CentOS 6. PHP 5.3.3 with all the latest relevant updates. It happened the first day drupal 7.22 was available and it appeared to be provoked by Jackson. Not having persuaded myself I actually want Jackson, it was easy to dispense with it. I do have the memory limit set to 128Mbytes. However, this isn't Roger's problem.
Memory limits of 128mb or more is not uncommon. It's even stated in the online documentation: A PHP memory limit of 32MB is the minimum requirement for Drupal 7 (16MB for Drupal 6), and 64MB is recommended. Some sites may need more than 64MB if they are using certain contributed modules such as Views and Panels. Memory limits of 128MB and higher are not unusual. There are several techniques to increase the PHP memory limit and you only need to use one of them. The right one for you depends on your system configuration. http://drupal.org/node/207036 Views and Panels are heavy modules. That's the price we pay for the ease in site building they provide. The other option is to not use them and go with custom code to generate your content and displays. Any site I build I evaluate what needs to be done and what will need to be done in the future before installing Views and/or Panels. Of course that's not an easy option for people not familiar with Drupal development. As far as Views, it will get better in Drupal 8, since it is going into core and will get a lot more attention from the development side as well as tighter integration into Drupal overall. Jamie Holly http://www.intoxination.net http://www.hollyit.net On 4/5/2013 2:26 AM, John Summerfield wrote:
On 05/04/13 00:28, Jamie Holly wrote:
I've got a Drupal 7 site running with 60 contrib modules and about a dozen custom modules. I got the memory limit set to 128mb and never run out of memory. This is on CentOS6 and PHP 5.3.23. There are also countless other Drupal 7 sites running out there with no problem. But you can pretty much break anything with the wrong configurations and/or modules.
In contrast, I just created a site with a few modules and themes, and without adding so much as any new content type or content, I did get memory problems
I'm using CentOS 6. PHP 5.3.3 with all the latest relevant updates. It happened the first day drupal 7.22 was available and it appeared to be provoked by Jackson. Not having persuaded myself I actually want Jackson, it was easy to dispense with it. I do have the memory limit set to 128Mbytes.
However, this isn't Roger's problem.
On 05/04/13 23:44, Jamie Holly wrote:
Memory limits of 128mb or more is not uncommon. It's even stated in the online documentation:
A PHP memory limit of 32MB is the minimum requirement for Drupal 7 (16MB for Drupal 6), and 64MB is recommended. Some sites may need more than 64MB if they are using certain contributed modules such as Views and Panels. Memory limits of 128MB and higher are not unusual. There are several techniques to increase the PHP memory limit and you only need to use one of them. The right one for you depends on your system configuration.
I know that, and that is why I was so surprised. A handful of extra modules. It only happened when Jackson was the active theme.
participants (4)
-
Idan Arbel -
Jamie Holly -
John Summerfield -
Roger