Discuss October 2010

discuss@lists.centos.org

256 participants
226 discussions

the wandering MAC?
by Boris Epstein 29 Nov '10

29 Nov '10

Hi all, I have what appears to be a truly puzzling problem. I've got this P4 32-bit machine running CentOS 5.5 with XEN that has two NICs: one onboard, an Intel Corporation 82540EM Gigabit and one on an expansion card, Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit. The second one is recognized as eth1. What's happening is, it is showing up under one of the two MAC's: either 00:0a:cd:1a:c1:71 or 00:00:00:00:c1:71. If you reboot it the MAC stays the same; if you shutdown and do a full powerdown it seems to change. Obviously, after it goes from one MAC to another you have to play with the start-up scripts for this interface to start up correctly and this becomes a major annoyance. Any idea what all of this mess could mean? Thanks. Boris.

6 8

Routing of outgoing packets
by Mitja Mihelič 22 Nov '10

22 Nov '10

Hi! I am trying to use hping to chek the latency of our network. Somehow things are not going to plan and I thought someone might be able to shed some light on the subject. Here is the setup: (the IP addresses gvien here are fake, but they do represent the correct state of the networking setup) vlan interface IP mask V2 eth0 192.168.20.20 32 V4 eth1 172.16.4.40 32 V6 eth2 172.16.6.60 32 The default route is set to eth1. The idea is to use eth2 for pinging only, the other two interfaces are used by another service and management access. If I do: ping -c 2 -I eth2 74.125.39.147 or fping -c 2 -I eth2 74.125.39.147 It binds to eth2 and sends its ICMP probes via that interface with the IP on that interface. If I do: hping3 -1 -c 2 -I eth2 74.125.39.147 -VD or [root@server ~]# hping3 -c 2 -I eth2 74.125.39.147 -VD DEBUG: if lo: Don't Match (but seems to be UP) DEBUG: if eth0: Don't Match (but seems to be UP) DEBUG: if eth1: Don't Match (but seems to be UP) DEBUG: if eth2: OK using eth2, addr: 172.16.6.60, MTU: 1500 It supposedly binds to eth2. But tcpdump tells another story. Packets get sent out via the default route (eth1) with the IP from eth2 set as the source address. The same happens with tcptraceroute (tcptraceroute-1.5-0.beta7.el5.rf.i386.rpm). I have tried various routing policies, but I have yet to find a solution that works. I have used iptables to log the packets in the OUTPUT chain, but they arrive there with the interface already set to eth1. Can anyone help ? Regards, Mitja Mihelic

3 3

PATA Hard Drive woes
by Keith Roberts 21 Nov '10

21 Nov '10

Hi All. Yesterday I was installing Centos 5.5 to my web server, and it looks like the main hard drive has gone AWOL. Fedora 12 put the file system into r/o mode. The drive is an Hitachi, still under warranty. There are bad sectors on it, and running the Hitachi DFT tool confirms this. Also I cannot repair the bad sectors. Would this be caused by a faulty I/O chip, or is it safe to say it's definately the HDD at fault? Kind Regards, Keith Roberts -- In theory, theory and practice are the same; in practice they are not. This email was sent from my laptop with Centos 5.5

12 30

Adding SAMBA users in Centos 5.5
by Peter Crighton 12 Nov '10

12 Nov '10

