Discuss

discuss@lists.centos.org

5 participants
34752 discussions

RE: [CentOS] Centos-4 Kernel pannic
by Bob Pierce 13 Apr '05

13 Apr '05

I think we might be interested in trying that new kernel. I will be upgrading the Server BIOS and SCSI RAID Firmware this morning, then we'll wait and see. If that doesn't help I think are next steps will be a new kernel and a memory scan. Thanks for your help, Bob. -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Johnny Hughes Sent: Wednesday, April 13, 2005 7:18 AM To: CentOS ML Subject: Re: [CentOS] Centos-4 Kernel pannic On Wed, 2005-04-13 at 07:47 -0400, James Olin Oden wrote: > This is not necessarily a problem with your hardware but could be a > bonified bug in the megaraid device driver. Looking at the changelog for the new kernel (from 2.6.9-5.0.3.EL up to 2.6.9-6.37.EL), there are several megaraid and/or scsi device driver changes ... may be fixed w/the new kernel.

1 0

Centos-4 Kernel pannic
by Bob Pierce 13 Apr '05

13 Apr '05

Hi all, We are running a new Centos-4 server, and it has kernel panicked on us 4 times in the last month. After the first kernel panic we hooked up a serial console to the server and captured the output in order to have a record of what happens. I've included the error messages from the last time it locked up... but it doesn't really mean much to me. Anybody have any ideas what might be causing this server lock up? Server description: -Dell PE1750 - dual 2.8Ghz Xeon (with Hyper Threading on) - 2GB DDR RAM - Perc4-DI onboard RAID using 3 scsi drives in raid-5 configuration -ext3 file system -kernel-smp-2.6.9-5.0.3.EL -mysql - from distribution -2 postfix instances rebuilt with MySQL support -amavisd-new -clamav -spamassassin -rbldnsd -bind Here's the captured output from a serial console connected to the server at time of fault. Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: f8872da8 *pde = 35562001 Oops: 0000 [#1] SMP Modules linked in: md5 ipv6 autofs4 sunrpc dm_mod button battery ac ohci_hcd tg3 floppy sg ext3 jbd megaraid_mbox megaraid_mm sd_mod scsi_mod CPU: 1 EIP: 0060:[<f8872da8>] Not tainted VLI EFLAGS: 00010246 (2.6.9-5.0.3.ELsmp) EIP is at __journal_file_buffer+0x1b/0x221 [jbd] eax: 00000000 ebx: d2fff26c ecx: 00000008 edx: c2327680 esi: c2327680 edi: 00000008 ebp: 00000000 esp: f7533dd4 ds: 007b es: 007b ss: 0068 Process kjournald (pid: 210, threadinfo=f7533000 task=f75825b0) Stack: 00000000 00000000 f148fad8 f7f66200 d2fff26c c2327680 f887351b 00000286 00000000 00000000 00000000 00000000 00000000 d2517e6c f7f66200 caa4c50c 00001f18 00000000 f75825b0 c011e8d2 f7533e44 f7533e44 f750c054 f8836f24 Call Trace: [<f887351b>] journal_commit_transaction+0x310/0xfb1 [jbd] [<c011e8d2>] autoremove_wake_function+0x0/0x2d [<f8836f24>] megaraid_isr+0x1ad/0x1bf [megaraid_mbox] [<c011e8d2>] autoremove_wake_function+0x0/0x2d [<c011bcd5>] finish_task_switch+0x30/0x66 [<c02c4363>] schedule+0x833/0x869 [<c0127e62>] del_timer_sync+0x7a/0x9c [<f8875e6d>] kjournald+0xc7/0x215 [jbd] [<c011e8d2>] autoremove_wake_function+0x0/0x2d [<c011e8d2>] autoremove_wake_function+0x0/0x2d [<c011bd1d>] schedule_tail+0x12/0x55 [<f8875da0>] commit_timeout+0x0/0x5 [jbd] [<f8875da6>] kjournald+0x0/0x215 [jbd] [<c01041f1>] kernel_thread_helper+0x5/0xb Code: 14 ba 01 00 00 00 83 c4 10 89 d0 5b 5e 5f 5d c3 55 31 ed 57 89 cf 56 89 d6 53 53 53 89 c3 c7 44 24 04 00 00 00 00 8b 00 89 04 24 <8b> 00 a9 00 00 08 00 75 29 68 d4 85 87 f8 68 9b 07 00 00 68 55

9 9

CentOS-announce Digest, Vol 2, Issue 6
by centos-announce-request＠centos.org 13 Apr '05

