Discuss

discuss@lists.centos.org

34758 discussions

Failing Network card
by Gregory P. Ennis 20 Jun '12

20 Jun '12

Everyone, Most of the time I am over my head in trying to troubleshoot problems. However, after reading manuals, man pages, and getting advice from this list I have been able to work my way through difficulties, and at the end, I usually have a better understanding of what 'is going on'. I can only hope this method will work on this problem too. I have been chasing a problem with a pci-e TrendNet(TEG-ECTX) gigabit card. After adding the card to a machine with a new Centos 6.2 install and naming it 'eth4' it works well for 6 to 12 hours and then fails. The failure is characterized by dropping its connection speed from 1000 to 100 while not allowing any data to flow in or out. When this happens a shutdown and reboot does not solve the problem, but shutting down and then removing the power does solve the problem. I wrote a perl script that uses the eth4 interface by pinging another machine every 60 seconds to try to figure out the relationship of the message log entries with the time of failure, and I think there is a corelation of the failure of eth4 to function with the below entry. Unfortunately, I am way over my head on this one. If any of you can help I would surely appreciate your thoughts. Some additional information that may be useful. The TrendNet card is the second TrendNet card I have used. The first card had the same symptoms, and I deduced the card was bad, and purchased another one. The symptoms are the same with the second card. Before I purchase a third card from a different manufacturer I thought I would post this to see what some of you think. This is the first pci-e card I have used; are there problems with the pci-e interfaces as opposed to pci? Do you think the motherboard could be the problem, and moving eth4 to a different slot on the motherboard would be worthwhile. Any ideas ??? Greg Ennis P.S. Here is the appropriate log entry in the /var/log/message file. Jun 20 03:08:38 Mail kernel: ------------[ cut here ]------------ Jun 20 03:08:38 Mail kernel: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x26d/0x280() (Not tainted) Jun 20 03:08:38 Mail kernel: Hardware name: p7-1220 Jun 20 03:08:38 Mail kernel: NETDEV WATCHDOG: eth4 (r8169): transmit queue 0 timed out Jun 20 03:08:38 Mail kernel: Modules linked in: ipt_REDIRECT ipt_LOG xt_limit ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle bridge autofs4 sunrpc bnx2fc cnic uio fcoe libfcoe libfc 8021q scsi_transport_fc garp stp llc scsi_tgt cpufreq_ondemand powernow_k8 freq_table mperf ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 vhost_net macvtap macvlan tun kvm uinput sg btusb bluetooth rfkill microcode snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd soundcore snd_page_alloc i2c_piix4 r8169 mii ext4 mbcache jbd2 sr_mod cdrom sd_mod crc_t10dif usb_storage sdhci_pci sdhci mmc_core ahci radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan] Jun 20 03:08:38 Mail kernel: Pid: 0, comm: swapper Not tainted 2.6.32-220.23.1.el6.centos.plus.x86_64 #1 Jun 20 03:08:38 Mail kernel: Call Trace: Jun 20 03:08:38 Mail kernel: <IRQ> [<ffffffff81069c97>] ? warn_slowpath_common+0x87/0xc0 Jun 20 03:08:38 Mail kernel: [<ffffffff81069d86>] ? warn_slowpath_fmt +0x46/0x50 Jun 20 03:08:38 Mail kernel: [<ffffffff81069d86>] ? warn_slowpath_fmt +0x46/0x50 Jun 20 03:08:38 Mail kernel: [<ffffffff81451c0d>] ? dev_watchdog +0x26d/0x280 Jun 20 03:08:38 Mail kernel: [<ffffffff814519a0>] ? dev_watchdog +0x0/0x280 Jun 20 03:08:38 Mail kernel: [<ffffffff810efbf3>] ? trace_nowake_buffer_unlock_commit+0x43/0x60 Jun 20 03:08:38 Mail kernel: [<ffffffff814519a0>] ? dev_watchdog +0x0/0x280 Jun 20 03:08:38 Mail kernel: [<ffffffff8107cab7>] ? run_timer_softirq +0x197/0x340 Jun 20 03:08:38 Mail kernel: [<ffffffff81072291>] ? __do_softirq +0xc1/0x1d0 Jun 20 03:08:38 Mail kernel: [<ffffffff810958b0>] ? hrtimer_interrupt +0x140/0x250 Jun 20 03:08:38 Mail kernel: [<ffffffff8100c24c>] ? call_softirq +0x1c/0x30 Jun 20 03:08:38 Mail kernel: [<ffffffff8100de85>] ? do_softirq+0x65/0xa0 Jun 20 03:08:38 Mail kernel: [<ffffffff81072075>] ? irq_exit+0x85/0x90 Jun 20 03:08:38 Mail kernel: [<ffffffff814fc550>] ? smp_apic_timer_interrupt+0x70/0x9b Jun 20 03:08:38 Mail kernel: [<ffffffff8100bc13>] ? apic_timer_interrupt +0x13/0x20 Jun 20 03:08:38 Mail kernel: <EOI> [<ffffffff812f5f9c>] ? acpi_idle_enter_simple+0x114/0x14b Jun 20 03:08:38 Mail kernel: [<ffffffff812f5f98>] ? acpi_idle_enter_simple+0x110/0x14b Jun 20 03:08:38 Mail kernel: [<ffffffff814014a7>] ? cpuidle_idle_call +0xa7/0x140 Jun 20 03:08:38 Mail kernel: [<ffffffff81009e06>] ? cpu_idle+0xb6/0x110 Jun 20 03:08:38 Mail kernel: [<ffffffff814ed686>] ? start_secondary +0x202/0x245 Jun 20 03:08:38 Mail kernel: ---[ end trace 24f15998c117ac8f ]--- Jun 20 03:08:38 Mail kernel: r8169 0000:01:00.0: eth4: link up Jun 20 03:08:39 Mail abrtd: Directory 'oops-2012-06-20-03:08:39-2420-0' creation detected Jun 20 03:08:39 Mail abrt-dump-oops: Reported 1 kernel oopses to Abrt Jun 20 03:08:39 Mail abrtd: Can't open file '/var/spool/abrt/oops-2012-06-20-03:08:39-2420-0/uid': No such file or directory

