I've had a Centos 5.3 zimbra mailserver set up for about 3 months now.Every 7-10 days or so, the system will do a kernel panic and I've been putting off its resolution due to other matters.I'm now ready to look into it but I have two issues :
1) No logs.
So far, I've manually rebooted when a kernel panic occured and could look at the panic printout and write down relevant info. But since I wanted more info than I had written down, I went hunting in the logs for the kernel panic event (one happened earlier today) but, to my surprise, I noticed the system doesn't log the kernel panic at all. Kdump is currently disabled as I'd like to keep all available memory available to the system but I was under the impression it would log the kernel panic message regardless but would simply leave out more advanced diagnostic information.How would I make sure the kernel panic is logged so I can have more info about it ?
2) The actual panic.Here's a snippet of what's appearing when the kernel panics :
I've also seen f793bee4 instead of the highlighted part above but everything else is always the same from the times I've seen (as I haven't always had the chance to be around when a panic occured).I'm looking further into it at this point but early research seem to indicate this could be a memory issue. I'll run memtest next weekend to check that out (since I don't want to take the system offline for any length of time during office hours) but people here might have other theories based on what I've put up so far. The system has all of the latest patches and updates and is running only what I need as far as software goes (zimbra server + prerequisites, x + GNOME (not loaded on startup), firefox and vnc for windows RDP access). My system also uses a software RAID1 array (boot = md0 and / = md2 with swap files not being mirrored as there's no need to).
PS : In order to further troublehsoot by myself before posting here, I've tried to enable kdump to see if kdump is the culprit for the missing logs but I'm also having an issue with it. I'm getting a "No kdump initial ramdisk found" and "mkdumprd: failed to make kdump initrd" messages at startup. I'm thinking this might be because of my raid array ? I've found an old bug report regarding one of those error messages on centos 5.2 but it was supposedly fixed in the 30 version by RH and I'm using the latest one (56).
When my server starts I received this text:No kdump kernel image found:[WARNING]Tried to locate /boot/vmlinuz-2.6.18-164.6.1.el5.centos.plusLoading kdump:[FAILED]
I'm posting because I've read everything I can find on google and in the forum and the man page and still can't get it to work. I did read the FAQ, I hope I have adhered to it.I've tried several things and I don't remember exactly everything I tried and in what order.I've got several (12) HP ProLiant DL140 G3 servers running CentOS 5 that lockup about once a week. These are in a remote colo cage so I all i have access to is the built-in HP lights-out management interface, which includes a console, and ssh. I've been trying to get kdump setup to try to figure out what's going on. As an aside, if I run top on the console (via the management interface) the servers stay up for about a week, if I don't run top they crash within about 48 hours.I've used yum update to update to the latest available kernel (2.6.18-194.26.1.el5.x86_64) and installed the debuginfo and debuginfo-common RPMs from http://debuginfo.centos.org/5/x86_64/I have a single command in the /etc/kdump.conf file:ext3 /dev/sda5
I use CentOS 5.3 with kernel 2.6.18-128.1.6.el5 for Clonezilla. It would be simpler for me if any of IDE or SATA drives detects as /dev/sdX device. Because when I cloning computers with Clonezilla it is matter which type of drive connected to cloned computer. So I must firstly clone computers with IDE drives, after that with SATA drives. If all drives would detected as /dev/sda I would can clone all computers at once! Is there simple way to enable new libata library without recompiling kernel? Is there already compiled kernels with this feature?
I have read that when using xfs with lvm2, prior to kernel 2.6.29 write barriers are by deffault disabled.As i want to migrate /home to xfs (and create a external partition to hold some data in xfs too) i was thinking in compile a custom kernel 2.6.30 or higher from [URL].I have read the wiki, all the warnings , and that for compile a kernel.org kernel you should use the Linux Kernel in a Nutshel guide/book. But i don't really know if would worth do that only to have write barrier support , more when in one month i will buy a ups to be sure i can shutdown the pc well if the power goes out.Should i enable write barriers on xfs with lvm2 ,although going to have a ups ?
I have a dumb question but the google can't seem to answer it. When (if?) my host locks up (RHEL 5.4) I generally don't get anything in /var/crash . kdump is configured correctly and works (if tested using ` echo "c" > /proc/sysrq-trigger` as per Red Hat's KBase article) but in the real world, when the system locks up nothing ever ends up there.
So, on to the dump ( ) question - I have to crash it using Ctrl + SysRq in order to get anything out of this, right. If the box is comatose and doesn't respond at all to the point of being power cycled, it's all gone isn't it? Volatile memory being what it is and all; or is there some sort of magic / voodoo in place that makes it survive the reboot. And no, my Dell PowerEdge 1950 doesn't have battery backed RAM, so i'm quite sure that unless i can kill it through sysrq ...
I would like to set up Kdump in case my machine crashes (and it still does frequently) to send the message to putty running on my windows machine (or to my other server running fedora 8).
My preference goes to the windows machine, but I have no clue how to set it up. Is it possible to get the "screen dump" on my windows putty?
My server crashes downloading torrents at high speeds (which is kind of what I want to do)
I'm having some issues creating output from kdump-tools. (Initially to diagnose some system freezes when using wine, but now I can't a staged panic to work and provide proper output.)
I initially started following what is stated at this link: https://www.bentasker.co.uk/documentati ... ian-jessie
I recently installed Deluge 1.2.0 from the following PPA:[URL]I using this on two different Linux computers. One is running Linux Mint 8 and the other is running Ubuntu Netbook Remix 9.10. The first time on either computer when I enable WebUI in the Deluge GUI it works fine. However if I ever disable it in plugins section I am subsequently unable to re-enable it (doesn't appear in the side panel again). Rebooting or reinstalling Deluge seems to have no effect.Is this a bug or am I doing something wrong?
Anyone can tell me how to enable and config auditd in linux kernel 2.6.9-5.EL. I have only found command auditd and auditctl in server that run kernel 2.6.9-5.EL. I ran auditd & and can saw auditd ran in my server. But I couldn't do anything with auditctl, no status, no rules, nothing :| . I tried to find audit.rules or auditd.conf but that nothing I can find.
in Ubuntu 10.04 I have updated my system with command: sudo apt-get dist-upgrade and I see new kernel was installed. Now restart is required. I don't like to restart this computer, because it should be up and running as much time as possible. Is there any way I could only re-run some kind of kernel module or something like that instead of restarting whole computer?
Running lucid in wubi and had issues with a wiggling screen on the 2.6.32 kernel. i update to 2.6.34-020634rc6. The wiggling stopped, but now I can't get even the normal setting to work (goes straight to "searching for drivers").
after update to kernel-2.6.18-164.el5 one of the 2 NIC's of my machine are only found at 1 of 4 reboots. Using the old one kernel-2.6.18-128.7.1.el5 all is fine. This are the to NIC's:
I compiled my kernel, compiled scsi support into kernel, used the new kernel and initrd, the boot failed.Then ,i unzip my initrd, found that sd_mod.ko can't be insert, i added it manual, and reboot OK.so, why! in the kernel configure , the sd_mod.ko is set to <M> , but why it can't be found in initrd?
The server runs# uname -r2.6.18-128.4.1.el5However, today I executed yum update kernel*due to security advisory. I was just about to reboot the system when I realized that it runs VMWare Server Instance that will most likely fail to restart after kernel upgrade (I had a hard time fixing it after previous kernel update). Now I want to keep 2.6.18-128.4.1.el5 after reboot.I see that new kernel is scheduled for booting:
I am running Lucid Lynx kernel 2.6.32.24. Soon after the latest kernel update I noticed that Virtualbox would not launch when I clicked on the icon. I have searched the Internet for days, tried numerous possible fixes, over hours of effort, but can't get it working at all. Ubuntu Lucid runs great!! There are no errors just a few blinks of the hard drive indicator and nothing. Is there anyone out there that has seen this same issue?
I'm running CentOS 5.3 and would like to know what the "best" or "proper" method is to build a custom kernel using the generic kernel sources from kernel.org. Most of the references I've found talk about modifying the current CentOS kernel using the RPM way. I really want to have the latest kernel due to some important security issues that haven't been addressed in the current CentOS 5.3 kernel.
I have done a new install of Fedora 14 but the RTL8191 wirless card is not being recognised. Realtek have provided the driver source but the make operation is failing because (I think) Fedora 14 isn't provided with the kernel source to enable it to complete successfully.
Basically (in easy to understand steps): how do I download correctly the Kernel source to enable the driver make operation to proceed?
I have a post at X86_64 but I still don't see any light there, hope some here could give me some info about HugeTLBFS on CentOS 5.x. This is the thread:
I transfer my dedicated to another i put same version on it php 5.2.9 and ldap module installed but couldnt activate it on new server is there something i missing ?
The first server I installed installed fine. The second server, installed with the same config, went to "kernel panic not syncing no init found try passing init= option in kernel" error. I tried reinstalling but it keeps going to that error after install reboot. The storage is ISCSI connected via Intel Server Adapter, which allows it to boot from ISCSI. Not sure if that's the cause for the problem, but the first server is connected to the same ISCSI and installed just fine.
Is there a way that I can make sure ISCSI module installs during installation? Although I think it is installed since it's able to copy the files and setup /dev/sda. I just wana make sure that it installs during setup.
I built a home server (NAS/WWW/SSH/media server etc) and chose CentOS 5 as the OS (stability, easy of configuration).I was just about to start tuning the power consumption when I realised that the kernel CentOS uses is so "old" that it does not support the latest reduced power consumption enhancements that Linux has achieved in big strides in the recent past (we are probably still talking 6-12+ months ago e.g. tickless kernel)..
So my questions; 1) I know CentOS was maybe not meant for home servers (certainly its not its primary purpose), but if it is, any ideas of what kind of power consumption it takes (I know its relative) and if there are particular power consumptions that are worthwhile?
2) Do you recommend me compiling my own 2.6.21+ kernel from kernel.org or am I just likely to have compatibility issues (I really did not want to do that) or when is CentOS 5.4 supposed to have a newer 2.6.21+ version kernel?
Was it wrong of me in principle to choose CentOS for a home server when I am power conscious? (I don't have a low-power VIA processor either but a P4 so I am really just hoping to make do with software changes).
I am an old days RH release user(from 6.x) and just switching back from Debian/Ubuntu to CentOS on some servers, but I can not understand the kernel update strategy currently enabled in CentOS.There are two boxes, with almost identical installation, but recently there was an auto update of kernel on one box. This auto update also seems to issue an auto reboot on the machine, which is unacceptable on server machines.
I'm setting up a raid 5 on several hard disks with a layer of lvm on top for good measure.I know the recent kernels support growing software raid, but since centos runs 2.6.18, I wanted to make sure it'll work. Does the centos kernel support growing raid devices?
I want to enable quota on my centos 5.5, I've tried and it showed correctly quotacheck but when i rebooted the machine it showed me an error saying that fsck.ext3: no such file or direcotory while trying to open /dev/VolGroup00/LogVol00 below are my fdisk and fstab file. how can I enable quota based on below configuration. otherwise may be I have to reformat the machine..n it'll be really painfull for me.
[root@drikdhaka ~]# fdisk -l Disk /dev/hda: 82.3 GB, 82348277760 bytes 255 heads, 63 sectors/track, 10011 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
A problem with installing CentOS 5.3 from DVD ... I downloaded the CentOS-5.3-i386-bin-DVD.iso, after recording an image on DVD Start the installation, selecting Installation Method, chose Local CDROM - Message on my screen: "CD Not Found"