13 Apr '05

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2005:365 Important CentOS 4 i386 and x86_64 gaim - security update (Johnny Hughes) 2. CESA-2005:365: Important CentOS 3 i386 gaim - security update (Tru Huynh) 3. CESA-2005:365: Important CentOS 3 x86_64 gaim - security update (Tru Huynh) 4. CESA-2005:021: Moderate CentOS 3 x86_64 kdegraphics - security update (Tru Huynh) 5. CESA-2005:021: Moderate CentOS 3 i386 kdegraphics - security update (Tru Huynh) 6. CESA-2005:365 Important CentOS 4 ia64 gaim - security update (Pasi Pirhonen) 7. CESA-2005:365 Important CentOS 3 ia64 gaim - security update (Pasi Pirhonen) 8. CESA-2005:021 Moderate CentOS 3 ia64 kdegraphics - security update (Pasi Pirhonen) 9. CESA-2005:365 Important CentOS 3 s390(x) gaim - security update (Pasi Pirhonen) 10. CESA-2005:021 Moderate CentOS 3 s390(x) kdegraphics - security update (Pasi Pirhonen) 11. CESA-2005:021-01: Moderate CentOS 2 i386 kdegraphics security update (John Newbigin) 12. CESA-2005:212-01: Moderate CentOS 2 i386 dhcp security update (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Tue, 12 Apr 2005 10:08:29 -0500 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2005:365 Important CentOS 4 i386 and x86_64 gaim - security update To: centos-announce(a)centos.org Message-ID: <1113318509.21916.9.camel(a)myth.home.local> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2005:365 - Important i386 and x86_64 gaim security update for CentOS-4. http://rhn.redhat.com/errata/RHSA-2005-365.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: gaim-1.2.1-4.el4.i386.rpm x86_64: gaim-1.2.1-4.el4.x86_64.rpm src: gaim-1.2.1-4.el4.src.rpm You can update your gaim with the command: yum update gaim -- Johnny Hughes

1 0

Installing grub to floppy image
by James Olin Oden 13 Apr '05

13 Apr '05

Does anyone know of a way to have grub install to a floppy image rather than a real floppy device? Thanks...james

2 2

Firefox problems
by James B. Byrne 12 Apr '05

12 Apr '05

Since upgrading to FireFox 1.0.2 I have noticed a large number of problems connecting to web sites that are reached without difficulty using MS-IE 6. The symptom is a message box that declares that the "The Document Contains No Data" which, ironically enough, is the very error I get when trying to reach http://www.google.ca/url?sa=U&start=1&q=http://kb.mozillazine.org/Do cument_contains_no_data&e=10167 using Firefox. I ended up getting it in MS-IE. Is it just me or did the last release of Firefox significantly degrade its reliability. When I close Firefox with multiple tabs I now nearly always get an error that attempts to mail itself off to Mozilla. After several dozen of these I just close them now. I have removed and re-installed Firefox several times without relief. I have these same problems on at least two different machines that I use, one running Win2Kpro and the other Win XPpro. I am not looking for a fix here, but I was wondering if anyone had further information on the subject that they are willing to share. Regards, Jim -- *** e-mail is not a secure channel *** mailto:byrnejb.<token>@harte-lyne.ca James B. Byrne Harte & Lyne Limited vox: +1 905 561 1241 9 Brockley Drive fax: +1 905 561 0757 Hamilton, Ontario <token> = hal Canada L8E 3C3

3 2

Warning: Kernel pressures approaching maximum tolerance limit
by Mickael Maddison 12 Apr '05

12 Apr '05

Hello CentOS, I'm seeing this in the logwatch output. Anything I find on the net hasn't been definitive. The system is an x-less server. --------------------- Kernel Begin ------------------------ WARNING: Kernel Errors Present vesafb: probe of vesafb0 failed with error -6...: 6 Time(s) ---------------------- Kernel End ------------------------- -- Best regards, Mickael mailto:mike@kamloopsbc.com

2 1

Re: Re: mkbootdisk!
by israel.garcia＠cimex.com.cu 12 Apr '05

12 Apr '05

On Sat, 2005-04-02 at 08:55 -0500, israel.garcia(a)cimex.com.cu wrote: > I'm trying to make a bootdisk in my CentOS server and I got this error.. > > any ideas? > > > [root@server:~]$ rpm -qa kernel kernel-2.6.9-5.0.3.EL > [root@server:~]$ mkbootdisk 2.6.9-5.0.3.EL --device > /dev/fd0 Insert a disk in /dev/fd0. Any information on the disk will be > lost. Press <Enter> to continue or ^C to abort: > cp: writing `/tmp/mkbootdisk.d20227/initrd.img': No space left on device > cat: write error: No space left on device > cat: write error: No space left on device > 20+0 records in > 20+0 records out On Apr 2, 2005 5:23 AM, Johnny Hughes <mailing-lists(a)hughesjr.com> wrote: >>The kernel and initrd are too big to fit on a floppy ... there is no >>option to boot them from floppy any more. Johnny, If I can not use a floppy any more to boot my server, What can I use to boot the server in case of a crash? How can I make a CD bootdisk to my CentOS Server? Is there another way to boot my server? regards; Israel

4 3

Upgrading to 2.6.11
by Jerry Geis 11 Apr '05

11 Apr '05

What would be the proper steps to upgrade to 2.6.11 on centos 4.0 This is what I think... tar -zxvf linux-2.6.11.6.bz2 cd linux-2.6.11.6 make oldconfig - enter for all choies presented vi .config - change 8250_NR_UARTS to 36 to support 4 - 8 port rs232 cards make bzImage make modules_install mkinitrd /boot/initrd-2.6.11.6 2.6.1.6 cp -f arch/i386/boot/bzImage /boot/vmlinux-2.6.11.6 edit /etc/grub.conf Is this the correct procedure? Thanks, Jerry

3 2

trouble booting the system with I2O hardware RAID
by Aleksandar Milivojevic 11 Apr '05

11 Apr '05

I've just made (yet another) CentOS 4 installation. The install process seems to go fine, however the machine doesn't wan't to boot. The system in question has one of I2O Adaptec RAID controllers. I've configured LVM with one volume group and several volumes. If I boot into the rescue mode, all looks fine and dandy. Anaconda finds the installation, and I can access all volumes. However, when doing "real" boot, it gets into trouble. All required modules are loaded from initrd image (as far as I can tell). The I2O modules are able to locate the RAID devices (I see all partitions reported: /dev/i2o/hda1 (unused), /dev/i2o/hdb1 (/boot), and /dev/i2o/hdb2 (rest of the system under LVM). The only thing different from rescue mode is that i2o/hda and i2o/hdb are reversed (this is strange, but it shouldn't affect things since /boot partition has a label "/boot", and all the rest is under LVM, so everything should be device name independent). I have no idea why i2o device drivers behave differently when loaded from initrd image during boot, and by Anaconda during installation. The last couple of messages printed on the screen are: Creating root device Mounting root file system kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. mount: error 2 mounting none Switching to new root WARNING: can't access (null) exec of init ((null)) failed!!!: 14 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! Looking at the "init" script from initrd image, this correspond to: echo Mounting root filesystem mount -o defaults --ro -t ext3 /dev/root /sysroot mount -t tmpfs --bind /dev /sysroot/dev echo Switching to new root switchroot /sysroot umount /initrd/dev Which would indicate that mount of root file system went OK, but then it failed to mount /dev filesystem (basically, move already mounted /dev to /sysroot/dev). After the switchroot /sysroot, old /dev mount point become invalid (non-accessible), the new /dev mount point was not there and of course everything broke from that point on. I've Googled around a bit, and the only relevant thing Google gave me was this French page. There were couple of more pages with similar but different problem (modules failing to load and/or detect disk drives, which is not the case here, all modules were loaded correctly as witnessed by successfull LVM initialization and successfull root file system mount). http://www.fedora-france.org/modules/newbb/viewtopic.php?topic_id=3838&foru… I do live in Canada, but don't speak a word of French (shame on me, but in my defense it is on my todo list). However I did managed to figure out somebody suggested going with Grub instead of LILO. IMO, Grub or LILO shouldn't make any difference, since the error is happening way after boot loader did its job. Anyhow, just for fun, I reinstalled the system from scratch, this time choosing Grub as boot loader of choice to be installed into MBR. However, for whatever reason, Anaconda did not install Grub (dd & less showed no signs of Grub in MBR). Boot into the rescue, chroot, grub-install, OK now I have Grub in MBR. But again, no joy. Grub doesn't even start and system simply hangs in mid-air. No errors printed, no anything. Currently, I'm kind of stuck and idea-less. The system did worked perfectly in the past with Red Hat 7.3 (and LILO as boot loader), and exactly the same hardware RAID configuration (two volumes, one for system, one for data). Any help, hint, etc would be greatly appriciated. -- Aleksandar Milivojevic <amilivojevic(a)pbl.ca> Pollard Banknote Limited Systems Administrator 1499 Buffalo Place Tel: (204) 474-2323 ext 276 Winnipeg, MB R3T 1L7

1 1

CentOS Firewall can handle multi IP?
by Franki 11 Apr '05

11 Apr '05

Hi guys, Just a quick question. Can RHEL4/CentOS built in firewall handle multiple IP's bound to one interface? For example on one of my boxes out there I have 64 IP's bound to an interface used in virtual hosting. I searched long and hard for a easy and useable solution without much success. I ended up rolling my own, but it's a hack. Was wondering if CentOS has any answers for me in that regard. rgds Franki

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss