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, 2007-09-29 at 17:08 +0200, Samuel Vogel wrote:
> 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
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
> " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>
>
>
>
>
>
>
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|