Cannot start kdump

Question

I'm trying to make a dojo xhrGet request using basic authentication but I keep getting 403 forbidden error. I can make the request with curl from the command line, so I know my credentials are valid. When I check the request headers, the Authorization: Basic header isn't even being set. What am I doing wrong:

    var lookupArgs = {
     url: "https://myendpoint.com/myapi/endpoint",
     user:"[email protected]",
     password:"mypassword",
     handleAs: "text",
     load: function(data) {
         content_node.innerHTML = data;
     },
     error: function(error) {
         content_node.innerHTML = error;
     }
 }
dojo.xhrGet(lookupArgs);

Request Header:

GET /myapi/endpoint HTTP/1.1
Host: myendpoint.com
Connection: keep-alive
Origin: http://my-origin
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3315.3 Safari/537.36
Content-Type: application/x-www-form-urlencoded
Accept: */*
Referer: http://my-origin
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9

Solution 1

title CentOS (2.6.18-308.el5)
        root (hd0,0)
        kernel /vmlinuz-2.6.18-308.el5 ro root=LABEL=/
crashkernel=128M
        initrd /initrd-2.6.18-308.el5.img

It looks like you put the crashkernel parameter into a new line. This is the reason for Kdump is not operational message. All the kernel parameters must to be put on the same line as kernel:

title CentOS (2.6.18-308.el5)
        root (hd0,0)
        kernel /vmlinuz-2.6.18-308.el5 ro root=LABEL=/ crashkernel=128M
        initrd /initrd-2.6.18-308.el5.img

After reboot, take a look at the /var/log/messages, you'll see something like this:

localhost kdump: kexec: loaded kdump kernel
localhost kdump: started up

and:

# /etc/init.d/kdump start
Starting kdump:                                            [  OK  ]
# /etc/init.d/kdump status
Kdump is operational

---

kdump: No crashkernel parameter was specified or crashkernel memory reservation failed
kdump: failed to start up

According to this document, try this:

crashkernel=128M@16M

Solution 2

Your crashkernel is too small. Try 256M, 384M, or even 512M. The message 'Memory for crashkernel ... is not within permissible range" is telling you that.

Comments

[Greg Petersen]

Or should I change the code ro root=LABEL=/ into ro root=/dev/sda3? --> DON'T do that without understanding.

[Pelang]

yes. i check that =/ refers to where the kernel is located base on /boot. thanks for reminding

[Pelang]

I edited the grub.conf to make the crashkernel in one line. but there is still error in /var/log/messages. I add the errors as additional info on the question above.

[Greg Petersen]

How about this crashkernel=128M@16M?

[Greg Petersen]

128@16M or 128M@16M?

[Greg Petersen]

Show us the new /var/log/messages after changing (from this line Kernel command line...)?

[Greg Petersen]

let us continue this discussion in chat

[Pelang]

Just need to make a reboot to make things work. Running the kdump on the current session without rebooting after the changes will still return the same error.

[Admin]

That 128M@16M was the missing piece, putting it in solved the issue and kdump has started.

[Admin]

based on documentation, 64 should be enough for 12GB RAM. But taking into account other missing information it is probably the documentation that needs tweaking...