[support] big problem with drupal 7.19 on shared server

Walt Daniels wdlists at gmail.com
Tue Jan 22 19:00:56 UTC 2013


Yes, that is a sure way to break sites.


On Tue, Jan 22, 2013 at 12:34 PM, Earnie Boyd
<earnie at users.sourceforge.net>wrote:

> This should be brought up in the Drush issue support as a feature
> request to leave php.ini alone.
>
> On Tue, Jan 22, 2013 at 8:31 AM, Shai Gluskin <shai at content2zero.com>
> wrote:
> > Hi Roger and all,
> >
> > Drush will delete non-drupal files that are not in the sites directory.
> >
> > It sounds like you typically have a php.ini file installed at the Drupal
> > root. Did you put it back after Drush erased it? Can you verify that it
> is
> > still there?
> >
> > Even though I have a dedicated server, I run it like a shared server
> using
> > cPanel. I've updated 12 Drupal 7.19 sites on 12 different cPanel accounts
> > and have not had any problems. However, my situation is different in
> that I
> > have the server-wide php.ini file tuned for my Drupal set-ups, so I don't
> > need to have any php.ini files installed at the Drupal root.
> >
> > But I do manage a Drupal site on another cPanel server and ran into
> problems
> > similar to what you ran into. Drupal erased the php.ini file installed at
> > the Drupal root. Once I figured out that was the problem (with some help
> > from the HostGator customer support), I just put back the php.ini file
> > (which I had a backup of) and everything got better.
> >
> > Shai
> >
> >
> > On Tue, Jan 22, 2013 at 4:21 AM, Roger <arelem at bigpond.com> wrote:
> >>
> >> Hello
> >> I updated drupal using drush successfully on the shared server
> >>
> >> When trying to open permissions I got bytes exhausted error and had to
> >> increase memory_limit to 256M to at least access permissions.
> >>
> >> Now have a problem, in /admin/structure/types/add I get error:
> >> *Fatal error*: Allowed memory size of 134217728 bytes exhausted (tried
> >> to allocate 79 bytes)
> >>
> >> I have tried various memory settings in php.ini on the server and find
> >> that memory_limit = 128M seems to try to allocate less bytes than if I
> use
> >>   96M, 128M or 256M.
> >>
> >> Why does drupal exhaust memory, this  seems most strange
> >> Can you please tell me what causes this error and how to fix it. Google
> >> has not helped much.
> >> Thanks in advance
> >> Roger
> >>
> >> --
> >> [ Drupal support list | http://lists.drupal.org/ ]
> >
> >
> >
> > --
> > [ Drupal support list | http://lists.drupal.org/ ]
>
>
>
> --
> Earnie
> -- https://sites.google.com/site/earnieboyd
> --
> [ Drupal support list | http://lists.drupal.org/ ]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/support/attachments/20130122/1a687de0/attachment.html 


More information about the support mailing list