Discuss

discuss@lists.centos.org

2 participants
34758 discussions

kernel update inconsistency...
by Maciej Żenczykowski 18 Jan '06

18 Jan '06

Hi, New kernels both up and smp via yum are installed not updated. The same happens for the kernel-devel package -- but the kernel-smp-devel package is updated... Cheers, MaZe.

3 5

HPLIP
by Robert 18 Jan '06

18 Jan '06

First, has anyone successfully installed the HPLIP driver from HP in CentOS4? Second, does that driver really provide the toolbox which includes handy stuff like ink level monitoring? I got the source RPM (hplip-0.9.4-1.1.src.rpm) from an FC4 testing mirror, which rebuilt fine on this machine: . . . + umask 022 + cd /home/rj/rpmbuild/BUILD + cd hplip-0.9.4 + rm -rf /home/rj/rpmbuild/tmp/hplip-0.9.4-buildroot + exit 0 Executing(--clean): /bin/sh -e /home/rj/rpmbuild/tmp/rpm-tmp.54540 + umask 022 + cd /home/rj/rpmbuild/BUILD + rm -rf hplip-0.9.4 + exit 0 [rj@mavis ~]$ su Password: but would not install. [root@mavis rpmbuild]# rpm -ivh ./RPMS/i386/hplip-0.9.4-1.1.i386.rpm error: Failed dependencies: system-config-printer < 0.6.131.3 conflicts with hplip-0.9.4-1.1.i386 hpijs < 1:0.9.4-1.1 conflicts with hplip-0.9.4-1.1.i386 The conflict with hpijs is a no-brainer -- remove it because hplip is a replacement. But what about system-config-printer? I'm not too keen on dropping back to manually setting up printers. Any advice is welcome.

3 5

CentOS-announce Digest, Vol 11, Issue 6
by centos-announce-request＠centos.org 18 Jan '06

18 Jan '06

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-2006:0101 Important CentOS 4 i386 kernel - security update (Johnny Hughes) 2. CESA-2006:0101 Important CentOS 4 x86_64 kernel - security update (Johnny Hughes) 3. CESA-2006:0101 Important CentOS 4 ia64 kernel - security update (Pasi Pirhonen) 4. CESA-2006:0101 Important CentOS 4 s390(x) kernel - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Jan 2006 18:05:51 -0600 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2006:0101 Important CentOS 4 i386 kernel - security update To: CentOS-Announce <centos-announce(a)centos.org> Message-ID: <1137542751.5710.12.camel(a)myth.home.local> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2006:0101 https://rhn.redhat.com/errata/RHSA-2006-0101.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: kernel-2.6.9-22.0.2.EL.i586.rpm kernel-2.6.9-22.0.2.EL.i686.rpm kernel-devel-2.6.9-22.0.2.EL.i586.rpm kernel-devel-2.6.9-22.0.2.EL.i686.rpm kernel-doc-2.6.9-22.0.2.EL.noarch.rpm kernel-hugemem-2.6.9-22.0.2.EL.i686.rpm kernel-hugemem-devel-2.6.9-22.0.2.EL.i686.rpm kernel-smp-2.6.9-22.0.2.EL.i586.rpm kernel-smp-2.6.9-22.0.2.EL.i686.rpm kernel-smp-devel-2.6.9-22.0.2.EL.i586.rpm kernel-smp-devel-2.6.9-22.0.2.EL.i686.rpm src: kernel-2.6.9-22.0.2.EL.src.rpm

1 0

4.2 Lockup on Fujitsu-Siemens Primergy Econel 200
by CM 18 Jan '06

18 Jan '06

