Discuss June 2009

discuss@lists.centos.org

286 participants
327 discussions

how to debug random server reboots
by Rudi Ahlers 03 Jun '09

03 Jun '09

Hi all, One of our CentOS 5.3 randomly reboots, at different times of the day, and I can't see why it's doing it. I have looked through the logs, but don't see any thing in there that shows me why it has rebooted. How can I debug this? Here's a snipped from the log, around the time of the reboot: Jun 2 14:59:59 usaxen02 kernel: EXT3-fs: mounted filesystem with ordered data mode. Jun 2 15:00:06 usaxen02 kernel: kjournald starting. Commit interval 5 seconds Jun 2 15:00:06 usaxen02 kernel: EXT3 FS on dm-8, internal journal Jun 2 15:00:06 usaxen02 kernel: EXT3-fs: mounted filesystem with ordered data mode. Jun 2 15:00:39 usaxen02 kernel: device vifvenu0 entered promiscuous mode Jun 2 15:00:39 usaxen02 kernel: ADDRCONF(NETDEV_UP): vifvenu0: link is not ready Jun 2 21:00:39 usaxen02 logger: /etc/xen/scripts/vif-bridge: iptables -A FORWARD -m physdev --physdev-in vifvenu0 -s 72.9.241.226 72.9.241.227 72.9.2 41.232 72.9.247.207 -j ACCEPT failed. If you are using iptables, this may affect networking for guest domains. Jun 2 15:00:43 usaxen02 kernel: blkback: ring-ref 8, event-channel 6, protocol 1 (x86_64-abi) Jun 2 15:00:43 usaxen02 kernel: blkback: ring-ref 9, event-channel 7, protocol 1 (x86_64-abi) Jun 2 15:00:43 usaxen02 kernel: ADDRCONF(NETDEV_CHANGE): vifvenu0: link becomes ready Jun 2 15:00:43 usaxen02 kernel: xenbr1: topology change detected, propagating Jun 2 15:00:43 usaxen02 kernel: xenbr1: port 5(vifvenu0) entering forwarding state Jun 2 17:30:22 usaxen02 syslogd 1.4.1: restart. Jun 2 17:30:22 usaxen02 kernel: klogd 1.4.1, log source = /proc/kmsg started. Jun 2 17:30:22 usaxen02 kernel: Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol01 ide0=noprobe) Jun 2 17:30:22 usaxen02 kernel: Linux version 2.6.18-128.1.10.el5xen (mockbuild(a)builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Thu May 7 11:07:18 EDT 2009 Jun 2 17:30:22 usaxen02 kernel: BIOS-provided physical RAM map: Jun 2 17:30:22 usaxen02 kernel: Xen: 0000000000000000 - 00000001de804000 (usable) Jun 2 17:30:22 usaxen02 kernel: DMI 2.4 present. Jun 2 17:30:22 usaxen02 kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Jun 2 17:30:22 usaxen02 kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled) Jun 2 17:30:22 usaxen02 kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Jun 2 17:30:22 usaxen02 kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled) Jun 2 17:30:22 usaxen02 kernel: ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) Jun 2 17:30:22 usaxen02 kernel: ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) Jun 2 17:30:22 usaxen02 kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) Jun 2 17:30:22 usaxen02 kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 Jun 2 17:30:22 usaxen02 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) Jun 2 17:30:22 usaxen02 kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) Jun 2 17:30:22 usaxen02 kernel: Setting APIC routing to xen Jun 2 17:30:22 usaxen02 kernel: Using ACPI (MADT) for SMP configuration information Jun 2 17:30:22 usaxen02 kernel: Allocating PCI resources starting at d4000000 (gap: d0000000:2ff00000) -- Kind Regards Rudi Ahlers CEO, SoftDux Hosting Web: http://www.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532

6 9

Re: [CentOS] Random server reboot after update to CentOS 5.3
by Dave Jones 03 Jun '09

03 Jun '09

