smilies
thank you fixed the bug
The graphs are clear, with a 6 day uptime and the job scheduled to run every 24h, there should be only 6 "Run Counts", the image shows 12 runs...Hi,
Could you be elaborate on what problems this version is supposed to have fixed? Your graphs were not very clear.
Thanx in advance for your input.
Regards
HASSAN
I read somewhere that this problem only appears when the script is scheduled to run in a round time, finished with :00 minutes. A workaround would be set the script to run at broken times like 13:01 pm instead of 13:00 pm. I don't use scheduled scripts so I can't tell if this is true but doesn't hurt to try...This scheduler bug has been around for most of v3! see: http://forum.mikrotik.com/viewtopic.php?f=9&t=22675 it can have a snowball effect if your 24hr or even 48hr timed scripts call other scripts in their runtime - you will end up with the same script running twice concurrently and on some occasions this will crash a V3 router.
17 sub releases and this is still a big problem. I wrote to support at V3.6, V3.11, and 3.15 the replys were "it will be fixed in a future release". How many releases exactly? will this be fixed before V4?
Unfortunately this is not the case... Some of our scripts are scheduled to run 11:58pm and 12:04am etc but they still run twice.I read somewhere that this problem only appears when the script is scheduled to run in a round time, finished with :00 minutes. A workaround would be set the script to run at broken times like 13:01 pm instead of 13:00 pm. I don't use scheduled scripts so I can't tell if this is true but doesn't hurt to try...
Me too .Hi,
I just upgraded an x86 router from 3.10 to 3.17 and it factory defaulted the config !
I am downgrading and restoring from a backup now.