I have openwrt 8.09.(2) installed on an Engenius 1650. Works fine and very comparable to DIR-300s and Nanostaion2 and Fonera+ I also tested.
Until I issue a simple
on the machine.
I have a little script in init.s that is called by cron every morning at 4am local time which reboots the router. I have hooked the router to a remote loggin server to see what happens and that is it:
Nov 20 04:00:02 60-234-221-116.bitstream.orcon.net.nz crond: USER root pid 20467 cmd /etc/init.d/chilli_startup start Nov 20 04:00:25 60-234-221-116.bitstream.orcon.net.nz init: init: starting pid 20638, tty '': '/etc/init.d/rcS K stop'
/etc/init.d/chilli_startup is my little script that calculates local time and sets up the 4am cron job and is called itself by cron to perform a reboot - which it does as we can see in the next line. The machine response to that command in so far as it 'closes up' that is it is not contactable anymore through ping or other wise but does not enter a complete reboot routine - as I can tell by watching the LEDs.
To ensure it is not my script I issues a 'reboot' on the command line and got the same effect. When I issue a command line reboot I get this through the remote logging:
Nov 20 07:15:01 60-234-221-116.bitstream.orcon.net.nz init: init: starting pid 2004, tty '': '/etc/init.d/rcS K stop' Nov 20 07:15:03 60-234-221-116.bitstream.orcon.net.nz root: stopping ntpclient
The machine will recover fine if I force a hard reboot by pulling the power plug.
I notice the same effect when flashing a new firmware version and using the mtd -r command. The flash will happen alright, but the reboot at the nd does not. When issuing a reboot command on redboot, the machine will reboot fine.
The log would suggest there is an issue with the /etc/init.d/rcS K stop script but looking at that, it does not actually do much.
Is there something I am doing wrong or awe looking at a bug here? Any advice welcome.
(Last edited by chillifire on 19 Nov 2009, 20:26)