Lighttpd takes all processor?
-
I have noticed on my pfSense box that whenever I login to the WebGUI, it starts the lighttpd to serve it. However, even when I am NOT using the WebGUI, it stays running and creeps up slowly until it is using all available processor, usually hovering about 85-90%. This slows everything down, and the only way to fix it is to SSH in and restart the WebConfigurator. For reference, this is a P266 with 256MB of RAM. Is this a known issue or does anyone know of a fix? Thanks.
-
I have noticed on my pfSense box that whenever I login to the WebGUI, it starts the lighttpd to serve it. However, even when I am NOT using the WebGUI, it stays running and creeps up slowly until it is using all available processor, usually hovering about 85-90%. This slows everything down, and the only way to fix it is to SSH in and restart the WebConfigurator. For reference, this is a P266 with 256MB of RAM. Is this a known issue or does anyone know of a fix? Thanks.
Any chance you've left a browser or two open on any status page? We do make use of AJAX in a couple places to refresh information. Maybe one of those is tripping you up.
–Bill
-
it's not lightpttd that eats the cpu
i have a 166 mhz box and lightpttd takes 0% cpu on index.php
but php takes close to 99% when its refresing index.php -
I have noticed on my pfSense box that whenever I login to the WebGUI, it starts the lighttpd to serve it. However, even when I am NOT using the WebGUI, it stays running and creeps up slowly until it is using all available processor, usually hovering about 85-90%. This slows everything down, and the only way to fix it is to SSH in and restart the WebConfigurator. For reference, this is a P266 with 256MB of RAM. Is this a known issue or does anyone know of a fix? Thanks.
Any chance you've left a browser or two open on any status page? We do make use of AJAX in a couple places to refresh information. Maybe one of those is tripping you up.
–Bill
Definitely sure, checked to make sure no browser processes were running whatsoever. What I eventually end up with is:
last pid: 4948; load averages: 1.82, 0.64, 0.25 up 0+01:15:13 15:13:34 30 processes: 2 running, 28 sleeping CPU states: 19.0% user, 0.0% nice, 79.8% system, 1.2% interrupt, 0.0% idle Mem: 32M Active, 8136K Inact, 19M Wired, 11M Buf, 184M Free Swap: 128M Total, 128M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 1248 root 1 132 0 3184K 2308K RUN 1:17 80.42% lighttpd 4689 root 1 97 0 5568K 2588K select 0:01 2.39% sshd 4945 root 1 -32 0 2256K 1500K RUN 0:00 0.54% top 389 root 1 4 0 43820K 17532K accept 0:05 0.20% php 388 root 1 4 0 41588K 15196K accept 0:03 0.00% php 1276 root 1 8 20 1652K 1228K wait 0:02 0.00% sh 609 root 1 8 20 1192K 648K nanslp 0:02 0.00% check_reload_st 303 root 1 -58 0 3676K 1904K bpf 0:00 0.00% tcpdump 168 root 1 96 0 1360K 992K select 0:00 0.00% syslogd 264 _dhcp 1 96 0 1388K 1020K select 0:00 0.00% dhclient 304 root 1 -8 0 1196K 684K piperd 0:00 0.00% logger 384 root 1 8 0 36632K 4596K wait 0:00 0.00% php 385 root 1 8 0 36632K 4596K wait 0:00 0.00% php 621 root 1 8 0 1568K 1236K wait 0:00 0.00% login 578 root 1 8 0 1304K 980K nanslp 0:00 0.00% cron 4871 root 1 20 0 3540K 2532K pause 0:00 0.00% tcsh 472 proxy 1 4 0 656K 416K kqread 0:00 0.00% pftpxAnd that's with no browser windows open. If I login to the box via console or SSH, I can Restart and it will be fine until I next access it via HTTP.
-
it's not lightpttd that eats the cpu
i have a 166 mhz box and lightpttd takes 0% cpu on index.php
but php takes close to 99% when its refresing index.phpSee previous post.
-
Looks like a lighttpd bug. We'll get it sync'd with the newest version of apc and lighttpd on next release once freebsd 6.2 arrives.
-
Looks like a lighttpd bug. We'll get it sync'd with the newest version of apc and lighttpd on next release once freebsd 6.2 arrives.
Yay, I found a bug. Thanks fellas.