Discuss

discuss@lists.centos.org

34753 discussions

CENTOS 5.4 /var/log/messages too many?????
by mcclnx mcc 30 Jan '10

30 Jan '10

we have CENTOS 5.4 on dell server and recently /var/log/messages have thousand of following messages every day. Jan 30 10:12:47 ORA5 snmpd[8295]: Connection from UDP: [127.0.0.1]:55837 Jan 30 10:12:47 ORA5 snmpd[8295]: Received SNMP packet(s) from UDP: [127.0.0.1]:55837 Jan 30 10:12:47 ORA5 snmpd[8295]: Connection from UDP: [127.0.0.1]:55837 Jan 30 10:12:47 ORA5 last message repeated 31 times Jan 30 10:12:47 ORA5 snmpd[8295]: Connection from UDP: [127.0.0.1]:64026 Jan 30 10:12:47 ORA5 snmpd[8295]: Received SNMP packet(s) from UDP: [127.0.0.1]:64026 Jan 30 10:12:47 ORA5 snmpd[8295]: Connection from UDP: [127.0.0.1]:64026 Anyone know how to fix it? Thansk. ___________________________________________________ 您的生活即時通－溝通、娛樂、生活、工作一次搞定！ http://messenger.yahoo.com.tw/

2 1

Recover /usr/lib/libc.a
by Zvi Vered 30 Jan '10

30 Jan '10

Hello, I'm using Centos: /proc/version = Linux version 2.6.18-128.el5 (mockbuild(a)builder16.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Jan 21 10:44:23 EST 2009 I did a mistake and erased libc.a from /usr/lib How can I recover it without reinstalling Centos ? Thanks.

3 2

Full Virtualized DomU won't boot
by Sergio Belkin 30 Jan '10

30 Jan '10

