System error critical kernel failure in previous boot

Kernel failure in previous boot микротик

Mon Aug 21, 2017 11:05 pm

Re: Random Kernel Failure in Previous boot Log

Mon Aug 21, 2017 11:07 pm

Re: Random Kernel Failure in Previous boot Log

Thu Aug 31, 2017 3:58 pm

Re: Random Kernel Failure in Previous boot Log

Thu Aug 31, 2017 4:10 pm

We usually respond within three weekdays. Please post ticket number which you did see in e-mail subject when you received automated reply from us.

Also note that rebooting issues can be debugged only if you contact support@mikrotik.com.

Multiple times in forum we have seen that people are saying that they have the same issue — «kernel faillure». It is simple message which says that router did reboot itself unexpectedly. Without involving support you can not determine if problem which you have is the same as other forum user might have.

Re: Random Kernel Failure in Previous boot Log

Thu Aug 31, 2017 7:09 pm

Re: Random Kernel Failure in Previous boot Log

Wed Dec 20, 2017 6:03 pm

Ing. Mario D. Clep
CTO — MKE Solutions
MikroTik Certified Trainer

Re: Random Kernel Failure in Previous boot Log

Wed Dec 20, 2017 9:22 pm

Please note that «rebooted because of kernel failure» means that router rebooted due to unexpected situation. Could be caused by software, hardware or Watchdog. Each case must be resolved separately through support. In order to reach solution as fast as possible — write to support@mikrotik.com and send latest supot file which would be generated after such crash on latest RouterOS version.

Kernel failure is not one specific crash. At the moment we are not aware about any current software caused Kernel failures. If we would receive complaint about software caused reboot, then we would fix such issue as soon as possible.

Источник

Kernel failure in previous boot микротик

Thu May 10, 2018 5:56 pm

Since upgrade to vV6.42.1 i am getting random reboots now

CCR1007-7G-C
kernel failure in previous boot
and
router rebooted because some critical program crashed

Happens at least once a day .. Had no issues running older version

Re: Kernel Failure in previous boot

Thu May 10, 2018 11:51 pm

I’m having similar issues. I have a CCR1009. It’s been acting as my PPPoE concentrator for a couple years. About 3 weeks ago, I upgraded the ROS version to 6.42.1 to address the vulnerability. I didn’t have any issues until yesterday after enabling OSPF/MPLS/VPLS on my network. About 12 hours later, the router rebooted. Then about 6 hours later, it rebooted again. Today it has rebooted about half a dozen times so far.

What else are you running on your router? What version did you upgrade from?

Re: Kernel Failure in previous boot

Fri May 11, 2018 9:31 am

MPLS / VPLS / OSPF / PPPOE

Sounds like we have the same problem .. Have you downgraded yet ? it was solid with version 6.40.1

Re: Kernel Failure in previous boot

Fri May 11, 2018 9:49 am

Re: Kernel Failure in previous boot

Fri May 11, 2018 1:14 pm

Re: Kernel Failure in previous boot

Fri May 11, 2018 6:10 pm

Re: Kernel Failure in previous boot

Fri May 11, 2018 9:58 pm

Re: Kernel Failure in previous boot

Sat May 12, 2018 12:32 pm

We have had such topics in forum repeatedly and the answer from us remains the same — it is not possible to determine cause of the issue through forum.

Kernel Failure — something went wrong and device rebooted itslef. Only MikroTik support can tell the reason. You must send supout file from your router to support@mikrotik.com. Maybe all of you have the same problem, maybe all of them are differenet, maybe they are caused by HW, etc. Only support@mikrotik.com can tell for sure by inspecting supout files.

In future — contact support first. Forum with such type of problem will not be able to help you.

Re: Kernel Failure in previous boot

Sat May 12, 2018 5:58 pm

We have had such topics in forum repeatedly and the answer from us remains the same — it is not possible to determine cause of the issue through forum.

Kernel Failure — something went wrong and device rebooted itslef. Only MikroTik support can tell the reason. You must send supout file from your router to support@mikrotik.com. Maybe all of you have the same problem, maybe all of them are differenet, maybe they are caused by HW, etc. Only support@mikrotik.com can tell for sure by inspecting supout files.

In future — contact support first. Forum with such type of problem will not be able to help you.

Re: Kernel Failure in previous boot

Sun May 13, 2018 1:59 am

Re: Kernel Failure in previous boot

Sun May 13, 2018 2:26 am

heavyd and johnnyk, were either of you able to create and send supout files?

