Tonight I was messing with my Asus WL-500 and was having trouble getting lighttpd to start. I found some post in russian that I was able to decypher thanks to my excellent linguist skills (haha). Anyway, it’s pretty easy.

# ipkg install nano
# nano /opt/etc/lighttpd/lighttpd.conf

and then change

# server.event-handler = «freebsd-kqueue» # needed on OS X

to

server.event-handler = «poll» # needed on OS X

After changing this, lighttpd started right up with fastcgi php.

Comments

Comment by wirespot on 2009-11-06 01:37:59 -0500

Thank you! Fixed mine too (on WL-500gP v1).

Comment by jsmith on 2009-11-30 09:26:28 -0500

Thanks a bunch man!

Comment by Violin Iliev on 2010-01-20 02:49:38 -0500

Thanks! 🙂
Mine is WL-500gP v2. This fix works fine. 🙂

Comment by Gabriel on 2010-01-30 07:15:55 -0500

Thanks a lot, Matt! I was working on installing ADOS download manager on my ASUS WL-520gU router with Tomato firmware when I encountered this error. I was wondering why nothing would display in my Web browser whenever I accessed lighttpd’s document root. Checking from /opt/var/log/lighttpd/error.log gave the same error as yours- fdevent_init failed. Changing server.event-handler from “freebsd-kqueue” to “poll” fixed it.

Comment by Jordi on 2010-03-15 05:23:49 -0500

Thanks, that works also on oleg’s wl500 firmware

Comment by Stepan on 2010-03-27 16:22:17 -0500

Thanks man, this works on WL-500gP with Oleg firmware too !!!

Comment by postbusjj on 2010-06-01 05:48:50 -0500

Brilliant!

Comment by Mark on 2010-06-21 20:58:58 -0500

Thanks bro, you spared what hair I have left.

Comment by das_deniz on 2010-08-08 12:41:19 -0500

ipkg nano completely redundant to ‘vi /opt/etc/lighttpd/lighttpd.conf’
otherwise absolutely spot on fix for “poll” thank you very much

Comment by senthil on 2011-02-20 20:25:56 -0500

Thank you for tips. It helped me to start the lighttpd.

Comment by cookies on 2011-03-10 00:51:50 -0500

worked for my WL-500GpV2

Comment by Burak on 2015-11-28 15:43:30 -0500

poll causes another error you can see in error log. so the best is:

server.event-handler = “select”

use this and you will see no error 😉 !!