On Friday 22 May 2009, Peter Hopfgartner wrote: ... >> Would it make sense to install the kernel from CentOS 5.2? Any >> contraindications? >As others have said, you should still have the 5.2 kernel around. Just change >the grub.conf and reboot. It makes no sense to start swapping around hardware >until you've tried to revert the kernel. >That said, we've seen hangs and strange kernel messages on several different >server platforms (HP DL140g3: NMI-related messages logged, HP DL160g5: hangs >semi-randomly) with the new 5.3 kernels. All of these problems could be >worked around by booting with the kernel option "nmi_watchdog=0". >/Peter I am experiencing the same issue with random reboots after a 5.3 upgrade. Sometimes it will go for days without rebooting then today it has rebooted 6 times at random times. I have modified grub.conf to go back to 2.6.18-92.1.22.el5xen on my dom0 and my only domU so we will see what happens (or hopefully doesn't happen) the next few days. I have a 3.0 P4 CPU with HT that does not support 64-bit so it's running an i686 kernel. It does have a Broadcom NIC like an earlier post was suspicious of: 02:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 02) 02:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02) I have upgraded about 8 other servers with no random reboot problems but they are all running on a newer processors with a 64-bit kernel. -- Dave Jones

4 4

Removing old kernels
by Frank M. Ramaekers 03 Jun '09

03 Jun '09

I have the following kernels on my /boot: 2.6.18-128.1.6 2.6.18-92.1.18 2.6.18-92.1.22 I'm low on /boot space and need to remove the oldest version. It appears that I cannot use yum to remove since all of the versions are the same (only the release is different). I believe that I can use rpm to remove the old version, but I also need to remove them from the grub.conf. Any other considerations and/or methods? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr. Fax: (254)741-5777 Waco, Texas 76710 _____________________________________________________ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at PrivacyAct(a)ailife.com.

8 10

Re: [CentOS] release/update question
by Radu-Cristian FOTESCU 03 Jun '09

03 Jun '09

--- On Tue, 6/2/09, Kai Schaetzl <maillists(a)conactive.com> wrote: > Point releases are just freezes in time. There are no > "special" updates for point releases, only for the > "current" release. This is what we all *believe* we know (e.g. "5"-current is now "5.3"+updates). However, TUV seems to have had a different opinion st some point in the past, or at least this is what Johnny understood. Read carefully this: http://bugs.centos.org/view.php?id=2481 Excerpts: ============================== we are trying something new to correspond to an upcoming 5.y.z release scheme from upstream. in the scheme, there will be a 5.1.z and 5.2.z tree ... those trees will be available for an extended period of time (5.1 and 5.2 ... each with different updates). ============================== we are not exactly sure how or even when upstream will do this z tree thing ============================== we do not have any intention of doing 5.1.1 or 5.1.2, just 5.1 ... and maintaining it while it is maintained upstream. ============================== Also, we do not plan to - as Johnny has already pointed out - do any 5.1.1 or 5.1.2 or 5.1.3 releases, since again that would be counter productive and leave users with a false sense of security thinking they have the latest patch levels for each machine - when they might not. ============================== So there *should* have existed: * 5.1-only updates issued post-5.2; * 5.1-only and 5.2-only updates issued post-5.3; etc. AFAIK, this never happened. Is the 5.x.z tree concept dead-before-birth?! Thanks, R-C __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/

6 10

CentOS-announce Digest, Vol 52, Issue 2
by centos-announce-request＠centos.org 03 Jun '09

