Discuss September 2011

discuss@lists.centos.org

268 participants
252 discussions

CentOS 6.0 Heartbeat missing logd??
by Ken Dechick 16 Sep '11

16 Sep '11

Hello list, Working on migrating my existing High-Availability setups from CentOS 5.3 to 6.0, both x86_64. I generally setup a fairly simple 2 node active/passive cluster using DRBD , Heartbeat, and Pacemaker. Use these clusters to run our proprietary Medical software plus a few key services ( openvpn , Digi PortServer Daemon, etc.). I had a procedure in place for doing all of this under 5.3 and was hoping to basically duplicate the same thing on CentOS 6 as an early step in moving all the servers we build to EL6. I expected some hurdles along the way. New versions of the needed software, the new ext4 file system, my move from standard partitioning to LVM , ect . Biggest issue up till now was that the pacemaker package from CentOS base (pacemaker-1.1.2-7.el6.x86_64.rpm) was built with no support for Heartbeat , surprisingly. That was easy to fix with a quick source rpm rebuild, but now I have run into a new wall I am hoping someone can help me with. The latest Heartbeat package from EPEL (heartbeat-3.0.4-1.el6.x86_64.rpm) I thought would be the easy way to go for EL6 (was using v3.0.3 on EL5), but it appears to be missing the logd daemon that it is supposed to include. Heartbeat logd With Heartbeat v3.0.3 I had the daemon installed as expected as: /etc/ init .d/ logd . In CentOS 6, I installed the v3.0.4 from EPEL and there is no logd installed. Of course heartbeat is complaining that logd is not running, but giving me no more info. So I snagged the source rpm and dug around thinking maybe I had to rebuild that myself too, but I find no mention of logd is these sources anywhere. Surely I am not the first to try to run a Heartbeat/Pacemaker cluster in CentOS 6, am I?? Can anyone shed some light on this? Googled around most of the afternoon yesterday but found no answers, or even anyone else having the same issue. Moving to another messaging layer is not something I really want to consider here. We only build a dozen of so HA setups a year so I try to keep them as similar as possible to make supporting them easier on my team. I used to work directly with Linbit on issues like this but last year the higher-ups in my company decided I knew enough about this stuff already and we dropped our support contract with them, doh ! Any help would be much appreciated! Thank You Kenneth Dechick Linux Systems Administrator Community Computer Services, Inc. This message and any attachments may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by e-mail, and permanently delete this e-mail.

1 0

Re: [CentOS] CentOS 5.6 to 5.7 upgrade
by m.roth＠5-cent.us 16 Sep '11

16 Sep '11

Sorin Srbu wrote: >>-----Original Message----- >>From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On > Behalf >>Of m.roth(a)5-cent.us >>Sent: Thursday, September 15, 2011 4:04 PM >>To: CentOS mailing list >>Subject: Re: [CentOS] CentOS 5.6 to 5.7 upgrade >> >>For us, it's breaking an ssh-restrict script we use with rsync for >>backups, mangling some passed wildcards. > > Is this a homebrew backup solution? > > I use BackupPC, and so far I haven't seen any problems Yep. The ssh-restrict only allows certain accounts to issue only certain commands when coming in through ssh, sorta like sudoers, for another layer of security. That security is *required* by law: some data from some systems contains HIPAA and PII. mark

1 0

Dedup (again)
by Fajar Priyanto 16 Sep '11

16 Sep '11

Hi all, Back in March someone asked about deduplication in Centos and I replied I'm using LessFS. I want to report that my overall experience is that I have performance issue up to the point that I would like to abandon it. The OP was asking http://www.opendedup.org/ How is it? Thanks Fajar

4 5

Cons of disabling *.i386 and *.i686 in a 64bit Distribution
by James Nguyen 16 Sep '11

16 Sep '11

