Discuss

discuss@lists.centos.org

34758 discussions

centos-release 5.7 srpm where?
by me＠tdiehl.org 18 Sep '11

18 Sep '11

Hi, Is the centos-release srpm for 5.7 available anywhere. I have looked at several mirrors but no srpms are to be found. I realize everyone is busy but it would be nice to have at least the srpms that were specific to the centos project with the release. Regards, -- Tom me(a)tdiehl.org Spamtrap address me123(a)tdiehl.org

3 3

Re: [CentOS] CentOS 5.6 to 5.7 upgrade
by fred smith 18 Sep '11

18 Sep '11

On Thu, Sep 15, 2011 at 08:53:44AM +0200, Sorin Srbu wrote: > 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! Seconded! My update went very well. booted right back up an everthing seems to be working--except... for some reason it overwrote my sendmail.cf rather than dropping in a sendmail.cf.rpmnew as it has done in the past, so after several hours I noticed I wasn't getting any incoming email. after a little flailing this morning (not having yet had any caffeine) I realized I should look at that. copied my version in, bounced sendmail and off to the races! Fred -- ------------------------------------------------------------------------------- Under no circumstances will I ever purchase anything offered to me as the result of an unsolicited e-mail message. Nor will I forward chain letters, petitions, mass mailings, or virus warnings to large numbers of others. This is my contribution to the survival of the online community. --Roger Ebert, December, 1996 ----------------------------- The Boulder Pledge -----------------------------

4 3

Thank you!!
by Thomas Dukes 17 Sep '11

17 Sep '11

Just wanted to thank everyone for helping me get my new machine up and running. I thought I had bought a boat anchor. Not sure what's up with my DVD drive on my 5.7 machine but I will be phasing/retiring it out over the next few days. Again thanks for your help and most of all your patience. Eddie

1 0

Upgrade from 5.6 => 5.7
by Thomas Dukes 17 Sep '11

17 Sep '11

SUCCESS!! Everything working, even the 'roll your own' apps!! Thanks!!

14 60

OT : ARIN Apologies .....
by Always Learning 16 Sep '11

16 Sep '11

For those who use Centos and have problems with ARIN, here is today's apology from ARIN's Chief Engineer Andy Newton posted on ARIN-Tech. Follow-ups, if any, off-list please. Thank you. Paul -------------------------------------- All, We appreciate your patience and willingness to work with us through issues and questions that have arisen with regard to Reg-RWS, our RESTful provisioning and resource management interface. We recognize that our current documentation is deficient, and we are working to correct that problem. Poor or inadequate documentation can be frustrating, and for that we apologize. While the Reg-RWS documentation addresses specific method calls and payloads, there is no good reference to the broader ARIN business rules nor how they apply to the RESTful interface or any of the other ARIN systems. We are working to address this gap. Again, thank you for your patience and willingness to work through questions and issues. Andy Newton Chief Engineer, ARIN

1 0

Yum segmentation fault updating from 5.6 to 5.7
by Sebastiano Pilla 16 Sep '11

16 Sep '11

I'm trying to update my CentOS 5.6 boxes to 5.7, and on every single one of them yum is failing with a segmentation fault: the error happens when yum is checking the 'base' repository. [root@picard yum]# yum update Loaded plugins: downloadonly, fastestmirror, priorities Determining fastest mirrors * base: mirrors.ircam.fr * extras: mirrors.ircam.fr * updates: mirror.opendoc.net base | 1.1 kB 00:00 base/primary | 961 kB 00:00 Segmentation fault Running yum under strace produces lots of output, the last lines are: access("/var/cache/yum/base/primary.xml.gz.sqlite-journal", F_OK) = -1 ENOENT (No such file or directory) fstat64(5, {st_mode=S_IFREG|0644, st_size=20480, ...}) = 0 _llseek(5, 0, [0], SEEK_SET) = 0 read(5, "SQLite format 3\0\4\0\1\1\0@ \0\0\0\21\0\0\0\0"..., 1024) = 1024 _llseek(5, 2048, [2048], SEEK_SET) = 0 read(5, "\r\0\0\0\0\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1024) = 1024 fcntl64(5, F_SETLK64, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}, 0xbf86a1c4) = 0 futex(0x7ba0918, FUTEX_WAKE_PRIVATE, 2147483647) = 0 stat64("/var/cache/yum/base/primary.xml.gz", {st_mode=S_IFREG|0644, st_size=983757, ...}) = 0 stat64("/var/cache/yum/base/primary.xml.gz", {st_mode=S_IFREG|0644, st_size=983757, ...}) = 0 stat64("/var/cache/yum/base/primary.xml.gz", {st_mode=S_IFREG|0644, st_size=983757, ...}) = 0 open("/var/cache/yum/base/primary.xml.gz", O_RDONLY|O_LARGEFILE) = 6 _llseek(6, 0, [0], SEEK_CUR) = 0 read(6, "\37\213\10\10\0\0\0\0\2\377/home/buildcentos/CENT"..., 8192) = 8192 --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ It seems that the primary.xml.gz file is somehow corrupted, but I've already tried a "yum clean all" and a "rm -rf /var/cache/yum/*" without success. Apart from being at CentOS 5.6 and all having this problem, the boxes have very few in common: - 2 physical machine running 5.6 32-bit, one in my office, the other in a datacenter - 1 physical machine running 5.6 64-bit in another datacenter - 2 KVM VPS running 5.6 32-bit in a third datacenter - 1 Xen VPS running 5.6 64-bit in a fourth datacenter There was a thread on the forum some months ago which mentioned this same problem, but the original poster didn't find a solution (or if he did, he didn't share it with the forum). Any suggestion is appreciated, I cannot reinstall those boxes with 6.0 for at least 4/5 months.

15 49

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

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