Discuss

discuss@lists.centos.org

34753 discussions

"print notifier" icon
by Frank Cox 04 Jun '09

04 Jun '09

The Print Notifier icon appears in on my Gnome panel when I print something. After the job is completed, the icon grays out, but it's still present. With my Fedora setup, the icon appears when the job is active or pending, then it goes away completely until the next time I print something. How can I make Centos 5.3 do the same thing? -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com

2 3

Instability with later 4.x kernels?
by Benjamin Smith 04 Jun '09

04 Jun '09

I have an Athlon with about 10 HDDs plugged in, primarily to do Disk2Disk backups. Some drives are PATA, some are SATA, some are USB. A strange concoction, but it's been relatively stable for some 4-5 years, despite numerous upgrades and so on. It's been running CentOS 4 for a long, long time. (years) Recently, I've started to have problems with its stability, and after 2 weeks of swapping hardware, found that using an earlier kernel restores its stability! It takes a few days to determine if anything "goes south", so debugging is very, very slow. But I get random read errors, either SCSI errors or (a few times) HDA read errors. Once the read errors begin, the system becomes very unresponsive, and often won't restart, even though I wait for hours, without my hitting the "kill switch". # uname -a Linux backuphost 2.6.9-67.0.22.EL #1 Wed Jul 23 17:17:45 EDT 2008 i686 athlon i386 GNU/Linux The failures occur on all /dev/sd* devices, even those that are USB. Once, /dev/hdc had a similar problem after /dev/sdb had failed. Don't know if the mapping below helps? /dev/hda - PATA, on motherboard, 20 GB. /dev/hdb - IDE CDROM /dev/hdc - on motherboard 500 GB IDE /dev/hdd - on motherboard 300 GB IDE /dev/hde - on PCI card, 500 GB IDE /dev/sda - SATA, on a PCI card, 1 TB /dev/sdb - SATA, on a PCI card 1 TB /dev/sdc - USB on a USB 2.0 PCI card, 750 GB /dev/sde - USB on a USB 2.0 PCI card, 750 GB /dev/sdf - USB on a USB 2.0 PCI card, 1 TB Here's what I see in the /var/log/messages: May 27 05:08:42 hume ntpd[4844]: kernel time sync enabled 0001 May 27 08:01:01 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 08:01:01 hume kernel: end_request: I/O error, dev sda, sector 12847 May 27 08:01:01 hume kernel: EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0 May 27 08:01:01 hume kernel: May 27 08:14:27 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 08:14:27 hume kernel: end_request: I/O error, dev sda, sector 12847 May 27 08:14:27 hume kernel: EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0 May 27 08:14:27 hume kernel: May 27 10:28:30 hume ntpd[4844]: synchronized to 63.240.161.99, stratum 2 May 27 11:48:07 hume sshd(pam_unix)[26873]: session opened for user root by (uid=0) May 27 11:48:10 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 11:48:10 hume kernel: end_request: I/O error, dev sda, sector 12847 May 27 11:48:10 hume kernel: EXT3-fs error (device sda1): ext3_find_entry: reading directory #2 offset 0 May 27 11:48:10 hume kernel: May 27 11:48:16 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 11:48:16 hume kernel: end_request: I/O error, dev sda, sector 12847 May 27 11:48:16 hume kernel: EXT3-fs error (device sda1): ext3_readdir: directory #2 contains a hole at offset 0 May 27 11:48:23 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 11:48:23 hume kernel: end_request: I/O error, dev sda, sector 12847 May 27 11:48:23 hume kernel: EXT3-fs error (device sda1): ext3_readdir: directory #2 contains a hole at offset 0 May 27 11:48:24 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 11:48:24 hume kernel: end_request: I/O error, dev sda, sector 12847 May 27 11:48:24 hume kernel: EXT3-fs error (device sda1): ext3_readdir: directory #2 contains a hole at offset 0 May 27 11:48:38 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 11:48:38 hume kernel: end_request: I/O error, dev sda, sector 0 May 27 11:48:38 hume kernel: Buffer I/O error on device sda, logical block 0 May 27 11:48:38 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 11:48:38 hume kernel: end_request: I/O error, dev sda, sector 8 May 27 11:48:38 hume kernel: Buffer I/O error on device sda, logical block 1 May 27 11:48:38 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 11:48:38 hume kernel: end_request: I/O error, dev sda, sector 16 May 27 11:48:38 hume kernel: Buffer I/O error on device sda, logical block 2 May 27 11:48:38 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 11:48:38 hume kernel: end_request: I/O error, dev sda, sector 24 May 27 11:48:38 hume kernel: Buffer I/O error on device sda, logical block 3 May 27 11:48:38 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 11:48:38 hume kernel: end_request: I/O error, dev sda, sector 32 May 27 11:48:38 hume kernel: Buffer I/O error on device sda, logical block 4 May 27 11:48:38 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 11:48:38 hume kernel: end_request: I/O error, dev sda, sector 40 May 27 11:48:38 hume kernel: Buffer I/O error on device sda, logical block 5 May 27 11:48:38 hume kernel: SCSI error : <0 0 0 0> return code = 0x40000 May 27 11:48:38 hume kernel: end_request: I/O error, dev sda, sector 48 May 27 11:48:38 hume kernel: Buffer I/O error on device sda, logical block 6 .. MANY MEGABYTES OF STUFF LIKE THIS .. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

