changing it to shm
the problem went away...
-ascs
-Message d'origine-
De : Samuel Vogel [mailto:[EMAIL PROTECTED]
Envoyé : samedi 29 septembre 2007 17:09
À : users@httpd.apache.org
Objet : [EMAIL PROTECTED] Investigating high harddrive load
Hey people,
I would like to know if there i
the same.
Thank you.
On 29.09.07 17:08, Samuel Vogel wrote:
> Date: Sat, 29 Sep 2007 17:08:54 +0200
> From: Samuel Vogel <[EMAIL PROTECTED]>
> To: users@httpd.apache.org
> References:
> In-Reply-To:
> Subject: [EMAIL PROTECTED] Investigating high harddrive load
>
>
I enabled mysql logging and after some SQL magic I had found the problem.
Thanks!
Regards,
Samy
Brian A. Seklecki schrieb:
Basic log analysis should be pretty obvious? Do you have a standard
format for vhost log subdirs? /var/log/${vhost}/{access,error}_log ?
$ sudo tail -F /var/log/*/access
Basic log analysis should be pretty obvious? Do you have a standard
format for vhost log subdirs? /var/log/${vhost}/{access,error}_log ?
$ sudo tail -F /var/log/*/access_log
It should become obvious very quickly -- unless it's a CGI/PHP script
running a disk-intensive code block.
~BAS
On Sat
Hey people,
I would like to know if there is any way to debug what vhost is causing
the high load on my harddrive, that I'm experiencing.
To be more specific:
When I run "top", 80% of my CPU time is in i/o wait. How could I find
out, what vhost is causing this?
Regards,
Samy
---