I have a few scripts but none act the way this one does. The desire is to reboot the router device once every day at 3AM. Seems simple but it has caused some undesirable oddities that I am unable to figure out.
What I am seeing is the day I add the script, it executes as expected but that is when normal expectation ends. Even though the “Next Run” field shows the next expected run time, it will skip this time and only execute every other day.
Then the strange thing happens, the script executes an unscheduled time during the day, also every other day after the scheduled reboot occurs.
While, I would like to know the answer as to why, I can live with the every other day problem but rebooting at 9:57 in the morning, just as the office starts doing its daily business has become a sore point. If anyone can chime in and help me figure out where this extra reboot is coming from, I would be most appreciative.
This is an x86 device running v6.35.2(stable) just recently upgraded from 6.35(stable) in hopes to resolve this as a stray bug with no luck. The device is an i7 CPU with 8 cores 3.4GHz and 2GB RAM. Storage is 120GB SDD.
What my question is: why do you need a reboot that often? A reboot is only needed when updating the OS, or the firmware.
The Mikrotik in a church I installed have been running here already for almost 3 years (not counting the one time power failure, and the multiple OS updates).
Thank you both for responding. I considered explaining why I am doing this but decided that it would detract from the goal. But since you asked, I will explain. This is certainly not a standard course of action…
The router will run for about three days and then appear to lock up. The device is non-responsive to network traffic and I am still working through what is happening on that front. For a couple of weeks this has been happening and I have not had the good fortune to have the client call me before they power cycle the unit. I have found that if I reboot the device every morning before they begin the day, the issue does not occur, thus I have time to explore the lock up issues without losing control. I am wanting to allow it to lock up once where I can get the client to tell me if they can get console access of if the machine is truly locked up. To ease tempers, I have been rebooting regularly and monitoring for unusual conditions.
To take this further, this unit is being used for three pptp site-to-site VPN tunnels and about 30 individual Windows software VPN clients that are on randomly through the day. This system worked perfectly for about a month after deployment and due to an ISP blunder, we were forced to relocate the operations to one of the other sites which could handle the bandwidth. It was there for about two weeks and worked perfectly. When the system moved back to the original site, it has developed this random lockup issue which takes 2-5 days to manifest and show itself.
The whole thing seems as if it is a memory leak of some sort but I cannot put my finger on it.
Also to add, I have looked in both WinBox and Webmin at the scheduled tasks and there only appears to be two tasks scheduled, the one I have shown and one other which runs hourly. The hourly task works fine. I cannot find anything which is causing the 9:57AM reboot of the router but I can assure you it is happening on a schedule of every day which is new of just the past few days and I do not know where else to look to eliminate that one.
