By talyia on

Hi all,
When I try to enter the admin area of the website at http://74.220.215.68/~leemagaz or go to any of the views pages, for example http://74.220.215.68/~leemagaz/articles, all I get is a blank screen. The error log is showing a ton of errors (I have copied some below.)
I spoke with the techs at the hosting place and they put php.ini files in all the directories... I also upgraded the memory limits in all those files. They said that it must be one of the scripts. I really have no idea what to do:(
I installed Gallery2 and the Gallery module on a test server and everything worked great. Then I installed it on the "real website" and all was fine for a while and then suddenly this happened. Should I just try dumping the gallery module? (Because that was the only thing that has changed) What else would you recommend?
I feel like crying (or hitting a punching bag)... I just don't know what to do:(

Thanks a lot,
Christine

[28-Aug-2008 14:51:57] PHP Fatal error: Out of memory (allocated 50331648) (tried to allocate 24 bytes) in /home1/leemagaz/public_html/includes/cache.inc on line 33
[28-Aug-2008 14:52:10] PHP Fatal error: Out of memory (allocated 50069504) (tried to allocate 232 bytes) in /home1/leemagaz/public_html/sites/all/modules/views/modules/taxonomy.views.inc on line 973
[28-Aug-2008 14:52:15] PHP Fatal error: Out of memory (allocated 50069504) (tried to allocate 85 bytes) in /home1/leemagaz/public_html/sites/all/modules/views/modules/taxonomy.views.inc on line 973
[28-Aug-2008 14:54:37] PHP Fatal error: Out of memory (allocated 50069504) (tried to allocate 78 bytes) in /home1/leemagaz/public_html/includes/cache.inc on line 33
[28-Aug-2008 14:54:44] PHP Fatal error: Out of memory (allocated 49807360) (tried to allocate 25 bytes) in /home1/leemagaz/public_html/sites/all/modules/views/modules/search.views.inc on line 126
[28-Aug-2008 14:54:51] PHP Fatal error: Out of memory (allocated 49545216) (tried to allocate 8192 bytes) in /home1/leemagaz/public_html/sites/all/modules/views/modules/search.views.inc on line 1
[28-Aug-2008 14:58:09] PHP Fatal error: Out of memory (allocated 50331648) (tried to allocate 24 bytes) in /home1/leemagaz/public_html/includes/cache.inc on line 33
[28-Aug-2008 14:58:13] PHP Fatal error: Out of memory (allocated 50331648) (tried to allocate 74 bytes) in /home1/leemagaz/public_html/includes/cache.inc on line 33
[28-Aug-2008 14:58:43] PHP Fatal error: Out of memory (allocated 50069504) (tried to allocate 7680 bytes) in /home1/leemagaz/public_html/sites/all/modules/views/modules/taxonomy.views.inc on line 978

⋅ Categories: Drupal 6.x

Comments

VM’s picture

VM commented

it would help to know how high you increased the memory limits ?
what version of PHP is in use ?

how many contrib modules ?
which ones ?

The above information will help those who support try and figure out what you can do based on the information you provide.

talyia’s picture

talyia commented

I have increased the memory limit to 150M in the php.ini.

PHP version 5.2.6

Contrib modules I am using:
advanced_help(for views)
bueditor
calendar
cck
contemplate
custom_breadcrumbs
date
devel (disabled)
fckeditor(disabled)
filefield
g2image
gallery
getid3
imageapi
imagefield
imce
img_assist(disabled)
lightbox2
node2node(disabled)
nodequeue
pathauto
sections(disabled)
simplegallery(disabled)
token
views

yelvington’s picture

yelvington commented

Use phpinfo() to check and see what PHP thinks it's being allocated. Sometimes people change ini files that aren't actually being read by PHP.

talyia’s picture

talyia commented

It recognizes the 150M. Is there anything else in that phpinfo that will be of any help to this thread?
One of the guys at my hosting place said that it could also be one of the scripts...?

VM’s picture

VM commented

The only thing you can do at this stage, is start disabling modules to see if there may be a situtation with one or more.

I'd start with any -dev modules. I"ve not tested G2.3 with D6 so I'm not sure how much memory that script alone would use.

talyia’s picture

talyia commented

the sites>all>modules

Would you recommend I do that?

VM’s picture

VM commented

modules can be disabled manually in the database by going into the system table and setting the status of the module to 0. removing the folder from the installation will not disable the module and will cause you other headaches because the DB will look for the modules folder.

talyia’s picture

talyia commented

Can you give me a brief set of instructions as to how to do that in the future? (Perhaps I should put the modules back in there now and then set their status to 0 as per your recommendation?)

VM’s picture

VM commented

using a tool like phpmyadmin
navigation to your system table
locate the offending modules
set their status to 0 , where their status is 1

you don't have to put the modules back to do this, only to be able to uninstall the modules properly. As it stands what you've done is left data in the DB related to those modules you deleted.

talyia’s picture

talyia commented

and it looked quite intimidating. I have been in there to create databases but that's about it. I was able to view all the tables in the dbase but how exactly do I go about setting the status of the modules to 0? It would be good to know this for the future.

One other question....the tech guy from my hosting center put a php.ini inside EVERY SINGLE directory when we were troubleshooting. Do I need to have php.ini inside EACH directory? Isn't it good enough to have just one php.ini file inside the root directory?

Thanks a lot,
Christine

talyia’s picture

talyia commented

I dumped the G2Image & Gallery modules and I am back in business...!! Oh thank GOODNESS!!!
I just wonder why the gallery module worked on my test server... but I'll leave that worry for another time.
Thank you!!! (Also, knowing about the PHPinfo is very handy for the future!!)

Going to go rest in peace now...:))
Thank you very much for replying to my cries for help so promptly... I really appreciate it:)

Christine

talyia’s picture

talyia commented

was to change the minimum cache lifetime from none to 1 minute. Could this have anything to do with it?

VM’s picture

VM commented

I don't think cache is a factor here. one or more of the modules in use may not be completely ready for prime time and may be causing a problem. The only way to start weeding that out is to start disabling modules.

if you kept a back up of your DB before you made changes (a best practice) you can roll back to that DB where the problem wasn't apparent.

lhtown’s picture

lhtown commented

One obvious difference between a test server and a live server is the number of concurrent users. Perhaps a poorly written script just couldn't handle it.

Also, on the big, bad web, you expose yourself to all sorts of nasties. It is possible that someone was doing some funny business either on purpose or inadvertently or perhaps they were trying to exploit some vulnerability either known or unknown.

mariagwyn’s picture

mariagwyn commented

I am running drupal 6.4, lots of contributed modules, PHP 5.2.5, with a 32M max allowed script.

I am getting this error repeatedly. What happens (according to my server folks) is that I incrementally bump up against my "fail count", which indicates that a "large number of memory is consumed ny the httpd processes due to which the services are getting unresponsive" (that is my server tech speaking). The result is the WSOD on site pages, and the collapse of my cPanel (which needs to be restarted every time).

This is the log confirmation my server folks send me:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
11684 nobody 18 0 51540 34m 3612 S 0 6.8 1:10.11
/usr/local/apache/bin/httpd -k start -DSSL
 9934 nobody 15 0 46784 30m 3556 S 0 5.9 1:12.58
/usr/local/apache/bin/httpd -k start -DSSL

I have had this error for a few weeks on all drupal 6.x sites. Earlier today I thought it was my Zen subtheme (due to the errors showing up...), so I disabled and am running a completely unmodified Garland while I upgrade the site. This was fine for a while, until this:

[Wed Sep 03 02:50:23 2008] [error] [client 75.175.45.213] PHP Fatal error:  Out of memory (allocated 6553600) (tried to allocate 19456 bytes) in /home/mgwynm/public_html/drupal6/sites/all/modules/cck/content.module on line 35, referer: http://mariagwyn.com/snqdev/admin/content/node/overview?page=1
[Wed Sep 03 02:50:16 2008] [error] [client 75.175.45.213] PHP Fatal error:  Out of memory (allocated 18612224) (tried to allocate 50 bytes) in /home/mgwynm/public_html/drupal6/includes/cache.inc on line 33, referer: http://mariagwyn.com/snqdev/about/ed-board/holloway
[Wed Sep 03 02:50:16 2008] [error] [client 75.175.45.213] File does not exist: /home/mgwynm/public_html/404.shtml, referer: http://mariagwyn.com/snqdev/about/ed-board/holloway
[Wed Sep 03 02:50:16 2008] [error] [client 75.175.45.213] File does not exist: /home/mgwynm/public_html/system, referer: http://mariagwyn.com/snqdev/about/ed-board/holloway
[Wed Sep 03 02:49:52 2008] [error] [client 75.175.45.213] PHP Fatal error:  Out of memory (allocated 11010048) (tried to allocate 19456 bytes) in /home/mgwynm/public_html/drupal6/modules/block/block.admin.inc on line 381
[Wed Sep 03 02:49:52 2008] [error] [client 75.175.45.213] PHP Warning:  MySQL client ran out of memory\nquery: SELECT data, created, headers, expire, serialized FROM cache WHERE cid = 'theme_registry:bluemarine' in /home/mgwynm/public_html/drupal6/includes/database.mysql.inc on line 128
[Wed Sep 03 02:49:52 2008] [error] [client 75.175.45.213] PHP Warning:  mysql_query() [<a href='function.mysql-query'>function.mysql-query</a>]: Unable to save result set in /home/mgwynm/public_html/drupal6/includes/database.mysql.inc on line 108
[Wed Sep 03 02:49:44 2008] [error] [client 75.175.45.213] PHP Fatal error:  Out of memory (allocated 15990784) (tried to allocate 77824 bytes) in /home/mgwynm/public_html/drupal6/sites/all/modules/views/modules/node.views.inc on line 271, referer: http://mariagwyn.com/snqdev/about/ed-board/holloway

Any ideas about this? I am going a bit crazy, not quite sure what to do.

talyia’s picture

talyia commented

Have you tried upping the memory at all? (Perhaps in a php.ini file in your root folder). I would increase it quite a bit more. Mine is currently at 96MB. (Which is way overkill I am sure but it doesn't hurt to at least try!) Then, as Yelvington suggested above, use phpinfo() to check and see what PHP thinks it's being allocated... to make sure it's using the memory you specified.
If this doesn't fix it, then it may indeed be one of the modules (as was the case with me)...

Christine