Discuss

discuss@lists.centos.org

34753 discussions

Re: [CentOS] latest kernel
by Clive Gould 02 Sep '06

02 Sep '06

Marko I have 5 servers running CentOS. Four of them work fine with the 42 kernel. The fifth I use as a yum respository and when I try to use the 42 kernel I lose all network connectivity. Reverting to the earlier kernel on this box restores connectivity. I append some dmesg excerpts which suggest that the new kernel handles PCI (GSI) differently, but have not had the time to investigate further. Please let me know if you find a solution. Best wishes Clive dmesg excerpt for 42 kernel: PCI: Probing PCI hardware (bus 00) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *9 ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [ALKA] (IRQs 16 17 18 19 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [ALKB] (IRQs 16 17 18 19 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0, disabled. ACPI: PCI Interrupt Link [ALKD] (IRQs 21) *0, disabled. Linux Plug and Play Support v0.97 (c) Adam Belay usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing ACPI: PCI interrupt 0000:00:05.0[A]: no GSI - using IRQ 11 ACPI: PCI interrupt 0000:00:06.0[A]: no GSI - using IRQ 5 ACPI: PCI interrupt 0000:00:0e.0[A]: no GSI - using IRQ 5 ACPI: PCI interrupt 0000:00:11.1[A]: no GSI ACPI: PCI interrupt 0000:00:11.2[D]: no GSI - using IRQ 11 ACPI: PCI interrupt 0000:00:11.3[D]: no GSI - using IRQ 11 ACPI: PCI interrupt 0000:00:11.5[C]: no GSI - using IRQ 9 ACPI: PCI interrupt 0000:01:00.0[A]: no GSI - using IRQ 11 apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac) apm: overridden by ACPI. 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004) 8139cp: pci dev 0000:00:0e.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip 8139cp: Try the "8139too" driver instead. ACPI: PCI interrupt 0000:00:06.0[A]: no GSI - using IRQ 5 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 0000:00:06.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xa400. Vers LK1.1.19 divert: allocating divert_blk for eth0 via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker ACPI: PCI interrupt 0000:00:05.0[A]: no GSI - using IRQ 11 divert: allocating divert_blk for eth1 eth1: VIA Rhine at 0xe3000000, 00:50:ba:a1:86:44, IRQ 11. eth1: MII PHY found at address 8, status 0x7809 advertising 05e1 Link 0000. 8139too Fast Ethernet driver 0.9.27 ACPI: PCI interrupt 0000:00:0e.0[A]: no GSI - using IRQ 5 divert: allocating divert_blk for eth2 eth2: RealTek RTL8139 at 0xa800, 00:10:dc:59:bd:dc, IRQ 5 eth2: Identified 8139 chip type 'RTL-8101' ACPI: PCI interrupt 0000:00:11.5[C]: no GSI - using IRQ 9 PCI: Setting latency timer of device 0000:00:11.5 to 64 pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5 pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5 USB Universal Host Controller Interface driver v2.2 ACPI: PCI interrupt 0000:00:11.2[D]: no GSI - using IRQ 11 dmesg excerpt for 34 kernel: PCI: Probing PCI hardware (bus 00) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *9 ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [ALKA] (IRQs 16 17 18 19 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [ALKB] (IRQs 16 17 18 19 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0, disabled. ACPI: PCI Interrupt Link [ALKD] (IRQs 21) *0, disabled. Linux Plug and Play Support v0.97 (c) Adam Belay usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 ACPI: PCI interrupt 0000:00:05.0[A] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5 ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5 ACPI: PCI interrupt 0000:00:0e.0[A] -> GSI 5 (level, low) -> IRQ 5 ACPI: PCI interrupt 0000:00:11.1[A] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 ACPI: PCI interrupt 0000:00:11.2[D] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI interrupt 0000:00:11.3[D] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 10 (level, low) -> IRQ 10 ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 11 (level, low) -> IRQ 11 8139too Fast Ethernet driver 0.9.27 ACPI: PCI interrupt 0000:00:0e.0[A] -> GSI 5 (level, low) -> IRQ 5 divert: allocating divert_blk for eth0 eth0: RealTek RTL8139 at 0xa800, 00:10:dc:59:bd:dc, IRQ 5 eth0: Identified 8139 chip type 'RTL-8101' ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 0000:00:06.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xa400. Vers LK1.1.19 divert: allocating divert_blk for eth1 via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker ACPI: PCI interrupt 0000:00:05.0[A] -> GSI 11 (level, low) -> IRQ 11 divert: allocating divert_blk for eth2 eth2: VIA Rhine at 0xe3000000, 00:50:ba:a1:86:44, IRQ 11. eth2: MII PHY found at address 8, status 0x7809 advertising 05e1 Link 0000. ACPI: PCI interrupt 0000:00:11.5[C] -> GSI 10 (level, low) -> IRQ 10 PCI: Setting latency timer of device 0000:00:11.5 to 64 pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5 pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5 USB Universal Host Controller Interface driver v2.2 ACPI: PCI interrupt 0000:00:11.2[D] -> GSI 11 (level, low) -> IRQ 11 uhci_hcd 0000:00:11.2: UHCI Host Controller uhci_hcd 0000:00:11.2: irq 11, io base 0000b000 uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1 hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected ACPI: PCI interrupt 0000:00:11.3[D] -> GSI 11 (level, low) -> IRQ 11 Message: 34 Date: Fri, 1 Sep 2006 15:13:02 -0400 (EDT) From: "Marko A. Jennings" <markobiz(a)bluegargoyle.com> Subject: Re: [CentOS] latest kernel To: centos(a)centos.org Message-ID: <48730.192.168.77.10.1157137982.squirrel(a)bluegargoyle.com> Content-Type: text/plain;charset=iso-8859-1 On Fri, September 1, 2006 4:04 pm, Micha Silver wrote: > Today I updated several servers running CentOS 4.3, and got the new > 2.6.9-42 kernel. One of the machines serves as our firewall. After > rebooting I lost all forwarding thru the machine. I reverted back to the > 2.6.9-34 kernel and connectivity returned. During the few minutes that > the new kernel was running I checked that the routing table looked OK, > and with tcpdump I saw that indeed no traffic was going thru from the > externel interface to any of the internal interfaces. > > Has anyone seen similar behavior?? >

1 0

Re: [CentOS] vncserver startup issue
by Bart Schaefer 02 Sep '06

02 Sep '06

Did you edit /etc/sysconfig/vncservers ?

2 1

CentOS-announce Digest, Vol 19, Issue 1
by centos-announce-request＠centos.org 02 Sep '06

02 Sep '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. CEBA-2006:0901 Important CentOS 4 i386 up2date - bugfix update (Johnny Hughes) 2. CEBA-2006:0901-001 Important CentOS 4 x86_64 up2date - bugfix update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 01 Sep 2006 12:48:59 -0500 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2006:0901 Important CentOS 4 i386 up2date - bugfix update To: CentOS-Announce <centos-announce(a)centos.org> Message-ID: <1157132939.5268.126.camel(a)myth.home.local> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Bugfix Advisory 2006:0901-001 The up2date released with CentOS-4.4 did not specifically require the new centos-release, however the new centos-release provides the /etc/sysconfig/rhn/sources file for up2date. This update changes up2date to require centos-release >= 4-4.2 which will allow up2date to be used to upgrade of CentOS from 4.3 (or older versions) to 4.4. The following updated files have been uploaded and are currently syncing to the mirrors: i386: up2date-4.4.69-25.centos4.7.i386.rpm up2date-gnome-4.4.69-25.centos4.7.i386.rpm src: up2date-4.4.69-25.centos4.7.src.rpm

1 0

vncserver startup issue
by Alex Pilson 02 Sep '06

02 Sep '06

I installed vncserver via yum and when I reboot the server it does not want to start despite being set to start upon boot. Logging in via SSH and then issuing vncserver, I am able to get it running properly. I can't seem to figure this out. Any pointers appreciated. -- <---------------------------------------------------------------> Alex Pilson FlagShip Interactive, Inc. alex(a)flagshipinteractive.com <--------------------------------------------------------------->

1 0

Yum upgrade to 4.4 problem
by Simen Thoresen 02 Sep '06

02 Sep '06

CentOS 4.3 (SMP, x86_64, Athlon64 X2) with all pre-4.4 release updates applied. Since I ran into the Yum issue at the previous upgrade, I first did yum upgrade to get the list of packages (6 to install, 206 to update). I then did yum upgrade yum (which passed without issues) yum upgrade sqlite (which passed without isseus). Fairly certain that yum now works correctly, I wanted to just do another small upgrade before doing the rest, and did yum upgrade samba [root@naboens ~]# yum upgrade samba Setting up Upgrade Process Setting up repositories Reading repository metadata in from local files <no progress> This seemed to hang, and a look at top showed yum consuming more and more memory, the system starting to swap and bog down and then become unresponsive (all swap exhausted, I was not quick enough to kill yum). I was able to reproduce this on a different machine (also x86_64, SMP and Athlon64 X2), so it seems to be an actual problem. As I can play around a bit more on this machine, I tried doing a yum upgrade (without specifying samba) and it behaves the same (ie yum consuming increasing amounts of memory while "Reading repository metadata (etc)". Has anyone else experienced and been able to resolve this? -S -- Simen Thoresen, Dolphin ICS Systems Administration and Wulfkit Support

14 27

Postfix won't relay after update to CentOS 4.4
by Kanwar Ranbir Sandhu 02 Sep '06

02 Sep '06

Hi Everyone, My CentOS 4.4 mail server is having problems sending mail after updating it to 4.4 Before the update, I did not have any problems. My ISP requires that email clients must authenticate to their mail servers before mail can be sent out. I setup smtp auth to get postfix to relay mail through the ISP's mail servers. Here's my config: main.cf -------- relayhost = [smtp.broadband.rogers.com] smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_sasl_security_options = sasl_passwd --------------- smtp.broadband.rogers.com blah@blah.com:password I've done the usual run through of config files after an update, and made some small changes to main.cf (just added in comments and examples that were in main.cf.rpmnew). When I try to send a message, this is the error I get: F060D1C068: to=<m3freak(a)rogers.com>, relay=smtp-rog.mail.yahoo2.akadns.net[206.190.36.18], delay=1, status=bounced (host smtp-rog.mail.yahoo2.akadns.net[206.190.36.18] said: 530 authentication required - for help go to http://help.yahoo.com/help/us/mail/pop/pop-11.html (in reply to MAIL FROM command)) Just in case the ISP had done something, I manually tested authenticating to the ISP's mail server, and it worked just fine: Connected to smtp.broadband.rogers.com (206.190.36.18). Escape character is '^]'. 220 smtp105.rog.mail.re2.yahoo.com ESMTP ehlo krs 250-smtp105.rog.mail.re2.yahoo.com 250-AUTH LOGIN PLAIN XYMCOOKIE 250-PIPELINING 250 8BITMIME AUTH PLAIN blahblahblahblahblahblahblahblahblah 235 ok, go ahead (#2.0.0) So, the problem is on the Postfix end. I must assume something in the Postfix update broke my setup, but I can't figure out what it is. Has anyone else run into this? Am I missing something obvious? Hints appreciated. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2142_FC4 i686 GNU/Linux 16:11:07 up 2 days, 9:40, 3 users, load average: 1.06, 0.75, 0.62

9 17

upgrade to 4.4 hangs
by Zube 01 Sep '06

01 Sep '06

Two identical machines, both running CentOS 4.3 plus all the errata. First one: yum update went for a while and hung. At the bottom of the yum.log file was this: Aug 31 06:58:01 Updated: control-center.i386 1:2.8.0-12.rhel4.5 Aug 31 06:58:09 Updated: iiimf-le-unit.i386 1:12.1-13.EL.5 Aug The python process was in the process list, but it was consuming no CPU time. I let it go for a couple of hours, then killed it and played with the duplicate removal script posted previously. Second one: I tried a combination of suggestions previously posted: yum clean all yum update yum sqlite python-sqlite python-urlgrabber python-elementtree yum clean all yum upgrade This also ran for a while and then hung in a similar fashion. The tail of the yum.log is: Aug 31 11:29:08 Updated: at.i386 3.1.8-80_EL4 Aug 31 11:29:09 Updated: samba-client.i386 3.0.10-1.4E.9 Aug 31 11:29:21 Updated: anaconda.i386 10.1.1.46-1.cento Suggestions for future tries on other machines? Thanks much, Zube

4 6

Kind of OT: internal imap server
by Kanwar Ranbir Sandhu 01 Sep '06

01 Sep '06

Hi Everyone, I'm running a Postfix+Dovecot+SpamAssassin box in a DMZ. Everything is honkey dorey. Lately I've been thinking about moving Dovecot (for IMAP) into the internal network - I'd rather not store my mail on the CentOS 4 host in the DMZ. Not having done this before, I'm not quite sure what options I have. Also, I don't know if this is a good idea at all. So: 1. Should I just leave mail storage on the same box in the DMZ? 2. If the answer to 1 is no, what's the best way to get mail from the SMTP server in the DMZ to an IMAP server in the internal network? Here's what I've briefly considered: DMZ Postfix+SpamAssassin -> Internal Postfix+Dovecot DMZ Postfix+SpamAssassin -> Internal Fetchmail+Dovecot 3. Any tutorials for this out there, or even articles, etc., discussing using Postfix as a gateway? So far, I haven't found any that I've liked. Thanks in advance for any help. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.17-1.2142_FC4 i686 GNU/Linux 00:49:28 up 2 days, 18:18, 3 users, load average: 0.58, 0.48, 0.29

15 78

4.4 yum update problem
by Les Mikesell 01 Sep '06

01 Sep '06

On one of my machines yum hung up while installing the updates and could not be interrupted or killed. I rebooted the machine the next day, but now a 'yum update' reports: Error: Missing Dependency: openssh = 3.9p1-8.RHEL4.12 is needed by package openssh-askpass-gnome and Error: Missing Dependency: rpm = 4.3.3-13_nonptl is needed by package rpm-build even though rpm -q says those version are installed: #rpm -q rpm openssh rpm-4.3.3-13_nonptl openssh-3.9p1-8.RHEL4.12 Now what? -- Les Mikesell lesmikesell(a)gmail.com

3 4

updating base kernel when plus kernel installed
by Robert Moskowitz 01 Sep '06

01 Sep '06

A while ago I installed 2.6.9-nnnn.plus.c4 (nnnn means version at that time, now at 42.0.2), but I have to boot with the base kernel, as the plus kernel does not seem to work with my Atheros card/drivers. Right now my base kernel is at: 2.6.9-34.0.2.EL and I have this feeling that is quite behind the current rev. I cannot figure out how to get kernel.i686 to upgrade. I can't even seem to get yum or yumex to list the package name for the current kernel rev.

4 4

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