7 21

CentOS-5.8 - Problem booting remote host
by James B. Byrne 20 Jun '12

20 Jun '12

Kernel 2.6.18-308.8.2.el5 I recently experienced an odd problem with a host at our warm-site location. The facility we use suffered an hvac failure during elevated ambient temperatures (30C+) on Monday past and the equipment room reportedly cooked for some hours. It was sufficient that our equipment shutdown. In all probability this was due to an over-temp condition since the systems are all powered from a UPS but possibly there was an extended power out instead. Whatever the cause one of our hosts did not restart subsequent to this shutdown. Which condition required my presence on site. When it was powered up today in situ the host's console would display the CentOS splash screen with the message [press any key to enter menu] and then the message "Booting in ....4 seconds" However, the countdown timer never changed from the initial value and the restart never took place. When I entered the console menu and selected the most recent kernel available the system booted normally. It had to do a lot of disk remediation on the first go through but all that completed without untoward difficulty. Subsequent shutdowns displayed the same behaviour. The splash screen displayed, the boot timer message showed, and then nothing changed thereafter unless and until I entered the boot menu. Selecting the default kernel in the boot menu allowed the restart to continue, this time without any unusual reports. I repeated this process several times more just to confirm that this was not a transient effect. Each time operator intervention from the console was required to restart the system but once this was done no further problems were noted. I repeated the process and rebooted using each of the older kernels present. As far as I could determine there was nothing wrong with any of the boot images once past the auto-select segment of the boot process. I then went into /boot/grub.conf and changed the default boot from index 0 to index 1 so as to use the previous kernel. Following this configuration change thereafter the system restarted normally without operator intervention. The problem kernel was installed from Updates on June 13 and was running from that date as shown in the log entries below. This was a remote restart and evidently it completed without any problem. Jun 13 10:15:59 inet04 shutdown[19274]: shutting down for system reboot . . . Jun 13 10:16:25 inet04 exiting on signal 15 Jun 13 10:18:35 inet04 syslogd 1.4.1: restart. Jun 13 10:18:35 inet04 kernel: klogd 1.4.1, log source = /proc/kmsg started. Jun 13 10:18:35 inet04 kernel: Linux version 2.6.18-308.8.2.el5 (mockbuild@build er10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)) #1 SMP Tue Jun 12 09:57:26 EDT 2012 The current syslog shows repeated restarts commencing at 18:12 on Jun 17 and ending at 19:08, after which the system no longer records any activity whatsoever until I restarted it manually earlier today. These two syslogd entries are adjacent in /var/log/messages Jun 18 19:08:48 inet04 kernel: PROBE_BLACKIST: IN=eth0 OUT= MAC=00:1c:c4:a1:66:1e:00:18:73:e8:35:a1:08:00 SRC=126.67.126.141 DST=209.47.176.105 LEN=48 TOS=0x00 PREC=0x00 TTL=110 ID=56792 DF PROTO=TCP SPT=2153 DPT=445 WINDOW=64240 RES=0x00 SYN URGP=0 Jun 20 12:11:31 inet04 ntpd[2480]: time reset +147721.498633 s Have any of you ever experienced anything like this? Does anyone have any idea what might have caused the corruption of the restart mechanism or where the problem might be? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Swap Partition in CentOS 5.8
by Kaushal Shriyan 20 Jun '12

