Discuss

discuss@lists.centos.org

34758 discussions

CentOS-announce Digest, Vol 87, Issue 18
by centos-announce-request＠centos.org 31 May '12

31 May '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:0703 CentOS 6 libatasmart Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 31 May 2012 10:41:00 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2012:0703 CentOS 6 libatasmart Update To: centos-announce(a)centos.org Message-ID: <20120531104100.GA6530(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2012:0703 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-0703.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e1f27d6dcd444a8984ae6765903a59ab58a0f587210ab4e1b0e31b0dd4191e9c libatasmart-0.17-4.el6_2.i686.rpm 6aa8a40d617eb33f0c6fdc5085ad9f4ea90b99a5f1c05adc347e6b87ad488303 libatasmart-devel-0.17-4.el6_2.i686.rpm x86_64: e1f27d6dcd444a8984ae6765903a59ab58a0f587210ab4e1b0e31b0dd4191e9c libatasmart-0.17-4.el6_2.i686.rpm a8dd5db94c2570cc254a794e2c885455b9799e1c9f2bfcfcc132a528e34508d2 libatasmart-0.17-4.el6_2.x86_64.rpm 6aa8a40d617eb33f0c6fdc5085ad9f4ea90b99a5f1c05adc347e6b87ad488303 libatasmart-devel-0.17-4.el6_2.i686.rpm 3e38ab0e8b7f5c376dda374e30544f954cd3b021abb8a5c97bd9f53c29d013a9 libatasmart-devel-0.17-4.el6_2.x86_64.rpm Source: b23a408d799b941a2a0fc4a77bd33e7780d6cb89ab7adf8ef63d722d70804b5d libatasmart-0.17-4.el6_2.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 87, Issue 18 ***********************************************

1 0

Centos 6.2 ATI Rage XL on board graphics seg faults when setting up the screen saver
by Seth Bardash 31 May '12

31 May '12

I have installed Centos 6.2 on: 1) Tyan S2892 with ATI on board Rage XL graphics ( Centos x86_64 version), 8GB memory, 3ware Raid array 2) Supermicro Dual Xeon Single core, old machine, with ATI onboard Rage XL graphics (Centos i386 version), 12GB memory, 3ware Raid array Both machines exhibit the same error. While trying to select a screen saver (clock or blank screen) the application seg faults. Other machines that we have installed 6.2 on with either a newer graphics chip set on board or a separate graphics card seem to work fine. Anyone with a work around or fix for this? Has anyone reported this upstream as a bug? Thanks in advance, -- Seth Bardash Integrated Solutions and Systems LLC 1510 Old North Gate Road Colorado Springs, CO 80921 seth(a)integratedsolutions.org Failure cannot survive knowledge and perseverance!

1 0

Just Stuck
by Gene Poole 31 May '12

31 May '12

OK, I did the deal and I am in the process of upgrading/migrating from CentOS 5.8 x86_64 to CentOS 6.2 x86_64. But, I'm stuck with a gnome GUI that only sees 1024x768. Under CentOS 5.8 it saw 1920x1080 (without much work from me). The command I was used to , system-config-display, is gone and I've read that xrandr is the replacement. I can't find a usage document on this command. The basic description of the hardware involved is: nVidia GT 7300 video card Viewsonic 24" monitor I don't have the exact specs for this hardware, but I can post it later if needed. I've run the following command: xrandr -q And sometimes it returns a list of modes that range from 5 entries to 15 entries. Any help will be appreciated! TIA, Gene Poole + It's impossible for everything to be true. +

4 3

iSCSI offload with Broadcom NetXtreme II BCM5709.
by Svavar Örn Eysteinsson 31 May '12

31 May '12

