Ever since installing PhpWiki 1.3.10, my 1.3 Apache HTTPD (on Linux) occasionally (a few times a day) starts eating up CPU time. Load averages which are typically well below 1.0, rise to 10.0 or more and don't come down until I restart HTTPD. I don't know how to debug this and I can't be sure it's PhPWiki, but I'm wondering if anyone else has seen this behavior and how one might go about finding the offending code. Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nope. It' not traffic. I checked both log files. It's HTTPD gobbling up CPU time. I restart Apache, and everything goes back to normal. I disabled PhpWiki (by renamin the directory so links can't find it) and the problem doesn't restart. Hmmm... If no one else reports a similar problem, then I'll assume it's something I've done wrong.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It could also be phpwiki, cycling in an endless loop, but this is normally stopped after some time by the php process. And I'm not aware of such problems lately.
It happened in previous experimental versions though.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I grep'ped for all the set_time_limit calls and disabled them. It still loops. My PHP config should kill it after 60 seconds, as it does when I write a hard loop in a test PHP routine. Bummer, too, 'cause I like PhpWiki but just can't run it with this problem. Guess I'll have to Plan B.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ever since installing PhpWiki 1.3.10, my 1.3 Apache HTTPD (on Linux) occasionally (a few times a day) starts eating up CPU time. Load averages which are typically well below 1.0, rise to 10.0 or more and don't come down until I restart HTTPD. I don't know how to debug this and I can't be sure it's PhPWiki, but I'm wondering if anyone else has seen this behavior and how one might go about finding the offending code. Thanks.
look at the access and error log.
it's probably just the googlebot.
Nope. It' not traffic. I checked both log files. It's HTTPD gobbling up CPU time. I restart Apache, and everything goes back to normal. I disabled PhpWiki (by renamin the directory so links can't find it) and the problem doesn't restart. Hmmm... If no one else reports a similar problem, then I'll assume it's something I've done wrong.
It could also be phpwiki, cycling in an endless loop, but this is normally stopped after some time by the php process. And I'm not aware of such problems lately.
It happened in previous experimental versions though.
I grep'ped for all the set_time_limit calls and disabled them. It still loops. My PHP config should kill it after 60 seconds, as it does when I write a hard loop in a test PHP routine. Bummer, too, 'cause I like PhpWiki but just can't run it with this problem. Guess I'll have to Plan B.