Just a quick update, I downgraded to 6.40.8 and I’ve gone a little over 24 hours without any kernel failure reboots.

Re: Kernel Failure in previous boot

Sun May 13, 2018 12:12 pm

heavyd and johnnyk, were either of you able to create and send supout files?

Just a quick update, I downgraded to 6.40.8 and I’ve gone a little over 24 hours without any kernel failure reboots.

Re: Kernel Failure in previous boot

Sat May 19, 2018 6:25 pm

Hi,
I have a autosupout of CCR-1036-12G-4S with RouterOS 6.42.2 recently upgraded, before upgrade 6.20. Before the update the router did not have any problem, when updating to version 6.42.2 and trying to make a change in a firewall rule or to include a new interface to a bridge the router stayed as inhibited and restarted.

How can I send them?

Re: Kernel Failure in previous boot

Tue Jun 26, 2018 10:43 pm

Re: Kernel Failure in previous boot

Thu Nov 15, 2018 9:16 am

Re: Kernel Failure in previous boot

Fri Nov 16, 2018 4:25 am

So which specific issue did you encounter? I noticed you post same in router rebooted because some critical program crashed. Those are two different error messages and most likely also two different reasons for a crash. Are you experiencing both of them?
Also another question — did you send «autosupout.rif» file to support? (autosupout gets generated automatically after each failure and can help mikrotik staff to determine cause of failure and fix it in next versions of ROS )

just for record: I recently had two «kernel failure» errors on one particular hAP ac^2 which runs ROS 6.43.2 and support received my report as Ticket#2018111622000492

Источник

Kernel failure in previous boot микротик

Wed Dec 08, 2021 11:46 am

Hello,
I tried to upgrade one router in our network to 7.1, but unfortunately, it ended up badly.

After reboot, there was high packet loss (90+%) to the router and to a few people behind it. Winbox hung up on «logging in». I was able to login via SSH a few times for a short amount of time, so I could get to these last messages:

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Thu Dec 16, 2021 10:34 pm

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Tue Dec 28, 2021 7:52 pm

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Mon Jan 03, 2022 10:28 am

Thank you for reply.

I still wait for reaction or at least some new major version with more bugfixes which could mean «we got this».

It might be bad luck, but it was second RouterBoard I upgraded back then and that happened. I do not have confidence to continue with similarly configured devices.

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Tue Jan 11, 2022 3:11 am

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Fri Jan 14, 2022 11:14 am

Thank you for sharing this info.

I can netinstall that board for sure, but still — I wish to know that what caused this issue was fixed, so probably I do not encounter that on any other board upgrades.

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Fri Jan 14, 2022 5:37 pm

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Sat Feb 19, 2022 10:47 am

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Sat Feb 19, 2022 12:15 pm

It is probably better not to try to upgrade such old and small devices, especially when you are not using any of the newer features.
(and also not when you were using features that are not yet stable in v7)

It really is not an upgrade to just do for the fun of it. And certainly not on a remote router.

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Sun Feb 20, 2022 12:25 pm

It is probably better not to try to upgrade such old and small devices, especially when you are not using any of the newer features.
(and also not when you were using features that are not yet stable in v7)

It really is not an upgrade to just do for the fun of it. And certainly not on a remote router.

Re: RB750 kernel failure, out of memory and rebooting after upgrade to 7.1

Tue Mar 01, 2022 2:19 pm

I get it and common sense says the same. But they said in the newsletter that even an historical devices can benefit better performance with RoS 7, you get the idea that it’s not a problem. After they released v7 even for those devices, I expect to get it working if not with initial stable release, then after some time for sure.

I have no problem with having devices like RB750 deprecated for RoS 7. Well, RB750 isn’t that bad, if you consider other like RB433

Wish luck to developers with getting the most types of their routerboards compatible, bug free and working without problem. They already did a tons of great work.

Источник

Kernel failure in previous boot микротик

Wed Mar 12, 2014 2:43 pm

several times a day the router reboots:

jan/01/2002 05:00:01 system,error,critical System rebooted because of kernel failure
jan/01/2002 05:00:01 system,error,critical router was rebooted without proper shutdown, probab
ly kernel failure

Re: System rebooted because of kernel failure

Wed Mar 12, 2014 3:02 pm

Re: System rebooted because of kernel failure

Wed Mar 12, 2014 3:20 pm

Re: System rebooted because of kernel failure

Wed Mar 12, 2014 3:45 pm

At Your Own Risk:

Re: System rebooted because of kernel failure

Wed Mar 12, 2014 4:39 pm

