Discuss

discuss@lists.centos.org

34753 discussions

failure to import ldif into ldap
by Tim Dunphy 04 Nov '10

04 Nov '10

Thanks all.. I have read the man of ldif.... your advice has gotten me quite far both in my current implementation and in my overall understanding of LDAP which I am hoping grows with each passing day. In my attempt to build my current directory, I have taken a dump of my last successful implementation (which was created on FreeBSD 8.1) and substituted values for the dc=company and dc=com values with the correct ones for the current directory (attempting to implement under CentOS 5.4) and even tho the correct schemas are in place it is choking on this entry: # defaults, sudoers, Services, acadaca.com dn: cn=defaults,ou=sudoers,ou=Services,dc=acadaca,dc=net objectClass: top objectClass: sudoRole cn: defaults description: Default sudoOption's go here And again I should have all the schemas in place to make this work... include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/nis.schema include /etc/openldap/schema/misc.schema inlcude /etc/openldap/schema/sudoers.schema include /etc/openldap/schema/openldap.schema [root@ldap ldif]# ldapadd -h ldap -a -w secret -x -D "cn=Manager,dc=acadaca,dc=net" -f /home/tim/txt/ldif/acadaca-master.ldif adding new entry "cn=defaults,ou=sudoers,ou=Services,dc=acadaca,dc=net" ldapadd: Invalid syntax (21) additional info: objectClass: value #1 invalid per syntax Why this ldif will work in one directory but not another is a mystery at this point.. thanks again -- Here's my RSA Public key: gpg --keyserver pgp.mit.edu --recv-keys 5A4873A9 Share and enjoy!!

1 0

Copying root partition
by Timothy Murphy 04 Nov '10

04 Nov '10

I recently transferred the / partition on my CentOS server from a small disk to a large disk, using "rsync -auvz". This works fine, except that I get dozens of selinux warnings when I re-boot. I'm running selinux in permissive mode. Is there any way to make sure that all the files in a partition are kosher as far as selinux is concerned? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

5 4

Web statistics - w3perl
by Jussi Hirvi 04 Nov '10

04 Nov '10

I am considering a richer alternative to good old Webalizer, in a webhotel (multidomain) setting. Any experience with w3perl? The demo at least looks impressive. http://www.w3perl.com - Jussi -- Jussi Hirvi * Green Spot Topeliuksenkatu 15 C * 00250 Helsinki * Finland Tel. +358 9 493 981 * Mobile +358 40 771 2098 (only sms) jussi.hirvi(a)greenspot.fi * http://www.greenspot.fi

5 5

Re: [CentOS] PATA Hard Drive woes
by Lamar Owen 04 Nov '10

04 Nov '10

>From: Keith Roberts <keith(a)karsites.net> >On Wed, 3 Nov 2010, Lamar Owen wrote: >> Might want to check the power supply as well. Bad/flakey >> power can indeed case damage to the drive surface; been >> there, done that, have two Maxtor 250GB drives with >> scribbled servo data to prove it. >OK. > I'm running the server from an APC UPS Back-UPS 650, so > there should not be any glitches in the power supply, should > there? Probably not on the AC side, although the Back-UPS 650 isn't a full online UPS but a switching standby UPS (full online, like the APC Symmetra 16KVA units I have here) rectify to DC, float the batteries at all times, and run the output from inverter all of the time (unless they're switched to bypass). The SmartUPS 1400RM I had in front of the PC that suffered the glitchy power is, unless I'm mistaken, also a full online pure sinewave UPS like the Symmetra, and is still in service (I checked its output on my oscilloscope first, though). No, I was referring to the output DC voltages (+12V, +5V, +3.3V,-5V, and -12V) from the power supply inside the system. In addition to my own personal RAID1 of 250GB drives, I also, a different time, lost a RAID5 array of 15K 36GB SCSI drives in a Dell 1600SC server; testing the power supply showed lots of noise and complete dropouts of a few milliseconds duration on the drive connectors' 5V supply pins. Completely and thoroughly scrambled the servo data on the Hitachi drives. Meaning they didn't just start showing bad sectors; they started getting seek errors. The 5V line on the drive connectors was reading an AC RMS of 4V superimposed on the +5V, yielding an effective DC voltage of 4V. Happened over a period of three weeks, during which time I had a number of mysterious failures (the Hitachi drives were error-correcting so well that by the time they started reporting errors, it was way past too late, and it became impossible for the Hitachi drives to even power up). I found that the power supply in question, upon investigation, provided the motherboard (where the DC power sensors on that box are) with clean 5V, and the drives were powered from a separate 5V rail, meaning the Dell management system wasn't seeing the power problems. A simple power supply tester with a built-in meter can be bought for less than $20; a more thorough power analyzer will run more than that. But even the simple one caught the failing Dell 1600SC supply. It took an oscilloscope to test the Antec in my personal box; turned out it was a cold solder joint in the Antec. A new power supply is less expensive than the equivalent labor it took to fix the Antec. I keep a known good 500W ATX 12V server-grade (8 pin 12V plug with adapters, and 24-pin ATX plug with 20-pin adapter) around for testing; that's one of the very first things I check when a PC is brought in that is flaky. (The very first thing is the dust accumulation, and the second thing is the heatsink compound). One of the first things I do on any CentOS system I put together is install lm_sensors and gkrellm (gkrellm from a third-party repo). I then enable all the motherboard sensors that are available in the gkrellm plugins, and run it (either local GUI or through ssh X forwarding to my central monitoring PC). On supermicro boards I install SuperODoctor for Linux, available on the supermicro site. The GUI runs well (there are some odd dependencies, however) and will e-mail you on alarm conditions that you can set. These include fan RPM, temperatures, and voltages. The CLI program isn't quite so sophisticated, but it can be run periodically and the result sent by e-mail for health checks. Drives that are having trouble will show up with high iowaits; run iostat (from the sysstat package) and look at the await result. Long awaits mean the drive is having trouble (or it has firmware issues like WD's EARS and EADS drives have in RAID configurations).

1 0

kernel bug fixed in later kernels
by Philip Manuel 04 Nov '10

04 Nov '10

Does anyone know if this is going to be fixed in CentOS ? // test case code below // expected behaviour is "all good" and a return code of zero. // this works on 2.6.35-1 // does not work on 2.6.18-194.17.4.el5 from Centos 5.5 // think this bug was fixed in git commit 8948e11f450e6189a79e47d6051c3d5a0b98e3f3 // around 2.6.22 // http://www.mail-archive.com/git-commits-head@vger.kernel.org/msg11654.html #include <fcntl.h> #include <stdio.h> #include <sys/stat.h> #include <sys/types.h> #include <unistd.h> int main(int argc, char** argv) { int fd = open("foo", O_RDONLY); if (setuid(1000)) { printf("could not setuid, run as root with correct uid\n"); return 1; } char proc_name[1024]; sprintf(proc_name, "/proc/self/fd/%d", fd); struct stat stat_buf; int rc = stat(proc_name, &stat_buf); if (rc == 0) { printf("all good\n"); } else { printf("busted, could not access %s\n", proc_name); } return rc; }

2 2

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

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