I have SAMBA working on Centos 5.5 - I can see and access my "home" directory from a Windows machine. I have created a new folder to share, changed the owner and group to my username and chcon -t samba_share_t to allow SELinux to share the folder. I can see this folder from Windows but not access it's contents. I think that the key reason is that there is no user assigned to the new share that I have created in SAMBA. I don't seem to be able add users/passwords (at least they don't stay present! In the SAMBA section of Control Panel I have selected my username from the Unix users and added it to SAMBA users with the same password as the Windows machine (and as it happens the Centos machine). Click Apply and OK. When I re-load the SAMBA section of Control Panel my user has disappeared! This didn't happen when I setup a Centos 4.4 machine - all the users are still visible in Control Panel. Without the user available I can't assign it to my new share. Why is my added user disappearing and how can I solve it? (I presume that I can access my "home" share as it is automatically by the username from Windows).

2 3

RHEL 6 potential release date???
by Tom Bishop 10 Nov '10

10 Nov '10

Benn playing with the beta's and have looked around for a potential release date...Does anyone know what the likely date is??? Thanks....

11 16

Network card not working after update to 2.6.18-194.17.4.el5
by Mathieu Baudier 10 Nov '10

10 Nov '10

Hello, the network card of my workstation stopped working after I updated the kernel to 2.6.18-194.17.4.el5 . I don't see any specific error messages when booting, and the related interface is shown as up by ifconfig with its (static) IP address properly set. But I cannot reach any other computer or router on the LAN (whereas other boxes work fine). Where the network cable is plugged, an orange light stays on and does not blink. Booting with 2.6.18-194.17.1.el5 instead solves the issue. The network card is: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10) I just wanted to share this, and see if anybody else experienced such issues. It makes me feel uncomfortable with updating some remote servers, because it would really be a pain to fix if their network cards stopped working after rebooting (they are not the same as the one of my workstation, but I would feel safer if I could find out that this is a problem with my computer and not with the kernel) Cheers, Mathieu

3 3

Web statistics - w3perl
by Jussi Hirvi 04 Nov '10

04 Nov '10

I am considering a richer alternative to good old Webalizer, in a webhotel (multidomain) setting. Any experience with w3perl? The demo at least looks impressive. http://www.w3perl.com - Jussi -- Jussi Hirvi * Green Spot Topeliuksenkatu 15 C * 00250 Helsinki * Finland Tel. +358 9 493 981 * Mobile +358 40 771 2098 (only sms) jussi.hirvi(a)greenspot.fi * http://www.greenspot.fi

5 5

SCSI/SAS error message by mpt2sas.ko
by Alexander Dalloz 03 Nov '10

03 Nov '10

Dear all, actually I installed CentOS 5.4 x86_64 on 11 new Dell R710 servers. It is required to use 5.4 to be covered by the NetApp Interoperability Matrix for use of Snapdrive. All systems spit out the error message mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:4637/_scsih_add_device()! at boot time. In dmesg the complete SCSI initialization logging appears as follows: SCSI subsystem initialized mpt2sas version 01.101.00.00 loaded scsi0 : Fusion MPT SAS Host GSI 22 sharing vector 0x5A and IRQ 22 ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 33 (level, low) -> IRQ 90 PCI: Setting latency timer of device 0000:03:00.0 to 64 mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (24544400 kB) mpt2sas0: PCI-MSI-X enabled: IRQ 98 mpt2sas0: iomem(0xdf2b0000), mapped(0xffffc20000040000), size(65536) mpt2sas0: ioport(0xfc00), size(256) mpt2sas0: sending diag reset !! [...] mpt2sas0: diag reset: SUCCESS mpt2sas0: Allocated physical memory: size(1125 kB) mpt2sas0: Current Controller Queue Depth(490), Max Controller Queue Depth(3439) mpt2sas0: Scatter Gather Elements per IO(128) mpt2sas0: LSISAS2008: FWVersion(02.15.63.00), ChipRevision(0x02), BiosVersion(07.01.09.00) mpt2sas0: Protocol=(Initiator,Target<6>mpt2sas0: Dell PERC H200 Integrated: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F1E) ), Capabilities=(Raid,TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) mpt2sas0: sending port enable !! mpt2sas0: host_add: handle(0x0001), sas_addr(0x5842b2b0194dce00), phys(8) mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:4637/_scsih_add_device()! mpt2sas0: port enable: SUCCESS Vendor: Dell Model: Virtual Disk Rev: 1028 Type: Direct-Access ANSI SCSI revision: 06 scsi 0:1:0:0: RAID1: handle(0x004f), wwid(0x04adb846d46d5f0a), pd_count(2), type(SSP) scsi 0:1:0:0: qdepth(128), tagged(1), simple(1), ordered(0), scsi_level(7), cmd_que(1) SCSI device sda: 285474816 512-byte hdwr sectors (146163 MB) sda: Write Protect is off sda: Mode Sense: 03 00 00 08 SCSI device sda: drive cache: write through SCSI device sda: 285474816 512-byte hdwr sectors (146163 MB) sda: Write Protect is off sda: Mode Sense: 03 00 00 08 SCSI device sda: drive cache: write through sda: sda1 sda2 sda3 sd 0:1:0:0: Attached scsi disk sda Vendor: FUJITSU Model: MBA3147RC Rev: D306 Type: Direct-Access ANSI SCSI revision: 05 scsi 0:0:0:0: SSP: handle(0x000a), sas_addr(0x500000e1150ca882), device_name(0x0000000000000000) scsi 0:0:0:0: SSP: enclosure_logical_id(0x5842b2b0194dce00), slot(1) scsi 0:0:0:0: qdepth(254), tagged(1), simple(1), ordered(0), scsi_level(6), cmd_que(1) Vendor: FUJITSU Model: MBA3147RC Rev: D306 Type: Direct-Access ANSI SCSI revision: 05 scsi 0:0:1:0: SSP: handle(0x000b), sas_addr(0x500000e1150ca9c2), device_name(0x0000000000000000) scsi 0:0:1:0: SSP: enclosure_logical_id(0x5842b2b0194dce00), slot(0) scsi 0:0:1:0: qdepth(254), tagged(1), simple(1), ordered(0), scsi_level(6), cmd_que(1) In the source code of the mpt2sas.ko module http://www.takatan.net/lxr/source/drivers/scsi/mpt2sas/mpt2sas_scsih.c?v=2.… the code part responsible for the error messages is 4633 /* check if this is end device */ 4634 device_info = le32_to_cpu(sas_device_pg0.DeviceInfo); 4635 if (!(_scsih_is_end_device(device_info))) { 4636 printk(MPT2SAS_ERR_FMT "failure at %s:%d/%s()!\n", 4637 ioc->name, __FILE__, __LINE__, __func__); 4638 return 0; 4639 } I am not sure what that should tell me. I can not detect any misfunction once the systems are up and running, nor any further error loggings. Any clue about the severity of that mpt2sas check and failure note? Best regards Alexander

1 1

sound
by mattias 01 Nov '10

01 Nov '10

Are the sound muted as default?

2 2

Possible to reboot a system after kickstart installation without pressing a key?
by Sean Carolan 31 Oct '10

31 Oct '10

The subject just about says it all - I'm wondering if there is a way to do a completely hands-off installation, including the reboot at the end, without "Press any key to continue"?

3 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss October 2010