20 Jun '12

Hi, Any recommendation to set SWAP Partition in CentOS 5.8 on 32GB Physical Memory Box and also how does swap partition is being used and any utility to know when was swap partition being used. Regards, Kaushal

6 5

CentOS-announce Digest, Vol 88, Issue 12
by centos-announce-request＠centos.org 20 Jun '12

20 Jun '12

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-2012:1016 CentOS 5 e2fsprogs Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 20 Jun 2012 11:25:09 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2012:1016 CentOS 5 e2fsprogs Update To: centos-announce(a)centos.org Message-ID: <20120620112509.GA30189(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2012:1016 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1016.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 9c15c4d62e72295c6ab4535879cf96cc0f6e27d634da1ddb71ebe67ecda429f9 e2fsprogs-1.39-34.el5_8.1.i386.rpm 672eb3efec3fc7b17d8a62c79e20040ffbe842d4aa722bb45c08fb87ed75d0d5 e2fsprogs-devel-1.39-34.el5_8.1.i386.rpm 6ba4bfb5bf2a363a23d7362520256224cff69f12dcbbe4c462d3d6886e0bdf15 e2fsprogs-libs-1.39-34.el5_8.1.i386.rpm 530384374a5f0d080cc021e9efe7a2950ab115da353ff7c9105cd94c92557b76 uuidd-1.39-34.el5_8.1.i386.rpm x86_64: 3101c862faeb6949ab554deb5111ee4c3739daa6b5b188971f4bdbb3a99c73f1 e2fsprogs-1.39-34.el5_8.1.x86_64.rpm 672eb3efec3fc7b17d8a62c79e20040ffbe842d4aa722bb45c08fb87ed75d0d5 e2fsprogs-devel-1.39-34.el5_8.1.i386.rpm dabd937633eaaa2fe0774f8ab24e10d3a49073015f26342f3f9cf784a8b82185 e2fsprogs-devel-1.39-34.el5_8.1.x86_64.rpm 6ba4bfb5bf2a363a23d7362520256224cff69f12dcbbe4c462d3d6886e0bdf15 e2fsprogs-libs-1.39-34.el5_8.1.i386.rpm f18641fe31e827c7a8c16c93a5605f6f9f1f2e3e086dfe759d932dedc0f4b713 e2fsprogs-libs-1.39-34.el5_8.1.x86_64.rpm 1992be1ba00e41ce4e8431c4de4800e1e264999c5254a3c777f9ffa5d18a838f uuidd-1.39-34.el5_8.1.x86_64.rpm Source: fbde83f866070d22a711fd5b94bb14b8ca44d2e4e9bbb9ead4563fca57ff9505 e2fsprogs-1.39-34.el5_8.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 88, Issue 12 ***********************************************

1 0

Memory recognition in 6.2
by Hugh E Cruickshank 20 Jun '12

20 Jun '12

Hi All: I have an HP DL380G5 server which I am loading CentOS 6.2 on and it does not appear to recognize all of the RAM installed on the server. The BIOS is reporting 26GB however top is reporting: Mem: 15720140k total, 418988k used, 15301152k free, 30256k buffers Swap: 17956856k total, 0k used, 17956856k free, 135536k cached and free is reporting: total used free shared buffers cached Mem: 15720140 418848 15301292 0 30256 135536 -/+ buffers/cache: 253056 15467084 Swap: 17956856 0 17956856 I have tried adding the mem= parameter to the /boot/grub/grub.conf file as in: title CentOS (2.6.32-220.17.1.el6.i686) root (hd0,0) kernel /vmlinuz-2.6.32-220.17.1.el6.i686 ro [SNIP] initrd /initramfs-2.6.32-220.17.1.el6.i686.img mem=26624M but this has not appeared to work. Any suggestions would be gratefully appreciated. TIA Regards, Hugh -- Hugh E Cruickshank, Forward Software, www.forward-software.com

6 14

Deleting Files
by Matt 20 Jun '12

20 Jun '12

I want to safely delete all files in a certain directory that are exactly 32 characters long. This is on CentOS 5.x. How would I do that?

5 5

RHEL6.3 is on rhn
by Rainer Traut 20 Jun '12

20 Jun '12

Just fyi, since yesterday evening RHEL 6.3 is available on rhn, but I see no announcement yet. [root@rhel6-test ~]# uname -a Linux rhel6-test 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux [root@rhel6-test ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.3 (Santiago) Rainer

1 0

PMA attacks
by m.roth＠5-cent.us 20 Jun '12

20 Jun '12

It appears to be a low-level attack, not so frequent as to be banned permanently, just a number of times a day. I did google on this, and I gather it's looking for phpmyadmin. We've been getting one from one specific network in Russia for weeks Here are more information about 91.201.64.24: [Querying whois.ripe.net] [whois.ripe.net] <snip> % Information related to '91.201.64.0 - 91.201.67.255' inetnum: 91.201.64.0 - 91.201.67.255 netname: Donekoserv descr: DonEkoService Ltd country: RU <snip> But now I'm seeing the same from Azerbaijan, and France, and elsewhere. Two questions: first, are other folks seeing this? and second, I can't imagine malware this stupid, to keep hitting the same sites over and over when it's not found, rather than bad password or user, so I'm wondering if this could be a targetting vector for an upcoming serious attack using another vector. Opinions? mark

4 3

My ROOT PASSWORD Is GETTING RESET After EVERY REBOOT
by chiong lawrence 19 Jun '12

19 Jun '12

Hello there, I'm using CentOS v6.2 x86_64bit. I'm confuse and can't figured-it-out after I run my KVM virtual machine the root password is getting RESET after every reboot of my VM. Any help is very much appreciated. Thank you. ** *Please consider the environment before printing this email.*

1 0

Re: [CentOS] Resizing est4 filesystem while mounted
by Jeff Boyce 19 Jun '12

19 Jun '12

Replying to the daily digest, with my response at the bottom. > Message: 18 > Date: Mon, 18 Jun 2012 22:28:31 +0200 > From: Dennis Jacobfeuerborn <dennisml(a)conversis.de> > Subject: Re: [CentOS] Resizing est4 filesystem while mounted > To: centos(a)centos.org > Message-ID: <4FDF8F6F.8030300(a)conversis.de> > Content-Type: text/plain; charset=ISO-8859-1 > > On 06/18/2012 10:09 PM, Jeff Boyce wrote: >> Replying to the daily digest, with my response at the bottom. >> >> >> >>> Message: 13 >>> Date: Fri, 15 Jun 2012 12:22:08 -0700 >>> From: Ray Van Dolson <rayvd(a)bludgeon.org> >>> Subject: Re: [CentOS] Resizing est4 filesystem while mounted >>> To: centos(a)centos.org >>> Message-ID: <20120615192207.GA23689(a)bludgeon.org> >>> Content-Type: text/plain; charset=us-ascii >>> >>> On Fri, Jun 15, 2012 at 12:10:09PM -0700, Jeff Boyce wrote: >>>> Greetings - >>>> >>>> I had a logical volume that was running out of space on a virtual >>>> machine. >>>> I successfully expanded the LV using lvextend, and lvdisplay shows that >>>> it >>>> has been expanded. Then I went to expand the filesystem to fill the new >>>> space (# resize2fs -p /dev/vde1) and I get the results that the >>>> filesystem >>>> is already xx blocks long, nothing to do. If I do a # df -h, I can see >>>> that >>>> the filesystem has not been extended. I could kick the users off the >>>> VM, >>>> reboot the VM using a GParted live CD and extend the filesystem that >>>> way, >>>> but I thought that it was possible to do this live and mounted? The RH >>>> docs >>>> say this is possible; the man page for resize2fs also says it is >>>> possible >>>> with ext4. What am I missing here? This is a Centos 6.2 VM with an ext4 >>>> filesystem. The logical volumes are setup on the host system which is >>>> also >>>> a Centos 6.2 system. >>> >>> Try resize4fs (assuming your FS is ext4). >>> >>> Ray >> >> Well, I have never seen a reference to resize4fs before (and yes my FS is >> ext4). It is not on my Centos 6.2 system, and doing a little searching >> through repositories for that specifically, or e4fsprogs, and I can't >> find >> it anywhere to even try it. Any google reference seems to point back to >> resize2fs. I ended up booting a live SystemRescueCD and using GParted >> via >> the GUI. My notes indicate that is what I had done previously also. I >> am >> still stumped, everything that I have read indicates that resize2fs can >> do a >> live resizing on ext4 file systems. Can anybody confirm or deny this? >> Is >> the reason I can't do this because it is on an LVM logical volume? >> Thanks. > > Please post some details about your storage topology. Without this > information its not really possible to be sure what is going on. > resizefs cannot work as long as the underlying layers don't see any change > in size and you didn't seem to look for that. > > Regards, > Dennis I provided some of that information in my original post, but if you can help explain why I couldn't seem to resize the file system while mounted here is more information. Host system is Centos 6.2 on a Dell PE T610 with hardware raid on a PERC H700. Raid 5 is setup across three disks with a fourth hot spare. I have created a volume group within the raid 5 encompassing most of my drive space. Within the VG I have created numerous logical volumes that are assigned to specific systems. Volume Group: vg_mei Logical Volumes: lv_earthroot lv_earthswap lv_earthvar lv_sequoiaroot lv_sequoiaswap lv_sequoiavar lv_sequoiahome lv_sequoiaecosystem Earth is my host system and Sequoia is one of the guest systems. lv_sequoiaecosystem is the space dedicated to our Samba server and is the LV that I was expanding to make more space available to the rest of the staff. I had successfully extended lv_sequoiaecosystem using the following command from root on earth (lvextend -L+50G /dev/vg_mei/lv_sequoiaecosystem). Issuing the command (lvdisplay /dev/vg_mei/lv_sequoiaecosystem) following this showed that the LV was successfully extended from 100 to 150 GB. I then logged onto sequoia as root and issued a df -h to determine which device needed the file system to be resized (/dev/vde1). The output below is current, after I resized the filesystem using GParted. [root@sequoia ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda2 4.5G 2.5G 1.8G 59% / tmpfs 1004M 112K 1004M 1% /dev/shm /dev/vda1 485M 55M 406M 12% /boot /dev/vde1 148G 85G 56G 61% /ecosystem /dev/vdd1 20G 1.3G 18G 7% /home /dev/vdc1 2.0G 266M 1.7G 14% /var Then from root on sequoia I issued the command (resize2fs -p /dev/vde1) and got back the result that the filesystem is already 26214144 blocks long, nothing to do. That is when I posted my first question about not being able to resize a live mounted filesystem. Is that enough information for your question, or is there something that I am not providing? Thanks. Jeff

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