The faulty interface lies between the chair and the keyboard.

Wordpress causing Apache to restart?

Here is a sample of the error logs; it starts off with about five miles of dots, then Fatal:

FATAL: erealloc(): Unable to allocate 1441792 bytes

[Fri Sep 01 13:25:59 2006] [notice] Parent: child process exited with status 1 — Restarting.
[Fri Sep 01 13:26:00 2006] [notice] Parent: Created child process 2468
[Fri Sep 01 13:26:01 2006] [notice] Disabled use of AcceptEx() WinSock2 API
[Fri Sep 01 13:26:04 2006] [notice] Child 2468: Child process is running
[Fri Sep 01 13:26:04 2006] [notice] Child 2468: Acquired the start mutex.
[Fri Sep 01 13:26:04 2006] [notice] Child 2468: Starting 250 worker threads.
[Fri Sep 01 13:26:04 2006] [notice] Child 2468: Listening on port 80.

I am going to deactivate user’s online script (WP-UserOnline version 2.04) to see if that’s the culprit?

Also see
Wp causing Apache to restart?

Recent Entries

One Response to “Wordpress causing Apache to restart?”

  1. John’s Blog » Blog Archive » Wordpress and Apache problem solved. Says:

    [...] After updating and restoring the database on the server, I have found that the errors that the server was having have now disappeared (to read previous articles on Wordpress being the cause of Apache to restarting follow the links. Article one and article two [...]

Leave a Reply

You must be logged in to post a comment.