Can anybody give me a reason why this would be a bad idea. So the premise for this question is that I setup an exclude=*.i368,*.i686 in my yum.conf. While doing a yum update I come across missing package dependencies for instance mkinitrd for the i386 package. I noticed there is already one for x86_64. I realized during the kickstart install that some of these *.i386 got installed before I could enable the exclude in the yum.conf. So the questions I pose is... why are some of these *.i386 packages getting installed on a 64bit distro? is there any harm is removing them all? I guess I could spin up a virtual and try, but wanted to see what the census already knows about this matter as well. Thanks! -- james h nguyen | lead systems architect | www.callfire.com | 1.949.625.4263

7 9

trouble booting install CD on old machine
by Keith Keller 15 Sep '11

15 Sep '11

Hi all, I'm having a bit of an issue booting the full 5.7 install CD on an older machine. I downloaded the ISOs earlier today, checked the sha1sums, and burned the CDs with no reported errors. But when I try to boot, the isolinux banner comes up quickly, but then instead of the boot prompt, I get a completely blank screen. After 30-60 seconds, I get a message in purple, the exact wording I don't recall, but something like "can't boot, please restart". Many years ago I put CentOS 4 on this machine, so I know it can boot CD media, and earlier today I booted an older UBCD, so I know that it can successfully boot from CD at the present time. (I didn't have time to test the CD I burned in another box; I will do that next time I have the CD.) What other options do I have for getting 5.7 on this box? I have a few ideas: --do some troubleshooting with the 5.7 CD. I don't really know how to go about this, and there's no guarantee it'll end up with being able to boot in the end. --perhaps an older CentOS 5 ISO will work better? Testing this will be fairly quick but is not sure to work. --remove the system disk, put it into another system that is known to boot the 5.7 CD, install there, then put the disk back. This could be somewhat time consuming (the machine is in a rack, and the system drive is buried in the chassis, not hot-swappable), but is pretty sure to work. --try to boot from USB. As I said, it's an old box, so I'm not sure it supports booting over USB media. There were no "boot from USB" options in the BIOS; I could try to flash the firmware, but that seems excessive for this sort of issue. Other thoughts/suggestions? Any ideas why I'd be seeing this particular boot behavior? It's not something I've seen before; either booting fails before even reaching isolinux, or the kernel panics on finding some exotic and/or broken piece of hardware. --keith -- kkeller(a)wombat.san-francisco.ca.us

3 4

Re: [CentOS] [CentOS-announce] Release for CentOS-5.7 i386 and x86_64
by Always Learning 15 Sep '11

15 Sep '11

On Wed, 2011-09-14 at 00:33 +0100, Karanbir Singh wrote: > We are pleased to announce the immediate availability of CentOS-5.7 for > i386 and x86_64 Architectures. Thank you for all the hard dedicated work. -- With best regards, Paul. England, EU.

5 6

distro pkg update messages only email lists or website too?
by R - elists 15 Sep '11

15 Sep '11

greetings are distro pkg update messages only email lists or website too? i see that CentOS 5 kernel stuff is pushed 2x in past coupla days and just wanna make sure what differences are... or was it just a move from CR to mainline difference and upgrading same things again? - rh

1 0

Error in updating to 5.7
by Alain Péan 15 Sep '11

15 Sep '11

Hi all, I have a Dell server, CentOS 5.6 64 bits, on which I configured the CR repository. I just tried to update to 5.7, and had this error : # yum update .... http://mirror.centos.org/centos/5/cr/x86_64/repodata/filelists.sqlite.bz2: [Errno 14] HTTP Error 404: Not Found Trying other mirror. Error: failure: repodata/filelists.sqlite.bz2 from cr: [Errno 256] No more mirrors to try. You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest The program package-cleanup is found in the yum-utils package. My repolist is this one : # yum repolist Loaded plugins: dellsysid, fastestmirror, refresh-updatesd Loading mirror speeds from cached hostfile * addons: distrib-coffee.ipsl.jussieu.fr * base: distrib-coffee.ipsl.jussieu.fr * epel: fr2.rpmfind.net * extras: centos.crazyfrogs.org * updates: centos.crazyfrogs.org repo id repo name status addons CentOS-5 - Addons enabled: 0 base CentOS-5 - Base enabled: 3535 cr CentOS-5 - CR enabled: 573 dell-omsa-indep Dell OMSA repository - Hardware independent enabled: 719 dell-omsa-specific Dell OMSA repository - Hardware specific enabled: 2 epel Extra Packages for Enterprise Linux 5 - x86_64 enabled: 6700 extras CentOS-5 - Extras enabled: 233 updates CentOS-5 - Updates enabled: 150 repolist: 11912 Other information : # cat /etc/redhat-release CentOS release 5.6 (Final) # uname -a Linux xxxxxxx 2.6.18-274.el5 #1 SMP Fri Jul 22 04:43:29 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux Does anybody has an idea why I have this error ? Thanks for the help. -- ========================================================== Alain Péan - LPP/CNRS Administrateur Système/Réseau Laboratoire de Physique des Plasmas - UMR 7648 Observatoire de Saint-Maur 4, av de Neptune, Bat. A 94100 Saint-Maur des Fossés Tel : 01-45-11-42-39 - Fax : 01-48-89-44-33 ==========================================================

5 6

CentOS 5.6 to 5.7 upgrade
by Sorin Srbu 15 Sep '11

15 Sep '11

Hi all, Almost wish I had something more exciting to say regarding the 5.6 to 5.7 upgrade, but it just worked flawlessly. Physical as well as virtual machines. Thanks CentOS-team for your good work! -- BW, Sorin ----------------------------------------------------------- # Sorin Srbu [Sysadmin, Systems Engineer] # Dept of Medicinal Chemistry, Phone: +46 (0)18-4714482 >3 rings> GSM # Div of Org Pharm Chem, Mobile: +46 (0)701-718023 # Box 574, Uppsala University, Fax: +46 (0)18-4714482 # SE-751 23 Uppsala, Sweden Visit: BMC, Husargatan 3, D5:512b # Web: http://www.orgfarm.uu.se ----------------------------------------------------------- # () ASCII ribbon campaign - Against html E-mail # /\ http://www.asciiribbon.org # # This message was not sent from an iProduct! # # MotD follows: # "God, root, what is difference?" -Pitr from http://www.userfriendly.org/cartoons/pitr/

1 0

Yum update to 5.7 unexpected results
by b.j. mcclure 14 Sep '11

14 Sep '11

I have a couple machines running 5.6 fully updated from cr repo. When I did 'yum update' this morning it found 8 updates: centos-release-5-7.el5 centos-release-notes-5.7-0 ghostscript 8.70-6.el5_7.3 nspr 4.8.8-1.el5_7 nss 3.12.10-4.el5 nss-tools 3.12.10-4.el5 ntp-4.2.2p1-15.el5 initscripts-8.45.38-2.el5 However yum reported 404 on everything but ntp and initscripts. I installed ntp and initscripts individually and yum continued to report 404 on the rest of the updates on both machines. One machine i386, the other x86_64. I did a 'yum clean all' followed by 'yum update' and it installed centos-release and centos-release-notes but not nss, nss-tools, ghostscript or nspr updates. []# cat /etc/redhat-release CentOS release 5.7 (Final) []# rpm -q nss nss-tools ghostscript nspr nss-3.12.8-4.el5_6 nss-tools-3.12.8-4.el5_6 ghostscript-8.70-6.el5 nspr-4.8.6-1.el5_5 Both machines had identical results and appear to be fully updated to 5.7 but with at least four packages not updated. I don't think this is an intended result. Any thoughts much appreciated. B.J. CentOS Linux release 6.0 (Final)

2 2

← Newer
1
...
10
11
12
13
14
15
16
...
26
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss September 2011