[support] Drupal 7 catastrophe

[Jamie Holly]

If phpinfo reports that it's using /etc/php.ini, then that's what it is 
using.

You posted earlier that you were able to use Drush to clear the cache. 
Try using that to set the theme:

drush vset theme_default bartik

You can also use Drush to disable modules.

If Drush is working on the site, then I would say the problem does lie 
in your theme.

Jamie Holly
http://www.intoxination.net
http://www.hollyit.net

On 2/12/2013 5:20 PM, Roger wrote:
> Drupal and/or PHP will not start, it's memory use grinds the whole
> computer system to a halt. It is not possible to switch themes or turn
> off modules. I believe that PHP does not read /etc/php.ini but there are
> no other files for it to read and phpinfo() reports /etc/php.ini
> Roger
> > <snip>
> >
> > Start by switching to the default theme and see if that fixes the
> > problem. If it doesn't, then you got to start disabling contib modules
> > one by one until you can figure out what the root of the problem is.
> >
> > If you're good enough at installing PHP modules, you could always use
> > XHProf or XDebug and have it record a call chart while executing the
> > site. That should give an idea where the problem is.
> >
> > Jamie Holly
> > http://www.intoxination.net
>
> On 2/11/2013 7:51 PM, Roger wrote:
>
> > As I understand it Drupal loads all modules and the current enabled
> > theme, (or maybe all the themes) on start up.
> >
> > More modules = more memory, even though many modules are on call, not
> > used in development or production except in certain rare circumstances,
> > for example norequestnewpass, newsletter and it's associated modules,
> > nat, mailsystem, autonodetitle, backup_migrate, devel, and all
> > workbench modules, just to name a few. For one of our sites, 43 modules
> > in all. Most of those exist only to solve issues introduced by other
> > modules.
> </snip>