Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've got a box that's been rebooting itself and we are trying to determine why. I'm trying to config diskdump, but the problem I've got is there's no available local space on the box, and swap is an LVM partition (I was not the one that built the box, sadly.) I'm guessing there's no way to configure diskdump to utilize an LVM partition? Any suggestions would be greatly appreciated.
OS: RedHat Enterprise Linux ES 4
Kernel: 2.6.9-34.ELsmp x86_64
Installed: diskdumputils-1.4.1-7.x86_64.rpm & crash-4.0-5.0.0.2.x86_64.rpm
The other issue, I'm not certain scsi_mod is supported:
This may not be exactly what your looking for but if the box has a serial port on it you could do the following, I have used these steps to diagnose kernel crashes before:
* Buy a Null Modem cable
* Link the null modem cable between the server thats crashing and another machine (this second machine will require some terminal software (minicom on linux, hyperterm on windows))
* Add the following to the grub.conf on the end of the appropriate kernel line your booting from
Quote:
console=tty0 console=ttyS0,9600n8
So this
Quote:
title Red Hat Linux (2.4.9-21)
root (hd0,0)
kernel /vmlinuz-2.4.9-21 ro root=/dev/hda6
initrd /initrd-2.4.9-21.img
would becomme this
Quote:
title Red Hat Linux (2.4.9-21)
root (hd0,0)
kernel /vmlinuz-2.4.9-21 ro root=/dev/hda6 console=tty0 console=ttyS0,9600n8
initrd /initrd-2.4.9-21.img
This will cause console output to be logged to the serial port as well as the main display. Finally set the second machine to log any data received from the serial port to a file. You may be able to push the serial port speed higher if you need that 115200 for example as a baud rate.
If the system crashes after this the second machine should capture any output about the crash.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.