Amazon web services 无法使用kdump保存崩溃转储

我在亚马逊的AWS Lightsail服务上有一个VPS服务器。 我一直在使用以下两个命令测试kdump（以触发自动内核崩溃）：

问题是系统崩溃并重新启动，但没有保存转储

以下是我所做的检查列表：

[centos@server crash]$ systemctl status kdump
● kdump.service - Crash recovery kernel arming    
  Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled)    
  Active: active (exited) since Mon 2019-03-18 07:43:34 UTC; 5 days ago   
 Process: 4119 ExecStart=/usr/bin/kdumpctl start (code=exited, status=0/SUCCESS)  
Main PID: 4119 (code=exited, status=0/SUCCESS)    
  CGroup: /system.slice/kdump.service

Mar 18 07:43:32 ip-.ap-northeast-1.compute.internal systemd[1]: Starting Crash recovery kernel arming...
Mar 18 07:43:34 ip-.ap-northeast-1.compute.internal kdumpctl[4119]: kexec: loaded kdump kernel
Mar 18 07:43:34 ip-.ap-northeast-1.compute.internal kdumpctl[4119]: Starting kdump: [OK]
Mar 18 07:43:34 ip-.ap-northeast-1.compute.internal systemd[1]: Started Crash recovery kernel arming.


[centos@server crash]$ dmesg | grep Reserving
[    0.000000] Reserving 256MB of memory at 368MB for crashkernel (System RAM: 2047MB)


[centos@server crash]$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.10.0-957.1.3.el7.x86_64 root=UUID=f41e390f-835b-4223-a9bb-9b45984ddf8d ro console=tty0 crashkernel=256M console=ttyS0,115200

[centos@server crash]$ grep -v ^# /etc/kdump.conf
path /var/crash
core_collector makedumpfile -l --message-level 1 -d 31
default reboot

/var/log/messages

中没有崩溃日志，表明可能存在任何错误。所以我想知道我可能错过了什么。或者AWS Lightsail VPS根本无法保存kdump…？

我想不出Lightsail实例无法保存崩溃转储的明显原因。在光伏环境中，afaik无法实现，但Lightsail不是光伏——它是HVM。Lightsail是“ec2 lite”，您没有那么多可用的工具——比如控制台屏幕截图和ec2中可以使用的工具。如果您倾向于对此进行详细的故障排除，请使用相同的操作系统创建一个实际的EC2

t2

实例，并查看您的设置是否在那里工作。如果不是，EC2工具可能会很有用。

[centos@server crash]$ systemctl status kdump
● kdump.service - Crash recovery kernel arming    
  Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled)    
  Active: active (exited) since Mon 2019-03-18 07:43:34 UTC; 5 days ago   
 Process: 4119 ExecStart=/usr/bin/kdumpctl start (code=exited, status=0/SUCCESS)  
Main PID: 4119 (code=exited, status=0/SUCCESS)    
  CGroup: /system.slice/kdump.service

Mar 18 07:43:32 ip-.ap-northeast-1.compute.internal systemd[1]: Starting Crash recovery kernel arming...
Mar 18 07:43:34 ip-.ap-northeast-1.compute.internal kdumpctl[4119]: kexec: loaded kdump kernel
Mar 18 07:43:34 ip-.ap-northeast-1.compute.internal kdumpctl[4119]: Starting kdump: [OK]
Mar 18 07:43:34 ip-.ap-northeast-1.compute.internal systemd[1]: Started Crash recovery kernel arming.


[centos@server crash]$ dmesg | grep Reserving
[    0.000000] Reserving 256MB of memory at 368MB for crashkernel (System RAM: 2047MB)


[centos@server crash]$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.10.0-957.1.3.el7.x86_64 root=UUID=f41e390f-835b-4223-a9bb-9b45984ddf8d ro console=tty0 crashkernel=256M console=ttyS0,115200

[centos@server crash]$ grep -v ^# /etc/kdump.conf
path /var/crash
core_collector makedumpfile -l --message-level 1 -d 31
default reboot