kdump failed

kdump 
是一种先进的基于 kexec 的内核崩溃转储机制。当系统崩溃时,kdump 使用 kexec 启动到第二个内核。
第二个内核通常叫做捕获内核,以很小内存启动以捕获转储镜像。第一个内核保留了内存的一部分给第二内核启动用。
由于 kdump 利用 kexec 启动捕获内核,绕过了 BIOS,所以第一个内核的内存得以保留。这是内核崩溃转储的本质

查看 /etc/grub.conf文件
发现crashkernel=auto,
如果系统内存 <= 8GB 对kdump kernel不会保留任何内容; 等于关掉了机器上的kdump功能;
如果系统内存  > 8GB 但是<= 16 GB,crashkernel=auto会保留256M,等同于crashkernel=256M
如果系统内存  > 16GB crashkernel=auto会保留512M, 等同于crashkernel=512M

修改:crashkernel=128M

时间: 2024-11-20 05:06:08

kdump failed的相关文章

kdump报错原理及解决方法

kdump是Linux内核崩溃转储机制.在系统崩溃时,kdump创建一个内存映像(vmcore),可以帮助确定崩溃原因.启用kdump需要你通过kdump专用储备系统存储器的一部分.这段内存不可用作其他用途.这和以前的diskdump,netdump是同样道理.cent 5之后的版本出现的. systemctl status kdump [server]-[[email protected] etc]$systemctl status kdump ● kdump.service - Crash

从mdb到crash

在Solaris上,事后分析crashdump或者在线调试操作系统内核的强大工具就是mdb.当然,mdb不支持源码级的调试,只支持汇编级的调试.而在Linux (以CentOS为例),类似的工具是crash. $ man -s8 crash NAME crash - Analyze Linux crash dump data or a live system SYNOPSIS crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile

oracle linux 6.3安装图形界面软件

副标题:oracle linux 6.3无法切换到图形界面处理 1.问题现象 1.1 startx命令不可用 [[email protected] cdrom]# startx -bash: startx: command not found 1.3 init 5无法执行完成 [[email protected] /]#init 5 [[email protected] /]#Calling the system activity data collector(sadc): starting p

mysqld服务启动失败, Failed to restart mysqld.service: Unit not found.

-bash-4.2# service mysqld restart Redirecting to /bin/systemctl restart mysqld.serviceFailed to restart mysqld.service: Unit not found. 并不存在 mysqld 的服务, -bash-4.2# -bash-4.2# chkconfig -list -list: unknown option -bash-4.2# chkconfig --list Note: Thi

Spring Cloud ZooKeeper集成Feign的坑2,服务调用了一次后第二次调用就变成了500,错误:Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is com.n

错误如下: 2017-09-19 15:05:24.659 INFO 9986 --- [ main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.spring[email protected]56528192: startup date [Tue Sep 19 15:05:24 CST 2017]; root of context hierarchy 2017-09-19 15:05:24.858 INFO 9986 --

Hive报错 Failed with exception java.io.IOException:java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative path in absolute URI: ${system:user.name%7D

报错信息如下 Failed with exception java.io.IOException:java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative path in absolute URI: ${system:user.name%7D 解决方法: 编辑 hive-site.xml 文件,添加下边的属性 <property> <name>system:java.io.tmpdir<

View Composer Agent initialization error (16): Failed to activate software license (1026556)

1.       桌面发布过程中偶尔有些桌面池中的桌面提示无法访问代理,查看报错信息如下:View Composer Agent initialization error (16):Failed to activate software license (1026556). KB地址:https://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1026556 主要意思是Windows 7系统激活的

Maven Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean Failed to delete access_log

I'm trying to run simple struts project using maven and tomcat. When I'm trying to exucute next goals:clean install tomcat7:run ,there is an error : [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean)

Applying GI PSU &quot;opatch auto&quot; fails with &quot;The opatch Component check failed&quot;

Applying GI PSU using "opatch auto" fails with "The opatch Component check failed" (文档 ID 1169036.1) APPLIES TO: Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterInformation in this document applies to any platform.***C