Hello all. We recently purchased HP Proliant DL380 G7 server and also a HP Lefthand P4500 G2 24TB iSCSI box. The server itself has Quad Ethernet based on the BCM5709 Chipset from Broadcom (NetXtreme II). My main question is about iSCSI offload mechanism, as iSCSI itself is pretty new to me but I have gotten a good hold on it tho. I have managed to setup and configured our Lefthand box into our iSCSI Network. iSCSI network : 192.168.200.0/24 I have also managed to setup and configure a fully operational Software based iSCSI traffic from the server to the Target without problems. Everything just works fine. Until I thought about iSCSI offload functionality offered by the Network Adapter in the server. As for the Software based iSCSI connection I have bonded(NIC Teamed) two NIC's on the server into a ALB(Adaptive Load Balancing) configuration. Those are eth2,eth3 interfaces configured as bond1 with IP address of : 192.168.200.20 (iSCSI network). My decision to team up eth2 and eth3 into ALB was clearly based on the HP Lefthand configuration guidelines. They state that the Lefthand box itself should be configured into ALB. So I configured the server also. But, am I misunderstanding the iSCSI thing about offload and or network configurations ? If I'm going to use offload mechanisms do I need to get rid of the bonding setup ? I'm asking because the server offers 4 interfaces, and also 4 iscsi offload interfaces :S These are the messages from dmesg : bnx2: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.1.12b (Oct 14, 2011) bnx2 0000:03:00.0: eth0: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f4000000, IRQ 16, node addr e4:11:5b:b6:92:e0 bnx2 0000:03:00.1: eth1: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f2000000, IRQ 17, node addr e4:11:5b:b6:92:e2 bnx2 0000:04:00.0: eth2: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f8000000, IRQ 18, node addr e4:11:5b:b6:92:e4 bnx2 0000:04:00.1: eth3: Broadcom NetXtreme II BCM5709 1000Base-T (C0) PCI Express found at mem f6000000, IRQ 19, node addr e4:11:5b:b6:92:e6 After I launch up iscsi, and iscsid these messages appear : iscsi: registered transport (tcp) iscsi: registered transport (iser) Chelsio T3 iSCSI Driver cxgb3i v2.0.0 (Jun. 2010) iscsi: registered transport (cxgb3i) Chelsio T4 iSCSI Driver cxgb4i v0.9.1 (Aug. 2010) iscsi: registered transport (cxgb4i) cnic: Broadcom NetXtreme II CNIC Driver cnic v2.5.7g (September 23, 2011) bnx2 0000:03:00.0: eth0: Added CNIC device bnx2 0000:03:00.1: eth1: Added CNIC device bnx2 0000:04:00.0: eth2: Added CNIC device bnx2 0000:04:00.1: eth3: Added CNIC device Broadcom NetXtreme II iSCSI Driver bnx2i v2.7.0.4i (Nov 01, 2011) iscsi: registered transport (bnx2i) scsi123 : Broadcom Offload iSCSI Initiator bnx2i [04:00.01]: ISCSI_INIT passed scsi124 : Broadcom Offload iSCSI Initiator bnx2i [04:00.00]: ISCSI_INIT passed scsi125 : Broadcom Offload iSCSI Initiator scsi126 : Broadcom Offload iSCSI Initiator bnx2i [03:00.00]: ISCSI_INIT passed iscsiadm -m iface -P1 shows me these interfaces Iface: default Iface: iser Iface: bnx2i.00:00:00:00:00:00 Iface: bnx2i.e4:11:5b:b6:92:e1 Iface: bnx2i.e4:11:5b:b6:92:e5 Iface: bnx2i.e4:11:5b:b6:92:e7 Am I correct that you can't bind more then one interface to a iscsi target ? As the physical interfaces (eth2, eth3) are bonded together how would I use those virtual bnx2i (offload) interfaces as bond ? Is that what they call multipath ? Do I need multipath in this setup? One server, one switch, one iSCSI target box. Any help, information and guidelines would be much appreciated about this scenario. I'm really lost about this one, and would clearly like my server to operate at the top... :) The server is running up_to_date Centos 6.2 x_64 and with the newest Broadcom drivers. Best regards, Svavar O Reykjavik - Iceland

1 0

snmpd not working well with selinux?
by John Horne 31 May '12

31 May '12

