On Tue, 26 Feb 2013 08:32:36 +1000
Brett Maxfield wrote:
> If apache can write everything on start, and then it becomes
> unresponsive, that sounds like file handles / inodes. There wont be
> errors as likely the thread with the problem can't write logs..
No, as long as I don't touch it, it runs
On Mon, 25 Feb 2013 14:48:10 -0500
Ben Johnson wrote:
> I do find it curious that your logs are so well-populated (error and
> suexec.log, in particular), but that's probably unrelated to the
> "unable to open logs" error.
It would be nice to just see errors in the suexec log.
> Does the syslog
If apache can write everything on start, and then it becomes unresponsive, that
sounds like file handles / inodes. There wont be errors as likely the thread
with the problem can't write logs..
But if apache locks up hard, due to no inodes, or something else, you wont kill
it with a kill -1, and
On 2/25/2013 12:03 PM, D'Arcy J.M. Cain wrote:
> I have been scouring the net for my specific issue. All the responses
> suggest that either the file permissions are wrong or that the ulimit
> is set too low. I know that neither of these is my problem because
> Apache starts at boot and sometim
I have been scouring the net for my specific issue. All the responses
suggest that either the file permissions are wrong or that the ulimit
is set too low. I know that neither of these is my problem because
Apache starts at boot and sometimes restarts while the server is
running. While it is run