XSS (was Re: Centos 5.3 -> Apache - Under Attack ? Oh hell....)
by Michael A. Peters 04 Jun '09

04 Jun '09

Bob Hoffman wrote: > Since each install uses the same pages basically, it is easy for a autobot > to find them all and zero day your forums, xss your whatever, and so on. > > Dang scary to leave JS on at all....even though you basically have too. Mozilla is beginning to address this issue with Content Security Policy -=- http://people.mozilla.org/~bsterne/content-security-policy/ -=- CSP will require pro-active webmasters who use it and browsers that enforce the client side enforcement, but it's a step in the right direction. I wrote a php class that partially implements CSP server side as an output filter -=- http://www.clfsrpm.net/xss/ -=- It's DOMDocument based and thus requires the php xml stuff, I've only tested it under php 5.2.9 but it should work in 5.x. The class does have some limitations, namely the document must be fully constructed and sent through the class before any of it is sent to the browser so web apps that do a lot of echo() and print() have to be re-written to not send anything until the page is fully constructed, and I've also found it has performance issues on complex pages with a lot of nodes, so for those kinds of pages I just create the page with the dynamic content first, send it through the filter, then create the nodes for static content I know is clean and use DOMDocument facilities to add those nodes before outputing the page to the client. It's not possible to completely implement CSP server side, but the class will catch most violations of a CSP policy and thus give some protection to users who are not running a CSP aware web browser. Another gotcha with the class, it seems importHTML() is not mb safe so if using importHTML() to get the document into a DOMDocument object for filtering, and the document contains any multi-byte characters, it seems libxml2 will encode them and there seems to be no way to stop it from doing it (at least with the php wrapper to libxml2). However if the document to be filtered is xhtml, you can use importXML() on it libxml2 does the right thing in leaving the mb characters alone. Once filtered, you can use saveHTML() to produce html instead of xhtml for browser compatibility, it seems saveHTML() is mb safe.

1 0

Adding an 'official' CentOS image to the Amazon EC2(Electronic Compute Cloud)
by Richard Shade 04 Jun '09

04 Jun '09

Sorry for not replying to this earlier, I just saw this thread because of the newsletter. We have had CentOS Images running in the cloud since 09/06/2007, and there have had a public script out for it, you can check us out in the Amazon catalog here: http://developer.amazonwebservices.com/connect/entry!default.jspa?categoryI…. This also has a build script here: http://s3.amazonaws.com/rightscale_scripts/CentOS5_2V4_0_2_Beta.sh, if you want to roll your own. If anyone needs any help or has any question on this shoot me an email. Also thanks to the CentOS team for all your hard work. -- Thanks, Richard Shade RightScale http://www.rightscale.com/

2 2

NOOBE help
by Sam Drinkard 03 Jun '09

03 Jun '09

I know, I should not have to ask this question, but it appears that ALL my previous yum.repos.d entries have been trashed, with the only ones left is base, CentOS Media then the mirrors.rpmforge.reo, rhel-mondo.repo, rpmforge.repo, and webmin.repo. I've been bitten by the mixing of repositories before and want to avoid that scenario. Something is amok in the existing, and it throws all kinds of errors about something not found or such, so I'm asking some kind soul of they would share their working repo file structure for me? I *think* I have protect base, and priorities installed already, but will double check. This is yet another new clean install after a botched attempt to recover some data from a mondo-rescue DVD which apparently dis some ugly things to stuff including grub. Anyhow, my main items of interest would be stuff like clamav-milter, spamass-milter, and anything else dealing with handling spam, not to mention some other scientific software like udunits, perhaps Grads (if exists), etc.. all geared towards weather. My humble thanks and apologies for my dumbness for not keeping good backups of important stuff.. it WONT happen again ! head hanging low :( Sam

2 1

Can't play DVD movies on CentOS 5.3 after following guidance on the wiki
by David McGuffey 03 Jun '09

03 Jun '09

8 13

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

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