Discuss October 2010

discuss@lists.centos.org

256 participants
226 discussions

LDAP authentication on a remote server (via ldaps://)
by Mathieu Baudier 07 Oct '10

07 Oct '10

Hello, I have a central repository of users/groups based on OpenLDAP which is working on a remote LAN (servers share users credentials and mount their home directories via NFS). They use non-encrypted ldap restricted to the local network. Now, I have a few servers in our local office and I would like them to authenticate from the remote LDAP server using encryption via ldaps://. (at this stage, without using client-side certificate) I have run a similar command as I did on the remote servers, replacing ldap://localldapserver by ldaps://ldap.mycompany.com: authconfig --enableldap --enableldapauth --enablecache --enablemkhomedir --ldapserver=ldaps://ldap.mycompany.com --enableldaptls --ldapbasedn=dc=mycompany,dc=com --passalgo=sha256 --updateall and I put the CA certificate at the right place. (either explicitly pointing to it TLS_CACERT or downloading it to /etc/openldap/cacerts vi system-configuration-authentication) In all my various tests, ldapsearch -x returns the content of the remote LDAP, so I guess that at least openldap clients are properly configured. But when I try: getent passwd the command hangs. Same when I try to: su - myuser (I also tried configuring with the system-configuration-authentication UI from a box with GNOME, and also tried authconfig without --enableldaptls) So is there anything specific to authentication ldaps: that I should have done? (as I said, this approach systematically works with plain ldap on this same LDAP server) Thanks in advance for your help! Mathieu Note: all systems involved are running up to date CentOS 5.5

4 6

Re: [CentOS] GDM could not write to you authorization file ... Please contact your system adminstrator
by Brent L. Bates 07 Oct '10

07 Oct '10

This error sounds familiar. If it is the same problem I've had a couple of times, every time it happens, I forget what it was I did the last time to fix it. :-( After I remember, it seems almost obvious. Assuming you've got the same problem, you need to log into the account remotely, with out a GUI interface, or as another user. See if you have a file ~/.ICEauthority. If it is there, delete it and then try logging in again. I think that is the right file for the problem I've had. I just remember that some file got corrupted and I had to delete it before GUI logins would work. I hope this helps. Good luck. -- Brent L. Bates (UNIX Sys. Admin.) M.S. 912 Phone:(757) 865-1400, x204 NASA Langley Research Center FAX:(757) 865-8177 Hampton, Virginia 23681-0001 Email: B.L.BATES(a)larc.nasa.gov http://www.vigyan.com/~blbates/

3 2

system "stuck" with 2.6.18-128 kernel. how to move to 2.6.18-194.17?
by Aleksey Tsalolikhin 06 Oct '10

06 Oct '10

Hi. I just noticed I had a CentOS 5.3 system that I updated to CentOS 5.5 a few days ago, and I just ran "yum -y update" again to get the latest kernel, and I just noticed it still has the old 2.6.18-128 kernel instead of the new 2.6.18-194.17. What gives? /etc/grub.conf points at 2.6.18-194.17, but when I reboot, 2.6.18-128 comes up. Any suggestions? Thanks, -at myserver# yum -y update ... myserver# reboot ..... myserver# uname -a Linux hwd-ddc-sonydb-prod 2.6.18-128.4.1.el5 #1 SMP Tue Aug 4 20:19:25 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux myserver# cat /etc/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/md1 # initrd /initrd-version.img #boot=/dev/md0 default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-194.17.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.17.1.el5 ro root=/dev/md1 initrd /initrd-2.6.18-194.17.1.el5.img title CentOS (2.6.18-194.11.4.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.11.4.el5 ro root=/dev/md1 initrd /initrd-2.6.18-194.11.4.el5.img title CentOS (2.6.18-128.4.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-128.4.1.el5 ro root=/dev/md1 initrd /initrd-2.6.18-128.4.1.el5.img myserver# rpm -q kernel kernel-2.6.18-128.4.1.el5 kernel-2.6.18-194.11.4.el5 kernel-2.6.18-194.17.1.el5 myserver#

7 8

kernel.org kernel in CentOS respin.
by Steve Clark 06 Oct '10

06 Oct '10

Hello List, I found these wonderful instruction by Alan Bartlett (thanks Alan) for building a kernel.org kernel that would install on CentOS 5.5. Doing this and moving the resulting .rpm to the target system and doing a rpm -ivh ... works great. Now I am trying to use the same rpm as part of a CentOS respin and the installation fails miserably leaving me with a unbootable system. Using the rescue option I see the following in my install log. Installing kernel-2.6.32.23-1.i386 /var/tmp/rpm-tmp.24949: line 1: uname: command not found /var/tmp/rpm-tmp.24949: line 1: uname: command not found /var/tmp/rpm-tmp.24949: line 1: [: too many arguments /var/tmp/rpm-tmp.24949: line 6: /sbin/new-kernel-pkg: No such file or directory error: %post(kernel-2.6.32.23-1.i386) scriptlet failed, exit status 127 Does someone have instructions for building a kernel.org kernel that will install like the standard CentOS kernels? Thanks, -- Stephen Clark NetWolves Sr. Software Engineer III Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark(a)netwolves.com www.netwolves.com

2 4

EXT4 mount issue
by Steve Brooks 06 Oct '10

06 Oct '10

Hi All, When a couple of EXT4 filesystems are mounted in a server I get the message Oct 1 18:49:42 sraid3 kernel: EXT4-fs (sdb): mounted filesystem without journal Oct 1 18:49:42 sraid3 kernel: EXT4-fs (sdc): mounted filesystem without journal in the system logs. My confusion is why are they mounted without a journal? They were both created with mkfs -t ext4 /dev/sdb mkfs -t ext4 /dev/sdc and mounted in "/etc/fstab" with /dev/sdb /sraid3 ext4 defaults 1 2 /dev/sdc /sraid4 ext4 defaults 1 2 both are 11T and so I would prefer as much stability as possible, io performance is not an issue on either device just integrity so I thought the journal would be default and necessary. Any thoughts would be much appreciated. Steve -- Dr Stephen Brooks http://www-solar.mcs.st-and.ac.uk/ Solar MHD Theory Group Tel :: 01334 463735 Fax :: 01334 463748 E-mail :: steveb(a)mcs.st-andrews.ac.uk --------------------------------------- Mathematical Institute North Haugh University of St. Andrews St Andrews, Fife KY16 9SS SCOTLAND ---------------------------------------

8 18

Colour laser printer
by Timothy Murphy 06 Oct '10

06 Oct '10

Anyone got a recommendation for a cheap (but good) colour laser printer that runs under CentOS-5.5 ? -- 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

9 9

OpenOffice or LibreOffice?
by Mark 06 Oct '10

06 Oct '10

Given that the Document Foundation has now split away from Oracle to continue the development of an independent office suite, do we have any idea which was CentOS and Red Hat are planning to go in this area - OpenOffice or LibreOffice? I know that LibreOffice is not production ready yet - they only have their first beta available, but it's just a matter of (likely a short) time before the split becomes a release. Thanks, Mark

6 6

GDM could not write to you authorization file ... Please contact your system adminstrator
by drew einhorn 06 Oct '10

06 Oct '10

I am the system administrator. I have a system that was built with a default install which resulted in everything in a single file system except for /boot wrote some scripts to split out: /home, /usr, /var, /opt, and /tmp to separate file systems/logical volumes it looks like it ought to work, There's plenty of space in all the filesystems and I can log via ssh and have write access in my home directory. Logging in via ssh did result in a new .Xauthority file being automatically created, but that did not help. Googleing around I saw a thread where the user was actually out of disk space, but before that was established somebody asked if /home was on a different filesystem from /, but what to do in that case never came up. Another google thread suggested looking in .xsession-errors, but I don't have one. I've found irrelevant ubuntu suggestions regarding ubuntu only packages. Still googleing -- Drew Einhorn "You can see a lot by just looking." -- Yogi Berra

2 2

CentOS-announce Digest, Vol 68, Issue 2
by centos-announce-request＠centos.org 05 Oct '10

05 Oct '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:0737 Important CentOS 5 x86_64 freetype Update (Karanbir Singh) 2. CESA-2010:0737 Important CentOS 5 i386 freetype Update (Karanbir Singh) 3. CEBA-2010:0728 CentOS 5 x86_64 device-mapper-multipath Update (Karanbir Singh) 4. CEBA-2010:0728 CentOS 5 i386 device-mapper-multipath Update (Karanbir Singh) 5. CESA-2010:0736 Important CentOS 3 i386 freetype - security update (Tru Huynh) 6. CESA-2010:0736 Important CentOS 3 x86_64 freetype - security update (Tru Huynh) 7. CESA-2010:0737 Important CentOS 4 i386 freetype - security update (Tru Huynh) 8. CESA-2010:0737 Important CentOS 4 x86_64 freetype - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Mon, 4 Oct 2010 20:11:54 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2010:0737 Important CentOS 5 x86_64 freetype Update To: centos-announce(a)centos.org Message-ID: <20101004201154.GA26585(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2010:0737 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2010-0737.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 5afa410c4f2974603ada97886e1ea5dd freetype-2.2.1-28.el5_5.i386.rpm d6c8f0a869ec4529e6cde8661a1c8356 freetype-2.2.1-28.el5_5.x86_64.rpm 4615f98627de96657c307ca4fbffc8c3 freetype-demos-2.2.1-28.el5_5.x86_64.rpm f8f4e754eeaeeda39093f82b86699930 freetype-devel-2.2.1-28.el5_5.i386.rpm 3485cd6fbf695c0c62e32e406dc3f33e freetype-devel-2.2.1-28.el5_5.x86_64.rpm Source: e8617dff266776ce4cbe429dbe742c27 freetype-2.2.1-28.el5_5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Mon, 4 Oct 2010 20:11:54 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CESA-2010:0737 Important CentOS 5 i386 freetype Update To: centos-announce(a)centos.org Message-ID: <20101004201154.GA26571(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2010:0737 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2010-0737.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: f74574c523f4fd9dbb493a64813aca87 freetype-2.2.1-28.el5_5.i386.rpm bc7dad9ba9e83cbc51a543c2eb4232ca freetype-demos-2.2.1-28.el5_5.i386.rpm b74f98b95c1915c92e01d91a131d251e freetype-devel-2.2.1-28.el5_5.i386.rpm Source: e8617dff266776ce4cbe429dbe742c27 freetype-2.2.1-28.el5_5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Mon, 4 Oct 2010 20:17:23 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEBA-2010:0728 CentOS 5 x86_64 device-mapper-multipath Update To: centos-announce(a)centos.org Message-ID: <20101004201723.GA27037(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2010:0728 Upstream details at : https://rhn.redhat.com/errata/RHBA-2010-0728.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 9d75907753ba5c8a9993bf970d26057a device-mapper-multipath-0.4.7-34.el5_5.6.x86_64.rpm 8d770d9150a26d3bf6f836688f9d71a7 kpartx-0.4.7-34.el5_5.6.x86_64.rpm Source: b2dbdd714f154621a0d48057b6768237 device-mapper-multipath-0.4.7-34.el5_5.6.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Mon, 4 Oct 2010 20:17:23 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEBA-2010:0728 CentOS 5 i386 device-mapper-multipath Update To: centos-announce(a)centos.org Message-ID: <20101004201723.GA27023(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2010:0728 Upstream details at : https://rhn.redhat.com/errata/RHBA-2010-0728.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 506dcc5cfd7d883281f4d7baca1df602 device-mapper-multipath-0.4.7-34.el5_5.6.i386.rpm 83d28d82788d72906e8b2890823e521b kpartx-0.4.7-34.el5_5.6.i386.rpm Source: b2dbdd714f154621a0d48057b6768237 device-mapper-multipath-0.4.7-34.el5_5.6.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 5 Date: Tue, 5 Oct 2010 17:49:55 +0200 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2010:0736 Important CentOS 3 i386 freetype - security update To: centos-announce(a)centos.org Message-ID: <20101005154955.GA23836(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2010:0736 freetype security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2010-0736.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/freetype-2.1.4-18.el3.i386.rpm updates/i386/RPMS/freetype-demos-2.1.4-18.el3.i386.rpm updates/i386/RPMS/freetype-devel-2.1.4-18.el3.i386.rpm updates/i386/RPMS/freetype-utils-2.1.4-18.el3.i386.rpm source: updates/SRPMS/freetype-2.1.4-18.el3.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update freetype Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

iptables failure at the last line
by Alexander Farber 05 Oct '10

05 Oct '10

Hello, can anybody please spot an error here? # sudo service iptables start Flushing firewall rules: [ OK ] Setting chains to policy ACCEPT: filter [ OK ] Unloading iptables modules: [ OK ] Applying iptables firewall rules: iptables-restore: line 20 failed [FAILED] And my /etc/sysconfig/iptables is (I'm trying to enable Samba, Apache, FMS dev. ed. and throttled SSH at 22 and 443): *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT ACCEPT [294:35064] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -s 194.247.190.0/24 -j DROP -A INPUT -p icmp -m icmp --icmp-type any -j ACCEPT -A INPUT -p tcp -m state --state NEW -m udp --dport 137 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m udp --dport 138 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 139 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m udp --dport 445 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 445 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 8080 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 1935 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 1111 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 443 --tcp-flags FIN,SYN,RST,ACK SYN -m limit --limit 1/min --limit-burst 2 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 22 --tcp-flags FIN,SYN,RST,ACK SYN -m limit --limit 1/min --limit-burst 2 -j ACCEPT COMMIT Any hints on how to debug those issues? The error message line points to the COMMIT. Thank you Alex

3 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss October 2010