Hi,

This has happened a couple of times now. On a Dell poweredge the system will crash at the stroke of midnight. This has been with two different RC versions - most recently rc9. Has anyone else seen this? I have a script that runs at midnight this time but last time there was no such script. Is this some kind of NTP bug by any chance?

Regards,

Malcolm

I have a supermicro system with rc10 adn it ran about 12 days I think then it rebooted in the middle of the day with respectable amount of traffic passing through its 6 interfaces. I have been reluctant to upgrade to rc11 because of the perceived problems with that build (no specifics, just seemed like a lot of people posted problems with rc11 and this rc10 seems to be working ok except for the single reboot so far). Any way, my reboot did not appear to happen at any special time - just mid portion of the day - early afternoon.

I didn't send supout because it didn't save a file - just rebooted and started running again. No autosuoout either... Is there something I can do to help diagnose for MT support if it does this again?

Scott

we i have the same question , when the traficc (pps)is very big the router will be reboot (if shut down the watchdog the router will be Crashed )

but use ver 2.9 ,there is no that problem


I think the problem caused by ver3.0,which can not be support smp very well

I have smp disabled due to problems when it was enabled. Support told me to disable it for now so I did and it improved stability a lot. I also turned connection tracking on because with it off it wouldn't work correctly.

Scott

1) check that your hardware is fully compatible with latest kernel version. If it is there shoudn't be any problems with latest RouterOs 3.0 version

2) Each crash generates a entry, that can be extracted using supout.rif file (or autosupout.rif is automatically created) just send it to mikrotik with the short description