Discuss

discuss@lists.centos.org

34758 discussions

CentOS-announce Digest, Vol 69, Issue 2
by centos-announce-request＠centos.org 03 Nov '10

03 Nov '10

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-2010:0817 Low CentOS 3 i386/x86_64 CentOS-3 - End Of Life (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Wed, 3 Nov 2010 11:56:09 +0100 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2010:0817 Low CentOS 3 i386/x86_64 CentOS-3 - End Of Life To: centos-announce(a)centos.org Message-ID: <20101103105609.GA32735(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2010:0817 End Of Life security update for CentOS 3: https://rhn.redhat.com/errata/RHSA-2010-0817.html As per the upstream vendors errata support policy, updates for CentOS-3 has ended on October 31th 2010. It is recommended that any system still running CentOS 3 should be upgraded to a more recent version of CentOS before this date to ensure continued security and bug fix support. see also http://wiki.centos.org/HowTos/EOLC3 Thank you to everyone who helped make this project possible. Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

2 1

SCSI/SAS error message by mpt2sas.ko
by Alexander Dalloz 03 Nov '10

03 Nov '10

Dear all, actually I installed CentOS 5.4 x86_64 on 11 new Dell R710 servers. It is required to use 5.4 to be covered by the NetApp Interoperability Matrix for use of Snapdrive. All systems spit out the error message mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:4637/_scsih_add_device()! at boot time. In dmesg the complete SCSI initialization logging appears as follows: SCSI subsystem initialized mpt2sas version 01.101.00.00 loaded scsi0 : Fusion MPT SAS Host GSI 22 sharing vector 0x5A and IRQ 22 ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 33 (level, low) -> IRQ 90 PCI: Setting latency timer of device 0000:03:00.0 to 64 mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (24544400 kB) mpt2sas0: PCI-MSI-X enabled: IRQ 98 mpt2sas0: iomem(0xdf2b0000), mapped(0xffffc20000040000), size(65536) mpt2sas0: ioport(0xfc00), size(256) mpt2sas0: sending diag reset !! [...] mpt2sas0: diag reset: SUCCESS mpt2sas0: Allocated physical memory: size(1125 kB) mpt2sas0: Current Controller Queue Depth(490), Max Controller Queue Depth(3439) mpt2sas0: Scatter Gather Elements per IO(128) mpt2sas0: LSISAS2008: FWVersion(02.15.63.00), ChipRevision(0x02), BiosVersion(07.01.09.00) mpt2sas0: Protocol=(Initiator,Target<6>mpt2sas0: Dell PERC H200 Integrated: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F1E) ), Capabilities=(Raid,TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) mpt2sas0: sending port enable !! mpt2sas0: host_add: handle(0x0001), sas_addr(0x5842b2b0194dce00), phys(8) mpt2sas0: failure at drivers/scsi/mpt2sas/mpt2sas_scsih.c:4637/_scsih_add_device()! mpt2sas0: port enable: SUCCESS Vendor: Dell Model: Virtual Disk Rev: 1028 Type: Direct-Access ANSI SCSI revision: 06 scsi 0:1:0:0: RAID1: handle(0x004f), wwid(0x04adb846d46d5f0a), pd_count(2), type(SSP) scsi 0:1:0:0: qdepth(128), tagged(1), simple(1), ordered(0), scsi_level(7), cmd_que(1) SCSI device sda: 285474816 512-byte hdwr sectors (146163 MB) sda: Write Protect is off sda: Mode Sense: 03 00 00 08 SCSI device sda: drive cache: write through SCSI device sda: 285474816 512-byte hdwr sectors (146163 MB) sda: Write Protect is off sda: Mode Sense: 03 00 00 08 SCSI device sda: drive cache: write through sda: sda1 sda2 sda3 sd 0:1:0:0: Attached scsi disk sda Vendor: FUJITSU Model: MBA3147RC Rev: D306 Type: Direct-Access ANSI SCSI revision: 05 scsi 0:0:0:0: SSP: handle(0x000a), sas_addr(0x500000e1150ca882), device_name(0x0000000000000000) scsi 0:0:0:0: SSP: enclosure_logical_id(0x5842b2b0194dce00), slot(1) scsi 0:0:0:0: qdepth(254), tagged(1), simple(1), ordered(0), scsi_level(6), cmd_que(1) Vendor: FUJITSU Model: MBA3147RC Rev: D306 Type: Direct-Access ANSI SCSI revision: 05 scsi 0:0:1:0: SSP: handle(0x000b), sas_addr(0x500000e1150ca9c2), device_name(0x0000000000000000) scsi 0:0:1:0: SSP: enclosure_logical_id(0x5842b2b0194dce00), slot(0) scsi 0:0:1:0: qdepth(254), tagged(1), simple(1), ordered(0), scsi_level(6), cmd_que(1) In the source code of the mpt2sas.ko module http://www.takatan.net/lxr/source/drivers/scsi/mpt2sas/mpt2sas_scsih.c?v=2.… the code part responsible for the error messages is 4633 /* check if this is end device */ 4634 device_info = le32_to_cpu(sas_device_pg0.DeviceInfo); 4635 if (!(_scsih_is_end_device(device_info))) { 4636 printk(MPT2SAS_ERR_FMT "failure at %s:%d/%s()!\n", 4637 ioc->name, __FILE__, __LINE__, __func__); 4638 return 0; 4639 } I am not sure what that should tell me. I can not detect any misfunction once the systems are up and running, nor any further error loggings. Any clue about the severity of that mpt2sas check and failure note? Best regards Alexander

1 1

Re: [CentOS] yum update
by Ritika Garg 03 Nov '10

03 Nov '10

Does the file /var/log/yum.log store the information of the last 7 days because I did some updates on 27October which are not there in the file.

3 2

cannon printer not printing
by Ritika Garg 03 Nov '10

03 Nov '10

Printer: Cannon MF4320d. I gave the command "lpr NNInteraction_Poster.pdf", then typed "lpq" which shows MF4320-4350_(UFRII_LT) is ready and printing Rank Owner Job File(s) Total Size active Ritika 636 NNInteraction_Poster.pdf 549888 bytes After a while "lpq" command returns: MF4320-4350_(UFRII_LT) is ready no entries But no printout is there. Is the driver missing? But then MF4320-4350_(UFRII_LT) will not come. What might be the problem?

1 0

Re: [CentOS] system logs out suddenly
by Ritika Garg 03 Nov '10

03 Nov '10

I updated libX11 and the problem is solved. Maybe the updated firefox and xulrunner are not compatible with the older version.

1 0

Building Samba RPM packages for RHEL/CentOS 5 - Needed corrections to the .spec file
by Miguel Medalha 03 Nov '10

03 Nov '10

I just built from source the Samba 3.5.6 RPM packages for CentOS 5.x/RHEL5.x. I found some glitches in the included samba.spec file and I thought someone else might benefit from my recent experience. The spec file for RHEL/CentOS resides, on the sources tree, under "samba-3.5.6\packaging\RHEL\". 1 - The process initially fails due to a dependency problem: missing "keyutils-devel". Change the respective entry on line 31 (BuildRequires:) to "keyutils-libs-devel" (yum install this file from the repositories if needed). 2 - Although it is called by the packaging process, the "umount.cifs" file is not compiled and therefore cannot be found in sources3/bin at the moment of packaging. Therefore, the RPM build process fails. Either comment the references to the file from lines 237, 396 and 414, if you don't need this function, or add the following to the ./configure command, starting on line 137: --with-cifsumount The default for this parameter is "no", and therefore it is not included in the "configure" process as is. 3 - The RPM build process finally fails because some files, which were compiled and copied to the temporary tree, are not called by the packaging process. The following lines must be included on the spec file, under "Files section": /usr/share/locale/de/LC_MESSAGES/net.mo %{_includedir}/wbc_async.h %{_mandir}/man5/pam_winbind.conf.5.gz I suggest you include them close to related lines (same paths) for the sake of clarity. After these corrections the build of the RPM packages went on with no errors and was successful. All the packages installed correctly afterward. I hope these tips will be useful to someone. PS - The sources for Samba 3.5.6 are here: http://www.samba.org/ Before building, you might be interested in patching the sources with the patch provided by Volker Lendecke to improve compliance with Windows ACLs. The patch is here, thanks to Volker: http://samba.org/~jra/samba-3-5-x-acl-jumbo-patch.tgz patch -b -p1 < jumbo-patch-3-5-6.diff After applying the patch and modifying the .spec file you can proceed to the building process. cd to "/usr/src/redhat/SOURCES/samba-3.5.6/packaging/RHEL" and execute the "makerpms.sh" script there.

1 0

projects.centos.org down again
by Glenn Eychaner 02 Nov '10

02 Nov '10

> Garry Dale wrote: >> There is an open bug report from 2009-09-21 with a similar summary [1]. >> Since bug 3858 was never closed, I've updated the notes. > > Per updates to bug tracker, the projects.centos.org site is back online. > > Should bug 3858 [1] now be closed, or is it acting as a placeholder for > events such as this? Just curious... Well, projects.centos.org was up briefly over the weekend, but appears (from my end) to be down again, same symptoms; HTTP connections just hang. Next time I'll download the LiveCD instructions I'm looking for to a static file! -G. -- Glenn Eychaner (geychaner(a)lco.cl) Telescope Systems Programmer, Las Campanas Observatory

1 0

CentOS-announce Digest, Vol 69, Issue 1
by centos-announce-request＠centos.org 02 Nov '10

02 Nov '10

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-2010:0812 Moderate CentOS 4 i386 thunderbird - security update (Tru Huynh) 2. CESA-2010:0812 Moderate CentOS 4 x86_64 thunderbird - security update (Tru Huynh) 3. CESA-2010:0811 Important CentOS 5 i386 cups Update (Tru Huynh) 4. CESA-2010:0811 Important CentOS 5 x86_64 cups Update (Tru Huynh) 5. CESA-2010:0812 Moderate CentOS 5 i386 thunderbird Update (Tru Huynh) 6. CESA-2010:0812 Moderate CentOS 5 x86_64 thunderbird Update (Tru Huynh) 7. CESA-2010:0819 Moderate CentOS 5 i386 pam Update (Tru Huynh) 8. CESA-2010:0819 Moderate CentOS 5 x86_64 pam Update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Mon, 1 Nov 2010 22:24:26 +0100 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2010:0812 Moderate CentOS 4 i386 thunderbird - security update To: centos-announce(a)centos.org Message-ID: <20101101212426.GA17456(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2010:0812 thunderbird security update for CentOS 4 i386: https://rhn.redhat.com/errata/RHSA-2010-0812.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/thunderbird-1.5.0.12-33.el4.centos.i386.rpm source: updates/SRPMS/thunderbird-1.5.0.12-33.el4.centos.src.rpm You may update your CentOS-4 i386 installations by running the command: yum update thunderbird Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

openldap fails to authenticate
by Tim Dunphy 02 Nov '10

02 Nov '10

I am attempting to setup an LDAP server under CentOS 5.4. However I am unable to search my ldap directory even tho I am supplying the proper credentials for the Manager account: [root@ldap openldap]# ldapsearch -x -h ldap -D 'cn=Manager,dc=example,dc=net' -W -b 'dc=example,dc=net' Enter LDAP Password: ldap_bind: Invalid credentials (49) Anonymous searches do work however: ldapsearch -x -h ldap -b "dc=example,dc=net" -s sub "objectclass=*" [root@ldap openldap]# ldapsearch -x -h ldap -b "dc=example,dc=net" -s sub "objectclass=*" # extended LDIF # # LDAPv3 # base <dc=example,dc=net> with scope subtree # filter: objectclass=* # requesting: ALL # # search result search: 2 result: 32 No such object I am currently attempting to use the actual word 'secret' to authenticate the Manager account: database bdb suffix "dc=example,dc=net" rootdn "cn=Manager,dc=example,dc=net" # Cleartext passwords, especially for the rootdn, should # be avoided. See slappasswd(8) and slapd.conf(5) for details. # Use of strong authentication encouraged. rootpw secret # rootpw {CRYPT}secret And I am getting error 49's in my openldap logs with loglevel set to 296 /var/log/openldap.log Nov 2 15:45:58 ldap slapd[3522]: slapd starting Nov 2 15:46:14 ldap slapd[3522]: conn=0 fd=11 ACCEPT from IP=127.0.0.1:44552 (IP=0.0.0.0:389) Nov 2 15:46:14 ldap slapd[3522]: conn=0 op=0 BIND dn="cn=Manager,dc=example,dc=net" method=128 Nov 2 15:46:14 ldap slapd[3522]: conn=0 op=0 RESULT tag=97 err=49 text= Nov 2 15:46:14 ldap slapd[3522]: conn=0 fd=11 closed (connection lost) this is how I have configured my ldap.conf BASE dc=example,dc=net HOST localhost URI ldap://ldap.example.net and for some reason slapd is listening on port 3774 even tho I haven't told it to: [root@ldap network-scripts]# netstat -tulnp | grep 389 tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 3774/slapd [root@ldap network-scripts]# netstat -tulnp | grep slapd tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 3774/slapd I haven't specified port 3774 _anywhere_ in my ldap config: [root@ldap network-scripts]# grep 3774 /etc/ldap thanks in advance for your help -- Here's my RSA Public key: gpg --keyserver pgp.mit.edu --recv-keys 5A4873A9 Share and enjoy!!

2 1

Best supported motherboard
by Basil Kurian 02 Nov '10

02 Nov '10

Which among these three motherboard is the best supported in Linux (Centos/Ubuntu) ? Intel® Desktop Board DH55HC [ http://ark.intel.com/Product.aspx?id=42409 ] Intel® Desktop Board DP55WG [ http://ark.intel.com/Product.aspx?id=40078 ] Intel® Desktop Board DP55KG [ http://www.intel.com/products/desktop/motherboards/DP55KG/DP55KG-overview.h…] Also which will be a good processor , for using in a desktop PC to run 4 or 5 Virtual machines concurrently on VirtualBox or VMWare ESX server ? Intel® Xeon® Processor X3460 [ http://ark.intel.com/Product.aspx?id=42931 ] or Intel® Core™ i7-870S [ http://ark.intel.com/Product.aspx?id=48498 ] -- Regards Basil Kurian http://basil.co.nr RSA Public key : gpg --keyserver pgp.mit.edu --recv-keys 41005549

3 3

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