Hello everybody, I'm looking for some insights on reproductible lockups with this server so please bear the long description that follows: Installed the 4.0 Centos than yum updated it so it results a 4.2 Centos fully updated. During the instalation and update there were no cold boots. That's important because if (updated Centos or not) you cold boot the server it stucks at the "configuring hardware ... storage" step. It does not matter the kernel version but if i choose the SMP kernels it freezes just a little later on "configuring hardware ... audio" step.It freezes at the same spot without kernel panicking. I altered the rc.sysinit file so that at the configuring hardware step it does not load any modules. It passes (forcefully) the configuring hardware step but it freezes at the next "Configuring kernel parameters" step. There are no errors in the log as the k(logd) is not started at that point. For a change, i installed a FC2 and it's stable. However i want that Centos running! Please give me some advice. CM lspci output: 00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 0c) 00:00.1 Class ff00: Intel Corp. Memory Controller Hub Error Reporting Register (rev 0c) 00:02.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A0 (rev 0c) 00:03.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A1 (rev 0c) 00:1c.0 PCI bridge: Intel Corp. 6300ESB 64-bit PCI-X Bridge (rev 02) 00:1d.0 USB Controller: Intel Corp. 6300ESB USB Universal Host Controller (rev 02) 00:1d.4 System peripheral: Intel Corp. 6300ESB Watchdog Timer (rev 02) 00:1d.5 PIC: Intel Corp. 6300ESB I/O Advanced Programmable Interrupt Controller (rev 02) 00:1d.7 USB Controller: Intel Corp. 6300ESB USB2 Enhanced Host Controller (rev 02) 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev 0a) 00:1f.0 ISA bridge: Intel Corp. 6300ESB LPC Interface Controller (rev 02) 00:1f.2 IDE interface: Intel Corp. 6300ESB SATA Storage Controller (rev 02) 00:1f.3 SMBus: Intel Corp. 6300ESB SMBus Controller (rev 02) 04:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) 04:04.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705 Gigabit Ethernet (rev 03) cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdb2[1] sda2[0] 3068288 blocks [2/2] [UU] md2 : active raid1 sdb3[1] sda3[0] 240605440 blocks [2/2] [UU] md0 : active raid1 sdb1[1] sda1[0] 521984 blocks [2/2] [UU] unused devices: <none> cat /proc/interrupts CPU0 CPU1 0: 1847902 1878624 IO-APIC-edge timer 1: 795 727 IO-APIC-edge i8042 2: 0 0 XT-PIC cascade 8: 0 1 IO-APIC-edge rtc 9: 0 0 IO-APIC-level acpi 12: 0 58 IO-APIC-edge i8042 14: 6204 11391 IO-APIC-edge libata 15: 1 47 IO-APIC-edge ide1 169: 0 0 IO-APIC-level uhci_hcd 201: 0 0 IO-APIC-level ehci_hcd 209: 111408 88 IO-APIC-level eth0 NMI: 0 0 LOC: 3726666 3726522 ERR: 0 MIS: 0

2 1

DHCP without network access
by Maciej Żenczykowski 18 Jan '06

18 Jan '06

