By mago-2 on

Hi there.

I've installed a new drupal, started creating content, added a couple of known modules and everything was going fine.

Then i installed the user_register_notify module (user_register_notify-6.x-1.10.tar) and BOOM, the modules page was not found.

I searched drupal.org about this and apparently it's due to lack of memory on the server. Some people said it had to do with the memory_limit value in php.ini. They also said that in order to customize php.ini in Dreamhost (i'm using dreamhost) you had to recompile php.

Knowing that the recompilation process was going to take at least a couple of hours, i deleted the user_register_notify module and everything went back to normal.

The memory limit issue might arise again in the future so in order to know what to do when it shows up again i ask you guys:

Is the recompilation of php the only way out of this? I did a phpinfo() and my server says: memory_limit 90M. Isn't that enough? Why did drupal exploded after i installed that little module?

Thanks for your time and all pointers are welcome.

⋅ Categories: Drupal 6.x

Comments

LuisCypher’s picture

LuisCypher commented

Dreamhost has had a lot of problems over the last few days my site goes down every day at the same time , so it could be an overloaded server. Check the status in the dreamost web-panel and read the comments of the status logs.
Servers having problems are associated with "Homie" presently "Galactus" is down

You shouldn't have to modify the memory limit , its set by dreamhost anyway and defaults to 90Mb. Up until recently I had no trouble with this limit. (recently being their servers crashing) They are looking to offload servers so if you increase it beyond 90mb you may violate their TOS and get booted.

aklouie’s picture

aklouie commented

I use dreamhost and had to shift from shared hosting to their private server service running at around 300mb to be safe (fairly low activity).

I also used their php.ini entry in the wiki to boost the php memory limit to 128mb and haven't had an issue since (lots of images to convert via imagecache)

I was getting issues with the shared hosting a ton... but you can't expect much from non-static pages from that

mago-2’s picture

mago-2 commented

Thanks for your time guys!