Hi, I use Centos 5.4 x86_64 kernel used is 2.6.18-164.11.1.el5xen I have a physical machine running Debian Etch (32 bit) and Debian Lenny and I virtualized the first one as follows: *Created a HVM DomU with Virt-Manager with a virtual disk file of 40000 M *Boot from LiveCD, and created a swap and a ext3 partitions (Yes, very simple layout). *Rsync'd files from root partition of physical machine to partition mounted on LiveCD on DomU. *Chrooted and edited files /boot/grub/menu.lst, /etc/fstab, etc/mtab, /boot/grub/device.map. *Then I rebooted from hard disk and stay freezed with the message "booting from hard disk" . But it doesn't boot at all from hard disk. I can boot using grub-rescue-cdrom, but if I try to install grub with grub-install it outputs: "The file /boot/grub/stage1 not read correctly" (I've tried --recheck option, and depmod and update-grub commands with no success) Output of file command on virtual disk file is: /virtuales/videodisk.img: x86 boot sector; partition 1: ID=0x82, starthead 1, startsector 63, 4273227 sectors; partition 2: ID=0x83, active, starthead 0, startsector 4273290, 77626080 sectors The DomU file is: DomU (file): name = "video" uuid = "54d25d78-b9d0-0159-542c-bb601cc936bb" maxmem = 1024 memory = 512 vcpus = 1 builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" boot = "d" pae = 1 acpi = 1 apic = 1 localtime = 0 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" device_model = "/usr/lib64/xen/bin/qemu-dm" sdl = 0 vnc = 1 vncunused = 1 keymap = "es" disk = [ "file:/virtuales/videodisk.img,hda,w", "file:/virtuales/isos/grub-rescue-cdrom.iso,hdc:cdrom,r" ] vif = [ "mac=00:16:36:0b:24:2d,bridge=xenbr0,script=vif-bridge" ] parallel = "none" serial = "pty" EOF With grub-rescue cd DomU can boot but as I've said can't install grub and loads also loopback interface. Please could you tell me what I am doing wrong? Thanks in advance!! -- -- Open Kairos http://www.sergiobelkin.com Watch More TV http://sebelk.blogspot.com Sergio Belkin -

2 2

CentOS 5 i386 Live CD
by Mike McCarty 29 Jan '10

29 Jan '10

Johnny Hughes wrote: > I forgot to add that the password for root and centos is: > > 12qwaszx > > Johnny Hughes wrote: >> The CentOS Development team is pleased to announce the availability of >> the CentOS 5 i386 Live CD. [...] >> This CD has a non writable /usr directory, which means it is not able to >> have software installed on it after boot up. The CentOS team is working >> hard to create a Live CD for CentOS 5 that is based on the Fedora Live >> CD Project (that is writable in all directories and even able to be used >> for installs) ... unfortunately we were not able to get this working >> with CentOS 5 for this release. We hope to get that Live CD working by >> the release of CentOS 5.1. Did I miss some notices? I don't recall seeing another LiveCD. How is progress coming? Mike -- p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);} Oppose globalization and One World Governments like the UN. This message made from 100% recycled bits. You have found the bank of Larn. I speak only for myself, and I am unanimous in that!

1 0

NFS vs SMb vs iSCSI for remote backup mounts
by Rudi Ahlers 29 Jan '10

29 Jan '10

Hi, I would like to get some input from people who have used these options for mounting a remote server to a local server. Basically, I need to replicate / backup data from one server to another, but over the internet (i.e. insecure channels) Currently we have been mounting an SMB share over SSH, but it's got it's own set of problems. And I don't know if this is optimal, or if I could setup something better. We don't have much control over the remote server, so I couldn't setup a VPN, or iSCSI or anything else. My options was FTP & SMB. But I want to move the backups in-house, to save bandwidth and have more control over what we do. So, with a new CentOS server & 2x1TB HDD's in RAID1 configuration, I can do pretty much whatever I want. The backup server(s) will serve backups for multiple servers, in different data centers (possible in different counties as well, I still need to think about this), so my biggest concern is security. We mainly use cPanel & DotNetPanel (Windows ServerS) , but also WebMin & VirtualMin, so I need to stick with their native backup procedures and don't really want to use a too technical backup system. The end users need access to the data 24/7, so having the remote share permanently mounted seems to be the best for this, then our support staff don't need to SSH into the servers and download the backups. With the mount, I can also use rsync backups, so an end user could restore only a single file if need be. NOW, the question is: Which protocol would be best for this? I can only think of SMB, NFS & iSCSI The SMB mounts have worked well so far, but it's not as safe, and once the SMB share is mounted, I can't unmount it until the server reboots. This isn't necessarily a bad thing, but sometime the backup script will mount the share again (I think this is a bug in cPanel) and we end up with 4 or 5 open connection to the remote server. NFS - last time I looked at it was on V3, which was IMO rather slow & insecure. iSCSI - this doesn't allow for more than one connect to the same share. Sometimes I user might want to download a backup directly from the backup server via FTP / SSH / a web interface, which I don't think will work. We also sometimes need to restore a backup on a different server (if for example the HDD on the initial server is too full), so this isn't possible. The remote shares also need to be mounted inside XEN domU's, or directly on CentOS / Windows servers. what would be my best option for this? -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532

13 31

Re: [CentOS] Lockup using stock r8169 on 4.8 in gigabit mode during heavy transfer on lan
by Tim Nelson 29 Jan '10

29 Jan '10

----- "Jason Pyeron" <jpyeron(a)pdinc.us> wrote: > I have no output in the logs, but /etc/init.d/network restart fixes > the issue. > I am rsync/scp (10GB) data from one 100MB Full duplex host to an ASUS > M3A78-EM > (RTL8111B/C). It locks up around the 1.5GB Tx mark. > If I ethtool -s eth0 autoneg off speed 100 duplex full it does not > happen again. > > Ideas? Part of the problem is that you mention r8169 kernel module in your subject but your hardware is RTL8111B. Realtek drivers are notorious for loading on improper hardware and appearing to work properly. You need to get the proper driver for your NIC. I've run into this countless times with the r8169 driver and non-r8169 Realtek NICs. And, on a side note, Realtek may possibly be the worst NIC out there, especially for server use. It may link at gigabit speed, but I bet a trusty old 3Com or Intel Pro 100 will get better throughput. Install a different NIC as fast as you can and never look back. --Tim

2 1

Lockup using stock r8169 on 4.8 in gigabit mode during heavy transfer on lan
by Jason Pyeron 29 Jan '10

29 Jan '10

I have no output in the logs, but /etc/init.d/network restart fixes the issue. I am rsync/scp (10GB) data from one 100MB Full duplex host to an ASUS M3A78-EM (RTL8111B/C). It locks up around the 1.5GB Tx mark. If I ethtool -s eth0 autoneg off speed 100 duplex full it does not happen again. Ideas? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.

2 1

Re: [CentOS] NFS vs SMb vs iSCSI for remote backup mounts
by J.Witvliet＠MINDEF.NL 29 Jan '10

29 Jan '10

At any rate... if I were in your shoes and really restricted to the options you propose, I would go with CIFS mounts through IPSEC tunnels. Wouldn't IPSEC add more overhead than an SSH tunnel? -geoff I would *certainly* not use ssh-tunnels, on a line that is not 100% error free or with high latency. In general tcp-in-tcp tunneling is BAD. One likely gets the infamous snowbal-effect. As ipsec is lower in the protocol-stack (then openvpn) it has probably the lowest overhead. ssh-tunnels are the worst (just nice for a quick tunnel in SOHO-environments) ______________________________________________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.

1 0

Re: [CentOS] NFS vs SMb vs iSCSI for remote backup mounts
by J.Witvliet＠MINDEF.NL 29 Jan '10

29 Jan '10

________________________________ From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Rudi Ahlers Sent: Friday, January 29, 2010 12:23 AM To: CentOS mailing list Subject: Re: [CentOS] NFS vs SMb vs iSCSI for remote backup mounts On Fri, Jan 29, 2010 at 1:18 AM, nate <centos(a)linuxpowered.net<mailto:centos@linuxpowered.net>> wrote: Rudi Ahlers wrote: > nate, why not? Is it simply unavoidable at all costs to mount on system on > another, over a WAN? That's all I really want todo If what you have now works, stick with it.. in general network file systems are very latency sensitive. CIFS might work best *if* your using a WAN optimization appliance, I'm not sure how much support NFS gets from those vendors. iSCSI certainly is the worst, block devices are very intolerant of latency. AFS may be another option though quite a bit more complicated, as far as I know it's a layer on top of an existing file system that is used for things like replication http://www.openafs.org/ I have no experience with it myself. nate _______________________________________________ CentOS mailing list CentOS(a)centos.org<mailto:CentOS@centos.org> http://lists.centos.org/mailman/listinfo/centos Thanx nate, this is what I wanted to hear :) So, is there any benefit in using NFS over SMB in this case? Can't speak for NFS(3/4), but i can tell you that that smb-protocol combined with high latency is a recepy for disaster. We tried it from europe to the carribean (both sat or fibre) but users spent their time more complaining then working. Needed horrible expensive lan-optimesers at both end So perhaps nfs4 or afs (later is intended for geographically separated machines, afaicr) but certainly not smb! ______________________________________________________________________ Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.

1 0

How to map ata#.# numbers to /dev/sd numbers?
by Stephen Harris 29 Jan '10

29 Jan '10

On my C5 machine (a Dell XPS420) I have a 500Gb disk on the internal SATA controller. I also have a SiI3132 dual-port multi-device eSATA card. This is connected to an external SATA array of disks. Now occasionally I see something like this in my logs ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 a ction 0x0 ata7.01: irq_stat 0x00060002, device error via D 2H FIS ata7.01: cmd 25/00:08:47:1c:92/00:00:6c:00:00/e0 tag 0 dma 4096 in res 51/40:00:4e:1c:92/00:00:6c:00:00/00 Emask 0x9 (media error) ata7.01: status: { DRDY ERR } ata7.01: error: { UNC } ata7.01: configured for UDMA/100 ata7: EH complete How do I tell what disk this is complaining about? Is there a way to determine what ata7.01 maps to in terms of /dev/sd# values? /proc/scsi/scsi doesn't obviously match scsi# numbers to ata# numbers :-( -- rgds Stephen

6 9

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