Not able to save crash dump using kdump












0















I have a VPS server on amazon's AWS Lightsail service.
I've been testing kdump using the following two commands(to trigger an automatic kernel crash):



# echo 1 > /proc/sys/kernel/sysrq
# echo c > /proc/sysrq-trigger


The problem is that the system crashed and rebooted, but there's no dump saved.



Here is a list of checking I've done:



[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


There's no log of the crash in the /var/log/messages indicating any error there might be. So I wonder what I might have missed. Or an AWS Lightsail VPS is not capable of saving a kdump at all...?



Thank you so much in advance.










share|improve this question



























    0















    I have a VPS server on amazon's AWS Lightsail service.
    I've been testing kdump using the following two commands(to trigger an automatic kernel crash):



    # echo 1 > /proc/sys/kernel/sysrq
    # echo c > /proc/sysrq-trigger


    The problem is that the system crashed and rebooted, but there's no dump saved.



    Here is a list of checking I've done:



    [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


    There's no log of the crash in the /var/log/messages indicating any error there might be. So I wonder what I might have missed. Or an AWS Lightsail VPS is not capable of saving a kdump at all...?



    Thank you so much in advance.










    share|improve this question

























      0












      0








      0








      I have a VPS server on amazon's AWS Lightsail service.
      I've been testing kdump using the following two commands(to trigger an automatic kernel crash):



      # echo 1 > /proc/sys/kernel/sysrq
      # echo c > /proc/sysrq-trigger


      The problem is that the system crashed and rebooted, but there's no dump saved.



      Here is a list of checking I've done:



      [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


      There's no log of the crash in the /var/log/messages indicating any error there might be. So I wonder what I might have missed. Or an AWS Lightsail VPS is not capable of saving a kdump at all...?



      Thank you so much in advance.










      share|improve this question














      I have a VPS server on amazon's AWS Lightsail service.
      I've been testing kdump using the following two commands(to trigger an automatic kernel crash):



      # echo 1 > /proc/sys/kernel/sysrq
      # echo c > /proc/sysrq-trigger


      The problem is that the system crashed and rebooted, but there's no dump saved.



      Here is a list of checking I've done:



      [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


      There's no log of the crash in the /var/log/messages indicating any error there might be. So I wonder what I might have missed. Or an AWS Lightsail VPS is not capable of saving a kdump at all...?



      Thank you so much in advance.







      centos aws crash core-dump kdump






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 11 mins ago









      xczzhhxczzhh

      2093510




      2093510






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f508251%2fnot-able-to-save-crash-dump-using-kdump%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f508251%2fnot-able-to-save-crash-dump-using-kdump%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          CARDNET

          Boot-repair Failure: Unable to locate package grub-common:i386

          濃尾地震