Mikrotik reboot varies times to the day

Mikrotik restarts varies times to the day .

How to know what it is?

is there anything in the log? is this a PC or routerboard? are you using Watchdog?

We need more info to be able to help

See what’s written in the log and paste it here and as HarvSki said is it RB or PC…

my core router started to hung up after upgrading to 2.9.14

Giving the fact that it is a pc based, I am not able to reboot it automatcly by watchdog.

I downgraded back to 2.9.11 but still have some time each 2-3days this issue. Before to upgrade from 2.9.11 to 2.9.14 the router was rock solid for more then 40days.

Very difficult to debug because I am not getting naything into the log…just freezingup

Regards
rosario

:frowning: one of my routers reboot too, in the log i can only see:

mar/04/2006 18:34:39 system,error,critical router was rebooted without proper shutdown
mar/04/2006 18:37:33 system,error,critical router was rebooted without proper shutdown
mar/04/2006 18:43:49 system,error,critical router was rebooted without proper shutdown
mar/05/2006 10:22:55 system,error,critical router was rebooted without proper shutdown
mar/05/2006 10:25:14 system,error,critical router was rebooted without proper shutdown
mar/05/2006 10:27:42 system,error,critical router was rebooted without proper shutdown
mar/05/2006 10:45:15 system,error,critical router was rebooted without proper shutdown
mar/05/2006 10:48:50 system,error,critical router was rebooted without proper shutdown

It´s a PC based router with 2.9.14


Regards

We just had a prod router reboot today after 90 days uptime as well.. 2.9.6. I wonder if there are some weird BGP flaps that aren’t liked, are you both running bgp as well?

mar/05/2006 15:31:50 system,error,critical router was rebooted without proper shutdown
mar/05/2006 15:34:25 system,error,critical router was rebooted without proper shutdown
mar/05/2006 15:39:42 system,error,critical router was rebooted without proper shutdown

Sam

If you can completly turn off watchdog and see if it still reboots. One time we upgraded the ip address in watchdog got changed to 0.0.0.0 and that caused the router to reboot alot for us.

Also if the ip your watching is your wireless link the link may be getting some interfearance which is causing it to reset.

We do not use watchdog…

@Changeip

No BGP…


Regards

This particular box was a supermicro, not able to use watchdog.

Sam

The part with the 0.0.0.0 ip address was directed to the “ping watchdog”, where the system reboots when it cannot reach the configured IP address anymore.

We had this bite us, too, in some occasions (like automatically switching to a backup uplink over which the “netwatched” ip address was not reachable. Made the whole fuss for automatic uplink switching useless, as while on the backup line the router rebooted continually… :smiley: ).

Best regards,
Christian Meis

I am not sure if the problem you are having is the sme as mine, but Quake3 crashes my RB532s

-Carlo

I had broken one memory module at my mikrotik (2x512 MB DIMM). It was reboot few times a week, sometimes two-three times a day.

I validated that a specific type of malformed packet would cause mikrotik to reboot under a load, but not sure this is what’s causing it. I have sent mikrotik results of this a few months back but never heard that it was fixed. I will test it again and see if its still an issue - possibly these packets are more in the wild now and hitting the router and rebooting them … that would be bad : )

Sam

could you resend that email to support@mikrotik.com so we could check again?

sent…

I will test this again in 2.9.14 and see what happens. Previously this was an issue when 2.9.7 was current but I am guessing its the same. I will followup later today after I resetup our dev environment.

Sam

Well, it hapends to me on two PCs.
One was rebooting without proper shutdown because it was to cold for him, I placed blanket over and everything is fine - I hope I’ll not forget to take it out when warm weather comes :smiley:
Other one had Power supply problem, I just changed it and this one is ok also.
In 99% of situations it’s hardware problem…

Cheers…

Just a followup - this malformed packet (biffit) does not cause MT to reboot anymore. I tested with 2.9.17 and it seems to be working as it should.

Thx,
Sam

Does the watchdog reboot the unit without proper shutdown?