03 Jun '09

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-2009:1076-01: Low CentOS 2 i386 End Of Life (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Wed, 03 Jun 2009 13:25:10 +1000 From: John Newbigin <jnewbigin(a)ict.swin.edu.au> Subject: [CentOS-announce] CESA-2009:1076-01: Low CentOS 2 i386 End Of Life To: centos-announce(a)centos.org Message-ID: <4A25ED16.4020809(a)ict.swin.edu.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed RHSA-2009:1076-01 End Of Life This is the End Of Life notification for CentOS-2. As per the upstream vendors errata support policy, updates for CentOS-2 ended on May 31, 2009. It is recommended that any system still running CentOS 2 should be upgraded to a more recent version of CentOS to ensure continued security and bug fix support. Upgrade information can be found here http://wiki.centos.org/MigratingTwoToFive More details are available from the RedHat web site at https://rhn.redhat.com/errata/rh21as-errata.html Thank you to everyone who helped make this project possible. The CAOS and CentOS projects, the unnamed upstream vendor and of course, the users who gave it a reason to exist. After 5 years at the helm of CentOS-2, I look forward to working on some new projects both CentOS and elsewhere. This might be the last update announcement I post but it won't be the last time you see my name. John. -- John Newbigin ITS Senior Analyst / Programmer Faculty of Information and Communication Technologies Swinburne University of Technology Melbourne, Australia http://www.ict.swin.edu.au/staff/jnewbigin ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 52, Issue 2 **********************************************

1 0

Harware vs Kernel RAID (was Re: External SATA enclosures: SiI3124 and CentOS 5?)
by Michael A. Peters 03 Jun '09

03 Jun '09

-=- starting as new thread as it is off topic from controller thread -=- Ross Walker wrote: > > The real key is the controller though. Get one that can do hardware > RAID1/10, 5/50, 6/60, if it can do both SATA and SAS even better and > get a battery backed write-back cache, the bigger the better, 256MB > good, 512MB better, 1GB best. I've read a lot of different reports that suggest at this point in time, kernel software raid is in most cases better than controller raid. The basic argument seems to be that CPU's are fast enough now that the limitation on throughput is the drive itself, and that SATA resolved the bottleneck that PATA caused with kernel raid. The arguments then go on to give numerous examples where a failing hardware raid controller CAUSED data loss, where a raid card died and an identical raid card had to be scrounged from eBay to even read the data on the drives, etc. - problems that apparently don't happen with kernel software raid. The main exception I've seen to using software raid are high availability setups where a separate external unit ($$$) provides the same hard disk to multiple servers. Then the raid can't really be in the kernel but has to be in the hardware. I'd be very interested in hearing opinions on this subject.

9 16

Hi ALL!!!
by Andrey Garkin 03 Jun '09

03 Jun '09

I have a one problem with Raid controller Tekram TR-822... I'm using dmraid software: root@ns1: / $ dmraid -r /dev/sda: sil, "sil_ajacddafagff", mirror, ok, 156299440 sectors, data@ 0 /dev/sdb: sil, "sil_ajacddafagff", mirror, ok, 156299440 sectors, data@ 0 When I'm start dmraid -ay: root@ns1: / $ dmraid -ay RAID set "sil_ajacddafagff" was not activated And I see from dmesg: device-mapper: table: 253:0: mirror: Device lookup failure device-mapper: ioctl: error adding target to table My system centos My kernel 2.6.18-128.1.10.el5.centos.plus

3 2

How to remove the wrong wireless firmware module
by David McGuffey 03 Jun '09

03 Jun '09

3 2

yum update error this morning
by Jerry Geis 03 Jun '09

03 Jun '09

I am getting the following "yum update" error this morning. C 5.3 x86_64. What shall I do? Jerry ----------- yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: centos.mirror.nac.net * updates: centos.mirror.nac.net * addons: mirrors.unbornmedia.com * extras: centos.mirror.nac.net Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package vsftpd.x86_64 0:2.0.5-12.el5_3.1 set to be updated ---> Package sos.noarch 0:1.7-9.16.el5_3.5 set to be updated ---> Package pidgin.i386 0:2.5.5-3.el5 set to be updated ---> Package poppler.x86_64 0:0.5.4-4.4.el5_3.9 set to be updated ---> Package audit-libs.x86_64 0:1.7.7-6.el5_3.3 set to be updated ---> Package pango.i386 0:1.14.9-5.el5.centos set to be updated ---> Package audit-libs-python.x86_64 0:1.7.7-6.el5_3.3 set to be updated ---> Package acpid.x86_64 0:1.0.4-7.el5_3.1 set to be updated ---> Package audit.x86_64 0:1.7.7-6.el5_3.3 set to be updated ---> Package libwmf.x86_64 0:0.2.8.4-10.2 set to be updated ---> Package libpurple.i386 0:2.5.5-3.el5 set to be updated ---> Package crash.x86_64 0:4.0-7.2.3.el5.centos.1 set to be updated ---> Package ipsec-tools.x86_64 0:0.6.5-13.el5_3.1 set to be updated ---> Package file.x86_64 0:4.17-15.el5_3.1 set to be updated ---> Package freetype.x86_64 0:2.2.1-21.el5_3 set to be updated ---> Package libpurple.x86_64 0:2.5.5-3.el5 set to be updated ---> Package freetype-devel.x86_64 0:2.2.1-21.el5_3 set to be updated ---> Package pidgin.x86_64 0:2.5.5-3.el5 set to be updated ---> Package httpd.x86_64 0:2.2.3-22.el5.centos.1 set to be updated ---> Package libwmf.i386 0:0.2.8.4-10.2 set to be updated ---> Package gnome-session.x86_64 0:2.16.0-6.el5.centos.2 set to be updated ---> Package net-snmp-libs.x86_64 1:5.3.2.2-5.el5_3.1 set to be updated ---> Package audit-libs.i386 0:1.7.7-6.el5_3.3 set to be updated ---> Package httpd-manual.x86_64 0:2.2.3-22.el5.centos.1 set to be updated ---> Package freetype.i386 0:2.2.1-21.el5_3 set to be updated ---> Package mod_ssl.x86_64 1:2.2.3-22.el5.centos.1 set to be updated ---> Package pango.x86_64 0:1.14.9-5.el5.centos set to be updated ---> Package freetype-devel.i386 0:2.2.1-21.el5_3 set to be updated ---> Package ntp.x86_64 0:4.2.2p1-9.el5.centos.2 set to be updated Traceback (most recent call last): File "/usr/bin/yum", line 29, in ? yummain.user_main(sys.argv[1:], exit_code=True) File "/usr/share/yum-cli/yummain.py", line 229, in user_main errcode = main(args) File "/usr/share/yum-cli/yummain.py", line 145, in main (result, resultmsgs) = base.buildTransaction() File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 647, in buildTransaction (rescode, restring) = self.resolveDeps() File "/usr/lib/python2.4/site-packages/yum/depsolve.py", line 704, in resolveDeps for po, dep in self._checkFileRequires(): File "/usr/lib/python2.4/site-packages/yum/depsolve.py", line 939, in _checkFileRequires if not self.tsInfo.getOldProvides(filename) and not self.tsInfo.getNewProvides(filename): File "/usr/lib/python2.4/site-packages/yum/transactioninfo.py", line 414, in getNewProvides for pkg, hits in self.pkgSack.getProvides(name, flag, version).iteritems(): File "/usr/lib/python2.4/site-packages/yum/packageSack.py", line 300, in getProvides return self._computeAggregateDictResult("getProvides", name, flags, version) File "/usr/lib/python2.4/site-packages/yum/packageSack.py", line 470, in _computeAggregateDictResult sackResult = apply(method, args) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 861, in getProvides return self._search("provides", name, flags, version) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 43, in newFunc return func(*args, **kwargs) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 837, in _search for pkg in self.searchFiles(name, strict=True): File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 43, in newFunc return func(*args, **kwargs) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 586, in searchFiles self._sql_pkgKey2po(rep, cur, pkgs) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 470, in _sql_pkgKey2po pkg = self._packageByKey(repo, ob['pkgKey']) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 413, in _packageByKey po = self.pc(repo, cur.fetchone()) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 68, in __init__ self._read_db_obj(db_obj) File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 94, in _read_db_obj setattr(self, item, _share_data(db_obj[item])) TypeError: unsubscriptable object

4 4

Yum-complete-transaction wants to wipe my system out
by Eduardo Grosclaude 03 Jun '09

03 Jun '09

After some enabling/disabling new repos (pgdg for PostgreSQL specifically) and admittedly some yum action that may have gone uncompleted, I am advised to run yum-complete-transaction. However, when I attempt to do this, yum warns that 225 packages will be erased, all of which I deeply care for. How can I safely back out of this situation? Thank you in advance -- Eduardo Grosclaude Universidad Nacional del Comahue Neuquen, Argentina

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss June 2009