Re: System rebooted because of kernel failure

Wed Mar 12, 2014 4:40 pm

simply send supout.rif file to support@mikrotik.com

kernel failure should be documented there

downgrading will not get the problem fixed for next release, if you don’t report to support

Re: System rebooted because of kernel failure

Thu Mar 13, 2014 3:09 pm

Re: System rebooted because of kernel failure

Thu Mar 13, 2014 3:19 pm

Re: System rebooted because of kernel failure

Fri Mar 14, 2014 7:17 am

Re: System rebooted because of kernel failure

Fri Mar 14, 2014 7:24 am

Re: System rebooted because of kernel failure

Sat May 24, 2014 1:25 pm

I`ve the same problem with Routeros 6.13 and routerboard 411 UAHR

Re: System rebooted because of kernel failure

Mon May 26, 2014 1:24 pm

I`ve the same problem with Routeros 6.13 and routerboard 411 UAHR

Re: System rebooted because of kernel failure

Mon Jun 16, 2014 11:12 pm

Re: System rebooted because of kernel failure

Thu Sep 18, 2014 8:39 pm

Dear Collegues,
we had same problem on CRS and 1100AHx2 with one ospf and some eoip runnings on it, the OS where 6.19 for CRS and 6.15 for 1100AHx2.
Frustrated from continous reboots of routers we used 2 RB2011 as spare one old with OS 6.7 start to work and now is 27 hours without reboot
secon where with OS 6.19 and still rebooting all day. At he and we dowgraded also the second to 6.7 and now seem stable.

whe opened tikets for that Ticket#2014091766000231 and Ticket#2014091666000626

I hope this description helps also MikroTik developpers

Re: System rebooted because of kernel failure

Thu Sep 25, 2014 3:35 am

Same problem here.

Re: System rebooted because of kernel failure

Mon Sep 29, 2014 6:24 pm

Re: System rebooted because of kernel failure

Mon Sep 29, 2014 6:37 pm

Re: System rebooted because of kernel failure

Mon Sep 29, 2014 6:53 pm

I just did the upgrade from 6.11 to 6.19 and after that it rebooted twice by kernel failure. After the third reboot, it stopped. Maybe because I changed some VRRP scripts?

This RB is being used on a test enviroment (thanks god!) for VRRP. I will use It and other RB1200(that has been upgraded as well and did not had problems) to have HA on my gateway to the internet.

There is one strange thing about this router, that is it’s not running On Master and On Backup scripts when VRRP interface’s state changes. I have the same scripts on both routers and no problem on 1200. 1100 simply ignores the scripts.

Re: System rebooted because of kernel failure

Mon Sep 29, 2014 7:01 pm

Re: System rebooted because of kernel failure

Wed Oct 01, 2014 2:51 pm

Just had this happen to me with 6.13 on a CCR1036. after about 90 days of uptime.
However crashes started happening every 5 minutes.
Upgraded to 6.19, been up 8 hours so far with no issues. We will see what happens when the traffic picks up today, but frankly I’m nervous.
I will be sending the supout to mirkotik.

One question, what x86 hardware do people use for RouterOS? Some have suggested it’s much more stable than CCR.

Re: System rebooted because of kernel failure

Wed Oct 01, 2014 5:26 pm

Re: System rebooted because of kernel failure

Mon May 25, 2015 6:48 am

Same problem here several time per day

uptime: 5m20s
version: 6.28
build-time: Apr/15/2015 15:18:31
free-memory: 37.1MiB
total-memory: 64.0MiB
cpu: MIPS 74Kc V4.12
cpu-count: 1
cpu-frequency: 600MHz
cpu-load: 3%
free-hdd-space: 46.8MiB
total-hdd-space: 64.0MiB
write-sect-since-reboot: 288
write-sect-total: 288
bad-blocks: 0%
architecture-name: mipsbe
board-name: RB2011L
platform: MikroTik

may/17 09:27:12 system,error System rebooted because of kernel failure
may/17 09:27:12 system,error Out of memory condition was detected
may/17 09:27:12 system,error router was rebooted without proper shutdown
may/17 09:27:12 system,error System rebooted because of kernel failure
may/17 09:27:12 system,error Out of memory condition was detected
may/17 09:27:12 system,error router was rebooted without proper shutdown
may/17 09:27:11 system,error,critical router was rebooted without proper shutdown
by watchdog timer

Funny the time is off in the logs. i guess it is because the router is not yet up to the point he knows that he is in Pacific/Auckland +12

Источник

• Вся активность