Hi,

right now I'm looking into logs and try to find out the reason, but the title says it all. I just enabled the module and after that the entire server was not responding. The /admin/build/modules page took 10 minutes to load and after that I disabled the module and everything got back to normal. During the unresponsive time I wasn't able to access ftp, load cpanel or anything, which is quite strange. This site is quite a big one with 36 content types almost 300 fileds and almost a 100 enabled modules but still running like a charm, but only enabling this module knocked it down.
Any ideas what could cause this?

Thanks,
Dave

Comments

NancyDru’s picture

There are more than 1,000 users of this module and no one else has reported this. I would look for some other process that consumed a vast amount of CPU power.

dawe’s picture

I'm going to re-test it on a dev version, but won't have time for it for a week at least. I didn't want to believe it either, so disabled and enabled the module 2 times and the server was unresponsive for a good while after both installation... Will try to share some useful info as soon as I can.

dawe’s picture

Hi,

re-tested on dev machine. It seems that some process is started after enabling the module which are very memory consuming, which knocked down the production site. After enabling on dev environment got a message "tried to allocate 4Gig of memory"... It happened every time I re-enabled the module (so must be in relation with the module), but afterwards it was OK with the module enabled on the site.

Can't say exactly what was the cause of the problem, but for future reference this post might be useful...

Long story short: Extreme memory consumption during enabling on very large site, but afterwards the module works as it should!

Dave

NancyDru’s picture

Priority: Critical » Major

I just installed 6.x-2.7 on a test site with only 64 nodes and there was no trouble at all.