[support] development and production environments

[cooper Quintin]

Victor Kane wrote:
> :)
>
>
> Of course, I don't know what your performance settings are, etc.
> (cache enabled?), but anyway, let's see if this success is contagious
> (something may have been repaired in the database, or cache's may
> never have been cleared): If you have the devel module installed,
> clear the cache and then back up the database and attempt to
> transplant the site elsewhere. If you don't have the devel module
> installed, click on the Save configuration button in Administer > Site
> building > Modules, then save the database.
Well, everything seems to be working swimmingly now!  The success was
indeed contagious, and I now have 3 wonderfull environments set up and
running smoothly.  Thanks so much for your help victor and everyone else
who replied to this thread!
>
> If the transplant works, we're all set (something was repaired).
>
> Victor Kane
> http://awebfactory.com.ar
>
> On Wed, Jan 28, 2009 at 8:48 AM, cooper Quintin <cooperq at cooperq.com
> <mailto:cooperq at cooperq.com>> wrote:
>
>     Well, now I am more confused than ever.  I did as you said, I disabled
>     all the third party modules on the site (I made sure that it was still
>     not working first.)  And then I started adding them back, one by one.
>     Well, I have added them all back now, and the site is still
>     running, no
>     crashes at all.  So by disabling and enabling all modules I fixed the
>     test site on my laptop.  I don't understand at all how it would happen
>     that the test site is crashing my laptop, I disable all modules then
>     enable all modules again and everything works exactly as it
>     should.  Any
>     ideas on this?
>     Victor Kane wrote:
>     > Well, that certainly narrows it down.
>     >
>     > Since you have a backup, can you take advantage of that 2
>     minutes and
>     > disable the core statistics module if it is enabled, and all 3rd
>     party
>     > modules? Because then you could start enabling them one by one
>     to see
>     > where the problem might be.
>     >
>     > If you can't get in, what you can do is the following: assuming your
>     > modules are in ./sites/all/modules, then simply move them away, then
>     > your site will come up without them enabled.
>     >
>     > Then you can sort of add them in one by one, to see which one is
>     > causing the problem.
>     >
>     > Make sure php.ini has enough memory allocated, push it up to 64M to
>     > start if you have many modules, or even more:
>     >
>     > memory_limit = 64M
>     >
>     > Another tack is to use some kind of MySQL diagnostics to see what
>     > queries are killing you.
>     >
>     > The devel module would help but only if you can get the site to run!
>     >
>     > What happens when you disable all the modules and start adding them
>     > back one by one (how many are there?)
>     >
>     > Victor Kane
>     > http://awebfactory.com.ar
>     --
>     [ Drupal support list | http://lists.drupal.org/ ]
>
>


-- 
Cooper Quintin
Freelance Programmer, Indymedia Journalist
http://CooperQ.com
(510) 827-5382