My first contact on watchdog-reboot in mikrotik v.6.xx is 13-09-2014.
Since then I replaced the support of more than 16 email.
2 S. Martins mail
1 email with Kristaps S.
10 mail Uldis
And at the end of one email from Janis B. To which I replied. But since 10-10-2014 I did not get an answer.
I sent them the 20-30 supout.rif
Zaaktualizowałem few devices (711, Lite5, 2011iL, etc..) To version 6.xx (6.7, 6.19, now 6.20).
When the work day, or two days can restart themselves. (disable watchdog suspends the device).
Sometimes when you enter the device from the MT v6.xx causes restart.
Sometimes supout.rif generating device with MT v6.xx causes restart.
Sometimes when you export the configuration to the device MT v6.xx causes restart.
Support recommending disable snmp, api - I made it - did not help.
Support recommending the inclusion of rstp - I made it - did not help.
I also have a lot adjoining equipment on the MT v5.26 and running. Any errors. Uptime of 100 days and more.
This is really ridiculous on their part. No information. No solution to the problem. No stable software. Do not refined.
Sell equipment that does not work well.
You test software on their clients. On what world you live?
Maybe I just was already beyond software development? Maybe it's time to give this project the people who know their stuff?
Please solution to my problem, because for such problems losing customers, good reviews.
I am terribly pissed off at your software. Although this is a very nice solution.
These people have a similar problem:
http://forum.mikrotik.com/viewtopic.php ... 00#p452253
http://forum.mikrotik.com/viewtopic.php ... 00#p452266
this "router was rebooted without proper shutdown by watchdog timer" problem solved?
I still have this issue from 6.7 to 6.19 mostly on all RB2011/ RB750G / RB911 / SXT Lite5 devices approx 70 pieces of our devices affected by this error.
Mostly all devices reboot between 1am to 3am. Devices that are affacted are not on the same location, (20-40km) all of them are running through uninterruptible power supply, so it could not be a power problem. At the same time, and on the same tower other devices which are not running Mikrotik 6.x version are still running.