Perhaps the Aztecs were running Unix, would sure explain a lot. :) There is no legit reason for your server to eating a gig of ram with Drupal. Likely you've been p@wned. Check your logs and kill anything out of the ordinary. I just had a drupal site compromised a week ago. Came as quite the surprise since it was fully patched. Had to switch to manual approval of new accounts as a work around.
On Tue, Jul 9, 2013 at 1:15 PM, Merrill Oveson <[email protected]> wrote: > Pluggers: > > Running Drupal 7.19 on CentOS 6.3 Apache 2.2.15. > Hosted on RackSpace: 1024 MB RAM 40 GB. > > > I went live on a site, everything worked fine for a week and then > suddenly... > "Out of memory: Kill process 21614 (httpd) score 23 or sacrifice child" > > Do I need to upgrade the slice? > I think 1024 should be enough. > > Ideas for what my httpd.conf should look like? > > BTW: RackSpace was no help. (Even though I like RackSpace.) When asked > about preventing the server from ever crashing - that is web server. The > tech responsed, "That is usually the biggest hurdle for most of our > customers." > > Merrill > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
