Posted: Fri Oct 30, 2009 0:36 Post subject: old httpd 100% bug back again?
Hi,
I'm using DD-WRT for a quite long time now and since a few days (maybe weeks) I'm experiencing an old bug again.
The httpd -S process raises up to 100% of the cpu time.
I have HTTPS webgui turned on but SSH is disabled.
Shouldn't you be running a VINT build? I didn't get high CPU with 13064, but I wasn't running it on a GSv1. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
according to this page:
http://www.dd-wrt.com/wiki/index.php/What_is_DD-WRT%3F
I should be able to run both.
I have a Broadcom BCM4712 chip rev 1 with 200 Mhz and corerev 7.
Never had problems with NEWD builds before (except the 100% httpd bug in older versions)....
I seem to recall something from the past about having https and http for Web Access enabled at the same time.
Do you have that? _________________ Kernel panic: Aiee, killing interrupt handler!
And do the correv test. Read the announcements. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
I'm not sure what you mean with "corerev test".
I already wrote that my router comes with corerev 7 but this should be no problem.
Or do I miss the point?
I'm not sure what you mean with "corerev test".
I already wrote that my router comes with corerev 7 but this should be no problem.
Or do I miss the point?
Correv is explained in the announcements. Did you read the correv for your router by doing the test, or reading about it. If it is 7 you can use newd. However, LOM likely nailed the real issue here.... _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Did you read the correv for your router by doing the test, or reading about it. If it is 7 you can use newd.
I've used the nvram command to determine my corerev version
Since disabling the http option there was no CPU race at all for now so LOMs solution seems to be correct, credits go to him.
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Mon Nov 02, 2009 1:04 Post subject:
I am not sure if you are running ssh, but there was a problem running "https" *and* "ssh" several months ago. It had the same 100% pegged CPU usage. I have not seen any recent reports, but I think that problem is still unresolved (at least it has not been reported as fixed). _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Try 12548. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."