Hi, I've got a box with CentOS 4.2 x86_64 which had no DHCP access for a few hours, now I can't ping it (I'm pretty sure the box is still up). I expect the DHCP lease has timed out and the box has lost it's IP, I was expecting it to reacquire it once the DHCP came back up (configuration problem) - but no luck. Is this a known problem? Any solution/workaround? (for now or for the future...) Cheers, MaZe.

10 13

gdm won't start
by Josh Kelley 18 Jan '06

18 Jan '06

I'm trying to set up a new CentOS 4.2 desktop, and gdm refuses to start. It blanks the screen, displays the swirling blue circle mouse cursor that appears to be an hourglass equivalent, then drops back to the console window. It repeats this several times then displays the following error: The display server has been shut down about 6 times in the last 90 seconds, it is likely that something bad is going on. I will wait for 2 minutes before trying again on display :0. xdm works, and I can access X Windows by running startx. Any ideas on how to troubleshoot? It's a fresh install with a few site-specific customizations, but I don't think that I've done anything that would intefere with gdm. It is a relatively minimal install, so it's possible that I'm missing some needed package. Thanks. Josh Kelley

3 5

3ware disk failure -> hang
by Joshua Baker-LePain 18 Jan '06

18 Jan '06

I've got an i386 server running centos 4.2 with 3 3ware controllers in it -- an 8006-2 for the system disks and 2 7500-8s. On the 7500s, I'm running an all software RAID50. This morning I came in to find the system hung. Turns out a disk went overnight on one of the 7500s, and rather than a graceful failover I got this: Jan 6 01:03:58 $SERVER kernel: 3w-xxxx: scsi2: Command failed: status = 0xc7,flags = 0x40, unit #3. Jan 6 01:04:02 $SERVER kernel: 3w-xxxx: scsi2: AEN: ERROR: Drive error: Port #3. Jan 6 01:04:10 $SERVER 3w-xxxx[2781]: ERROR: Drive error encountered on port 3 on controller ID:2. Check cables and drives for media errors. (0xa) Jan 6 01:04:10 $SERVER kernel: Debug: sleeping function called from invalid context at include/asm/uaccess.h:556 Jan 6 01:04:10 $SERVER kernel: in_atomic():0[expected: 0], irqs_disabled():1 Jan 6 01:04:10 $SERVER kernel: [<c011fbe9>] __might_sleep+0x7d/0x88 Jan 6 01:04:10 $SERVER kernel: [<f885f056>] tw_ioctl+0x478/0xb07 [3w_xxxx] Jan 6 01:04:10 $SERVER kernel: [<c011fec9>] autoremove_wake_function+0x0/0x2d Jan 6 01:04:10 $SERVER kernel: [<f883f905>] scsi_done+0x0/0x16 [scsi_mod] Jan 6 01:04:10 $SERVER kernel: [<f8860529>] tw_scsi_queue+0x163/0x1f1 [3w_xxxx] Jan 6 01:04:10 $SERVER kernel: [<f883f748>] scsi_dispatch_cmd+0x1e9/0x24f [scsi_mod] Jan 6 01:04:10 $SERVER kernel: [<f884417e>] scsi_request_fn+0x297/0x30d [scsi_mod] Jan 6 01:04:10 $SERVER kernel: [<c0221f68>] __generic_unplug_device+0x2b/0x2d Jan 6 01:04:10 $SERVER kernel: [<c0221f7f>] generic_unplug_device+0x15/0x21 Jan 6 01:04:10 $SERVER kernel: [<c022288d>] blk_execute_rq+0x88/0xb0 Jan 6 01:04:10 $SERVER kernel: [<c022096e>] elv_set_request+0xa/0x17 Jan 6 01:04:10 $SERVER kernel: [<c022251f>] get_request+0x1de/0x1e8 Jan 6 01:04:10 $SERVER kernel: [<c01a97c3>] task_has_capability+0x4a/0x52 Jan 6 01:04:10 $SERVER kernel: [<c0225cd5>] sg_scsi_ioctl+0x2bf/0x3c1 Jan 6 01:04:10 $SERVER kernel: [<c02261aa>] scsi_cmd_ioctl+0x3d3/0x475 Jan 6 01:04:10 $SERVER kernel: [<c014d41b>] handle_mm_fault+0xbd/0x175 Jan 6 01:04:10 $SERVER kernel: [<c011ad67>] do_page_fault+0x1ae/0x5c6 Jan 6 01:04:10 $SERVER kernel: [<c014e4a6>] vma_adjust+0x286/0x2d6 Jan 6 01:04:10 $SERVER kernel: [<f88228ea>] sd_ioctl+0xb3/0xd4 [sd_mod] Jan 6 01:04:10 $SERVER kernel: [<c02246e8>] blkdev_ioctl+0x328/0x334 The 3ware boards are running the latest firmware and I'm using the stock driver in the kernel. I *did* have to upgrade mdadm to 1.12.0, as the stock version doesn't support stacked arrays. 3dmd is running. Any ideas as to what I can do to prevent this in the future? Having the system hang every time a disk dies is, well, less than optimal. Thanks. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University

9 38

unconfig'ing a machine
by Mark Belanger 18 Jan '06

18 Jan '06

The sys-unconfig script does not really work as advertised. For one thing it doesn't change the hostname. Is there an documentation about how to do the following: - Change the hostname, IP, networking etc for a currently networked machine - Change the hostname, IP, networking etc for a currently non-networked machine - Turn a networked machine into a non-networked machine. On a higher level - I'm looking for a turnkey way to send a box to someone, and have them set up the host and networking info. tia, -Mark

3 2

yum groupinstall "MySQL Database"
by Alexandru E. Ungur 17 Jan '06

17 Jan '06

Hi all, I have a question related to yum groupinstall. I just tried a: yum groupinstall "MySQL Database" I expected that I would end up with a MySQL Database server, but it installed a bunch of .rpms *except* mysql-server. No big deal, I'm just curious if it was intended this way or not, that's all. Thank you and, Have a nice evening everyone, Alex

3 2

Netfilter conntrack problem...
by Maciej Żenczykowski 17 Jan '06

17 Jan '06

Hi folks, I have the following in my firewall (condensed version) [CentOS 4.2: 2.6.9-11.EL.i686 kernel]: INPUT: --state ESTABLISHED,RELATED -j ACCEPT -p tcp -j REJECT --reject-with tcp-reset -j REJECT OUTPUT: ACCEPT The connection is over a wireless link so packets _do_ get dropped even though throughput is around 100-400 kB/s (depending on atmospheric conditions, etc.) Now I've noticed that sometimes connections are broken, I've narrowed the problem down to _this_ firewall (as in it's not the only one, but I'm pretty sure that it's at fault here...) Tcpdumping a "ssh somewhere cat /dev/zero > /dev/null" session on the firewall to an external host (a few hops away, reliable links, except for the single wireless link) on a prematurely terminated connection reveals the following (near the very end): # tcpdump -i eth1 host $TARGET -n -nn SRC=$FIREWALL:38945 DST=$TARGET:22 (all stream counts (acks) where 1728xxxxx so 1728 has been replaced with nil to gain on readability...) 034006 IP SRC > DST: . ack 05611 win 23688 <nop,nop,timestamp 603026606 838569311,nop,nop,sack sack 3 {11403:12851}{07059:09955} 068320 IP DST > SRC: . 12851:14299(1448) ack 85975 win 8576 <nop,nop,timestamp 838569322 603026606> 068421 IP SRC > DST: . ack 05611 win 23688 <nop,nop,timestamp 603026641 838569311,nop,nop,sack sack 3 {11403:14299}{07059:09955} 101781 IP DST > SRC: P 14299:15747(1448) ack 85975 win 8576 <nop,nop,timestamp 838569325 603026641> 101879 IP SRC > DST: . ack 05611 win 23688 <nop,nop,timestamp 603026674 838569311,nop,nop,sack sack 2 {11403:18643}{07059:09955} 133870 IP DST > SRC: . 18643:20091(1448) ack 85975 win 8576 <nop,nop,timestamp 838569328 603026674> 133969 IP SRC > DST: . ack 05611 win 23688 <nop,nop,timestamp 603026706 838569311,nop,nop,sack sack 2 {11403:20091}{07059:09955} 164262 IP DST > SRC: . 20091:21539(1448) ack 85975 win 8576 <nop,nop,timestamp 838569332 603026706> 164358 IP SRC > DST: . ack 05611 win 23688 <nop,nop,timestamp 603026737 838569311,nop,nop,sack sack 2 {11403:21539}{07059:09955} 198287 IP DST > SRC: . 21539:22987(1448) ack 85975 win 8576 <nop,nop,timestamp 838569335 603026737> 198386 IP SRC > DST: . ack 05611 win 23688 <nop,nop,timestamp 603026771 838569311,nop,nop,sack sack 2 {11403:22987}{07059:09955} 230168 IP DST > SRC: . 22987:24435(1448) ack 85975 win 8576 <nop,nop,timestamp 838569338 603026771> 230285 IP SRC > DST: . ack 05611 win 23688 <nop,nop,timestamp 603026803 838569311,nop,nop,sack sack 2 {11403:24435}{07059:09955} 252786 IP DST > SRC: . 05611:07059(1448) ack 85975 win 8576 <nop,nop,timestamp 838569340 603026771> 252857 IP SRC > DST: R 1475625677:1475625677(0) win 0 As far as I can tell, the second to last packet is perfectly valid - it is a valid retransmit of a missing/dropped piece. For some reason it results in a reset being sent from the tcp-reset rule (counter increases). Thus it would seem the packet is not matching the ESTABLISHED rule. Any ideas? Is this a bug? Has this been fixed in a/the newer kernel (I've got 156 days of uptime and a lot of junk on the box so I don't really want to reset it... :( ) Is the firewall configuration above correct - ie. is that a valid spot to generate TCP Resets? I doubt DROP'ing the packets will help since it'll just cause a stall, with future retransmits not getting through due to not matching as ESTABLISHED anyway... Cheers, MaZe.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss