/sbin/reboot no longer working

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Installed latest stable version of the code 3.0.3.8-081 
2. Setup CRON job to run /sbin/reboot by editing script
echo "0 5 * * * /sbin/reboot >/dev/null 2>&1 #reboot_task" >> $CRONTABS
3. Apply
4. Wait for a day 

or Login to shell using putty, issue 
/sbin/reboot

What is the expected output? What do you see instead?
At 5AM every day router should reboot, or whenever you issue reboot command 
using putty. But router does not reboot, reboot command just returns. The Cron 
job is calling the script at 5AM, as apperent by log, but router stays up!

Original issue reported on code.google.com by Adarsha...@gmail.com on 22 Oct 2014 at 2:20

GoogleCodeExporter commented 9 years ago

just checked on 3.0.3.8-084, the device was rebooted.

Original comment by d...@soulblader.com on 24 Oct 2014 at 12:47

Changed state: Invalid

GoogleCodeExporter commented 9 years ago

Not for me..

Nov  5 01:58:22 NTP Client: Synchronizing time to pool.ntp.org.
Nov  5 01:58:24 NTP Client: System time changed, offset: 0.431966s
Nov  5 05:00:01 crond[642]: crond: USER admin pid 844 cmd /sbin/reboot 
>/dev/null 2>&1
Nov  5 07:58:23 NTP Client: Synchronizing time to time.nist.gov.
Nov  5 07:58:25 httpd[585]: Received SIGTERM, terminating.

Ideally I should even see that line in the log as the log gets cleared upon 
reboot. But in my case router continues to operate as if nothing happened even 
after crond called reboot.

Original comment by Adarsha...@gmail.com on 5 Nov 2014 at 4:39

javitu / rt-n56u

/sbin/reboot no longer working #1347