Posted: Sun May 19, 2019 15:33 Post subject: shedule reboot not working
Router Model:linksys wrt 1900ac
Status: ok
Reset: no
Errors:the schedule reboot is not working.Will appreciate it if u can have a careful look at it.
I have to keep rebooting manually because when i schedule it it does not work.
Thank you
Just tossing this out, but have you checked if the time is set in your router? If not, please ensure that you have a time server set for use. I recommend utilizing time.nist.gov as it's the main server for NIST and will automatically balance the load of the NIST servers by redirecting the query to a server with lower utilization.
If your time isn't set, the schedules won't work. First thing I could think of.
One more thing... Did you flash the new DD-WRT firmware and keep your old settings? If so, try changing the time schedule for the automatic reboot, save settings, apply, then change them back to what you ultimately want, save, apply and reboot the router. Sometimes the old settings in NVRAM don't migrate properly after a DD-WRT upgrade.
Posted: Sat Jun 01, 2019 10:33 Post subject: Worked once, but...
The Scheduled Reboot worked the first night after I'd updated to R39884 (20190530), but isn't working now.
My recollection is that this has been an issue that's come and gone over various releases. Rather than mess with it, I've added the "Reboot" script under Administration/Commands. _________________ Router: Linksys WRT1900ACSv2
Modem: Verizon Fios DD-WRT v3.0-r44048 std (08/02/20)
ISP: Verizon Fios
NAS: ReadyNas314
After I couldn't get the scheduled reboot to work by checking the box in the Administration/Keep Alive tab, I UNchecked that box, and put the following script into the Adminstration/Commands "Startup" section:
Unfortunately, this isn't working either. I've checked to see that the script is indeed getting written (it is), and the entry has been made in /tmp/cron.d (it's there).
Any thoughts on this? I've found, at least with older releases, that without a regular reboot, dnsmasq stops working reliably.
I have not used the script in a long time and I find nothing that says it has to be
but I did have cron enabled on Administration->Management tab with other tasks.