System error critical router rebooted because some critical program crashed

System error critical router rebooted because some critical program crashed

Sat Aug 06, 2022 9:49 am

Suddenly today my CCR crashed with a error message — Router rebooted because some critical program crashed.

Kindly please tell me what the issue about .

Re: CCR2004-16G-2S+ — Critical Program Crashed

Sat Aug 06, 2022 10:29 am

It would help a lot more if you
— provided us the correct version your device is currently using
— provided more info on what else is running on that device

You can consider to upgrade to latest stable version (from your previous posts, which I normally should not look for, if the info would have been given from the first time, I see you’re on 7.3.1. Is that still the case ?)

If it happened only once, don’t worry too much about it.
If it happens more often, best to create supout.inf and send it over to support so they can investigate.

Re: CCR2004-16G-2S+ — Critical Program Crashed

Sun Aug 07, 2022 11:52 am

Re: CCR2004-16G-2S+ — Critical Program Crashed

Sun Aug 07, 2022 11:56 am

Re: CCR2004-16G-2S+ — Critical Program Crashed

Sun Aug 07, 2022 12:10 pm

Re: CCR2004-16G-2S+ — Critical Program Crashed

Sun Aug 07, 2022 12:29 pm

Yes and no.
The purpose of the UPS module should be to monitor the UPS and alert when needed, not to CRASH when UPS is down.

Or am I completely misunderstanding how all this is supposed to work

Источник

System error critical router rebooted because some critical program crashed

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

Источник

Народ, у всех Mikrotik уходит в ребут если пускать через него zmap?

Каждый раз при запуске zmap на адреса из wan сегмента (запускаю с хоста расположенного в lan сегменте) Микротик ребутается
Проверял на: RouterOS 6.30.4 и 6.31

Настройки топорные:
/interface ethernet set ether1 name=ether1-gateway
/interface ethernet set ether2 name=ether2-local

/interface bridge add name=bridge-local disabled=no auto-mac=no protocol-mode=rstp
/interface bridge set «bridge-local» admin-mac=[/interface ethernet get ether2-local mac-address]
/interface bridge port add bridge=bridge-local interface=ether2-local

/ip dhcp-client add interface=ether1-gateway disabled=no

/ip address add address=192.168.88.1/24 interface=bridge-local
/ip pool add name=»default-dhcp» ranges=192.168.88.10-192.168.88.254
/ip dhcp-server add name=default address-pool=»default-dhcp» interface=bridge-local lease-time=10m disabled=no
/ip dhcp-server network add address=192.168.88.0/24 gateway=192.168.88.1
/ip dns static add name=router address=192.168.88.1>

/ip firewall nat add chain=srcnat out-interface=ether1-gateway action=masquerade

zmap запускаю с хоста подключенного к ether2-local: zmap -B 10M -p 80 -o jus_test_22.csv x.x.0.0/16
x.x.0.0/16 — wan segment
Через 1-2 секунды роутер уходит в ребут.

После ребута в логах:
system,error,critical System rebooted because of kernel failure
system,error,critical router was rebooted without proper shutdown

Источник

System error critical router rebooted because some critical program crashed

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

Источник

System error critical router rebooted because some critical program crashed

связь пропадает с микротиком пропадает от 10 минут до 2 часов, всё это время инет работает стабильно.

внутренней памяти в микротике свободно 76%, загрузка проца порядка 25-40% (опять таки не постоянно, но выше 40 не наблюдал)

ИМНО не может инет через ADSL нагрузить проц 750 до 40%.
Что-то не то у вас настройками или самим микротиком.

У меня дома у самого ADSL+Mikrotik — не видел я больше 10%. При этом каждый день что-качается и раздается. Среднее количество коннектов 200-270.

Даже если вы от АТС через дорогу живете, то у вас в лучшем случае 20 мегабит Down и 1,8 мегабита UP и это только в идеальных условиях. И такие скорости не могут вогнать микротик в 40%, а уж выше тем более.

А достучаться вы до него не можете, потому-что весь UP канал от микротика забит торрентами. Ограничивайте скорость исходящего трафика в торрент-клиенте и, скорее всего, все ваши проблемы прекратятся. Все равно в суперсиды с ADSL вам не пробиться.

микротик до этого был прошит на 6.0с какую то версию, и работал стабильно полгода, где в июне начал тупить не подетски, но только щас меня начало это доставать как надо и в итоге я тут, попробывал перепрошить до 6.1, ничего не изменилось, разве что лишняя строчка в логах появилась.

если честно, то вот щас я в шоке, с 11 ip есть не большая зачка с торента (начальник качает что-то), порядка 78-125 пакетов прыгает.

среди настроек ничего не добавлялось, как один раз настроил, так и пашет уже полгода.

но вы то один родный юзаете данный девайс, я правильно понимаю?

вчера вечером наблюдал 100% нагрузку проца при 1000+ коннектов, причём свыше 500 это были входящие запросы на 53 порт, 30 минут аптайма при такой нагрузке, и миктротик ушёл в даун (не мог подключиться по удалёнке), хотя при этом внешний ip пинговался без проблем. При этом стоит заметить что ширина входящего канала на микротик не был забита на 100% по пропускной способности.

сейчас висит 200-350 коннектов, нагрузка на проц порядка 9-35%, множественных коннектов на 53 порт из вне нету, но аптайм не превышает 2-3 часов.
возникает вопрос, как правильно разрулить данную нагрузку, и тем более вопрос почему микротик уходит в даун даже при такой нагрузке?

Источник

• 3 weeks later…

• 3 years later…

• 2 months later…