Hello, I am trying to use SNMP on a CentOS 6.2 server, and am using the 'pass_persist' configuration command: pass_persist .1.3.6.1.4.1.141.1 /usr/local/sbin/snmp-iostat I have set the file context of 'snmpd_exec_t' on the snmp-iostat program. If I disable SELinux, then it all works fine (that is, I can then snmpget/snmpwalk for OIDs in the configured pass_persist OID, and values are returned). If I enable SELinux and start the snmpd daemon, as root, from the command line, then again it all works fine. However, if I enable SELinux, and startup the SNMP daemon using the 'service' command, as occurs at system boot, then I get no values returned. I get, for example: snmpwalk -v 2c -c public localhost enterprises.141.1.1.10 SNMPv2-SMI::enterprises.141.1.1.10 = No Such Instance currently exists at this OID (Yes I am using the enterprise number 141 which doesn't belong to us. I have applied for a site enterprise number, but heard nothing yet.) I really don't want to disable SELinux completely, but 'getsebool' shows no variables relating to SNMP so I am a bit stuck as to how I can get this to work. I also don't understand why it works with SELinux enabled when started from the command line, but not when started by the 'service' command. That seems very odd. Anyone any ideas about this? Thanks, John. -- John Horne Tel: +44 (0)1752 587287 Plymouth University, UK Fax: +44 (0)1752 587001

2 11

Request for CentOS stats
by Max Pyziur 31 May '12

31 May '12

Greetings, Are there any summary CentOS numbers available? The number of subscribers to this email list, and the number of server installs? Much thanks, Max Pyziur pyz(a)brama.com

12 21

Feedback for CentOS 6 on a recent Thinkpad X220 Tablet?
by Mathieu Baudier 31 May '12

31 May '12

Hello, I'm considering buying a Lenovo Thinkpad X220 *Tablet*. Does anybody run CentOS 6 on it? Is the multitouch working? Thanks in advance for any hint, Mathieu PS: I have checked thinkwiki.org already

1 0

Warning: Size of service_message struct (8376 bytes) is > POSIX-guaranteed atomic write size (512 bytes).
by Kaushal Shriyan 31 May '12

31 May '12

Hi, I am running Nagios on CentOS release 5.5 (Final). Any clue about the below warning? Please let me know if any one needs any additional information. /usr/sbin/nagios -v /etc/nagios/nagios.cfg Nagios 2.12 Copyright (c) 1999-2007 Ethan Galstad (http://www.nagios.org) Last Modified: 05-19-2008 License: GPL Reading configuration data... Running pre-flight check on configuration data... *Warning: Size of service_message struct (8376 bytes) is > POSIX-guaranteed atomic write size (512 bytes). Service checks results may get lost or mangled!* Checking services... Checked 341 services. Checking hosts... Checked 27 hosts. Checking host groups... Checked 13 host groups. Checking service groups... Checked 3 service groups. Checking contacts... Checked 27 contacts. Checking contact groups... Checked 10 contact groups. Checking service escalations... Checked 0 service escalations. Checking service dependencies... Checked 0 service dependencies. Checking host escalations... Checked 0 host escalations. Checking host dependencies... Checked 0 host dependencies. Checking commands... Checked 77 commands. Checking time periods... Checked 4 time periods. Checking extended host info definitions... Checked 0 extended host info definitions. Checking extended service info definitions... Checked 0 extended service info definitions. Checking for circular paths between hosts... Checking for circular host and service dependencies... Checking global event handlers... Checking obsessive compulsive processor commands... Checking misc settings... Total Warnings: 1 Total Errors: 0 Things look okay - No serious problems were detected during the pre-flight check Regards Kaushal

2 1

need assist with upstart config problem
by James B. Byrne 30 May '12

30 May '12

I am trying, without success, to create an upstart config file to automatically start and restart an ssh proxy. The command sting that I use in the script has been checked and verified from the shell but it fails in the upstart file. The file contents are: . . . # proxy is used to authenticate smtp submissions # so start it before the postfix service starts start on starting postfix # Take down proxy after postfix stops stop on stopped postfix # tell upstart that this script creates a daemon # and have upstart manage PID creation # but it is generally a bad idea to use this with a # script / end script block, use exec() instead # no fork in ssh #expect fork # restart automatically if connection fails respawn # for script debugging with strace # but not available in 0.6.3 of course #debug # use strace -p <pid> -o /tmp/upstart_debug.log -Ff -s 1024 -v # Setup script configuration variables: # localhost means we do not expose proxy to internet env LOCAL_HOST=localhost # port 143 is default IMAP service port for plain text connections env LOCAL_PORT=143 # ports less than 1024 require root privileges to establish # this must be a passwordless login using PKI certificates # requires one time setup of local root user ssh key and cert # and adding this host's root user cert to authorized_keys of # login host's root user. env LOGIN_USER=root # login PKI credentials for LOGIN_USER env LOGIN_IDENT=/root/.ssh/id_rsa # login host, may be different than remote host for port forwarding # must resolve to an address that sshd login server listens on env LOGIN_HOST=inet07.hamilton.harte-lyne.ca # the remote host destination for port forwarding env REMOTE_HOST=inet07.hamilton.harte-lyne.ca # port that remote service listens on env REMOTE_PORT=143 # Locate ssh binary env SSH_BINARY=/usr/bin/ssh # SSH options used: ### -D : "dynamic" app-level port forwarding - not used. ### # -f : run in background without a terminal implies -n # -i : identity file for pki login credentials # -l : login user name # -L local_host:local_port:remote_host:remote_port # : Establishes proxy connection from local port # port on the remote host. # -n : stdin from /dev/null, must be used when ssh is run in bg. # -N : Do not run a command on the remote host. Otherwise an # error results because we are not initiating a session. # -o ExitOnForwardFailure=yes : Wait until connection successfully # completes before daemonizing # -o ServerAliveInterval=15 : Keep connection alive every 15 seconds # -q : Run quietly, do not produce local output. # -T : disable pseudo-tty allocation # SSH options used env SSH_OPTIONS=" -o ExitOnForwardFailure=yes " env SSH_OPTIONS=${SSH_OPTIONS}" -o ServerAliveInterval=15 " # SSH switches used: env SSH_SWITCHES=" -fNqT " exec ${SSH_BINARY} ${SSH_OPTIONS} ${SSH_SWITCHES} -l ${LOGIN_USER} -i ${LOGIN_IDENT} -L ${LOCAL_HOST}:${LOCAL_PORT}:${REMOTE_HOST}:${REMOTE_PORT} ${LOGIN_HOST} # EOF The exec is all one line. I have tried removing -f from the switches but this makes no difference. Whenever I start this job it immediately fails with the following in the syslog: . . . May 30 16:47:06 inet08 init: LOCAL_ssh_imap_proxy main process ended, respawning May 30 16:47:06 inet08 init: LOCAL_ssh_imap_proxy main process (3393) terminated with status 255 May 30 16:47:06 inet08 init: LOCAL_ssh_imap_proxy main process ended, respawning May 30 16:47:06 inet08 init: LOCAL_ssh_imap_proxy main process (3397) terminated with status 255 May 30 16:47:06 inet08 init: LOCAL_ssh_imap_proxy respawning too fast, stopped Is what I am doing wrong obvious to anyone? -- *** 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

Re: [CentOS] Upgrading FC2 to CentOS 5.* - anyone second this?
by Les Mikesell 30 May '12

30 May '12

On Wed, May 30, 2012 at 1:51 PM, Reindl Harald <h.reindl(a)thelounge.net> wrote: > > Am 30.05.2012 20:36, schrieb Les Mikesell: >> Fedora doesn't support/recommend in-place upgrades across major >> versions or at least didn't for those versions. My experience was >> that even within a major rev. an update could kill your system. > > then you are doing something wrong Yes, I was running it on an IBM server box that they didn't bother to test. Found out much later that the pre-update kernel worked on the firmware I had installed and the mid-rev update they pushed needed a firmware bios update to run there. > am i really the only one who did some hundret successfull > fedora dist-upgrades in the last 4 years with yum and > no downtime longer than a normal kernel update? Probably. Lots of other things broke in same-major-rev updates until I gave up at FC6. Whether any particular machine runs or not has never been a priority for fedora. Maybe your hardware matches one of the developers. On the other hand, I had 2 4-year uptime runs with a pre-fedora RH 7.3. (had to move it once). For about 6 of those years it was very busy. -- Les Mikesell lesmikesell(a)gmail.com

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