Discuss

discuss@lists.centos.org

34753 discussions

CentOS-announce Digest, Vol 96, Issue 11
by centos-announce-request＠centos.org 27 Feb '13

27 Feb '13

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. CEBA-2013:0558 CentOS 5 rpm Update (Johnny Hughes) 2. CEBA-2013:0559 CentOS 5 rgmanager Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 26 Feb 2013 16:05:54 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2013:0558 CentOS 5 rpm Update To: centos-announce(a)centos.org Message-ID: <20130226160554.GA16464(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2013:0558 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0558.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e1b9f740f247c2d2d5f12d994dfa20e060dd9cb4ecaf3f49a7178e3d269b1e5e popt-1.10.2.3-32.el5_9.i386.rpm 4754bbb37ef0cbbf93713f2c36db85bfd17b6ef4f20d592a2a326247c83b019e rpm-4.4.2.3-32.el5_9.i386.rpm 709aae2dcecd69d9f618ff2df6b2287a66ad19f70b49e71d6466b2728677f4f3 rpm-apidocs-4.4.2.3-32.el5_9.i386.rpm 0bf2abc1f4a4f8a5cd8c1b9640ae0dbc93ab494ca4871f74a1a6f92ad25004f1 rpm-build-4.4.2.3-32.el5_9.i386.rpm 7ca0a6635cc98a70b68f3d219634f7058d510fa94f0ff10094cf66a5a5133068 rpm-devel-4.4.2.3-32.el5_9.i386.rpm 639b54e492116f6ae6f5ad5d68b6369e0af9115ca19a4b7552cbd28af6abe0e9 rpm-libs-4.4.2.3-32.el5_9.i386.rpm 5311dcd963e3e5a886b667c8aaace683cb7d28cb74007e055c1af0920a6d2c7d rpm-python-4.4.2.3-32.el5_9.i386.rpm x86_64: e1b9f740f247c2d2d5f12d994dfa20e060dd9cb4ecaf3f49a7178e3d269b1e5e popt-1.10.2.3-32.el5_9.i386.rpm 2b80a4055de8dac4be3000e6e04c5413c975c30feeae12057a149944e93c571c popt-1.10.2.3-32.el5_9.x86_64.rpm b709444ee4c7009046de6d64616bc2769c7b9aa2b88018e2ac982c5bd8fe869c rpm-4.4.2.3-32.el5_9.x86_64.rpm 66e2627515c37e20400d202d5bff7eeee54737871ec0689d9c3cacfac88dbd25 rpm-apidocs-4.4.2.3-32.el5_9.x86_64.rpm df76ed1cb1d24996aecf644861f1f0ba7a309fc5ccdaaebf7f28cfb05fe52d53 rpm-build-4.4.2.3-32.el5_9.x86_64.rpm 7ca0a6635cc98a70b68f3d219634f7058d510fa94f0ff10094cf66a5a5133068 rpm-devel-4.4.2.3-32.el5_9.i386.rpm 990430a8952296ac879c0230071e0d3fbceab301265308ba10dd3af5d604a06e rpm-devel-4.4.2.3-32.el5_9.x86_64.rpm 639b54e492116f6ae6f5ad5d68b6369e0af9115ca19a4b7552cbd28af6abe0e9 rpm-libs-4.4.2.3-32.el5_9.i386.rpm 78d97ed81dd2bfb324611dc8b57ced8e74fbac94ba54e8b76a5db904939e3be3 rpm-libs-4.4.2.3-32.el5_9.x86_64.rpm 9a4ff6fd6ee5af2fe19a4a2ef59c8bf7e5e8af5576060c1f6134cf130e7d380e rpm-python-4.4.2.3-32.el5_9.x86_64.rpm Source: 042c0e851da369e1557facc1b87ecfeb6bd2b4a22dc9d767b7eedd44366428e5 rpm-4.4.2.3-32.el5_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Tue, 26 Feb 2013 16:28:33 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2013:0559 CentOS 5 rgmanager Update To: centos-announce(a)centos.org Message-ID: <20130226162833.GA16682(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2013:0559 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0559.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 10d6ad046b53a8e55920ddb5ea4c34f09e9405250143d716021da5004b22a856 rgmanager-2.0.52-37.el5.centos.1.i386.rpm x86_64: cf91e9ffdc1ab8ae24a7dfba2216ccce1be18f478f472a413999aade839cec47 rgmanager-2.0.52-37.el5.centos.1.x86_64.rpm Source: 09f520aaea478ed93c8845aceb98b3b8f3432c5a96e5fc80cbb27faecb6f7e80 rgmanager-2.0.52-37.el5.centos.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 96, Issue 11 ***********************************************

1 0

HP download.linux.hp.com not available for rsync?
by Rafał Radecki 27 Feb '13

27 Feb '13

Hi All. TCP port 873 (rsync) is closed on download.linux.hp.com for ~24 hours. Does anyone know why? A quick look in google has not helped to find the answer. Best regards, Rafal.

2 2

Did anybody do a dovecot update on centos 5.x?
by Götz Reinicke - IT Koordinator 27 Feb '13

27 Feb '13

Hi, dose anybody did a dovecot update from the original 1.0.7 to e.g. 1.1 or 1.2 from atrpms repository? We dont have any special settings; Each user one mbox mailbox. About 500 imap/pop3 accounts, 400GB data. Any suggestions and comments are welcome. Regards . G. Reinicke -- Götz Reinicke - IT-Koordinator - Filmakademie Baden-Württemberg GmbH

4 5

Centos 6 apache mod_wsgi warning
by Robert Moskowitz 26 Feb '13

26 Feb '13

On a system I just built and installed fresh from base and update I am getting warnings in httpd/error.log about mod_wsgi: Compiled for Python/2.6.2 mod_wsgi: Runtime using Python/2.6.6 Just a 'warning'. What to do?

1 0

SSHD rootkit in the wild/compromise for CentOS 5/6?
by Gilbert Sebenste 26 Feb '13

26 Feb '13

Hello everyone, I hope you are having a good day. However, I am concerned by this: https://isc.sans.edu/diary/SSHD+rootkit+in+the+wild/15229 Has anyone heard yet what the attack vector is, if 5.9 and 6.4 are affected, and if a patch is coming out? Thanks! Gilbert ******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************

10 13

Re: [CentOS] running yum update on remote servers
by James B. Byrne 26 Feb '13

26 Feb '13

On Mon, February 25, 2013 09:03, Dennis Jacobfeuerborn wrote: > On 02/25/2013 02:48 PM, Robert Moskowitz wrote: >> I have read a couple old threads here on updates for servers, and I >> am >> looking for some mechanics to getting the actual updates done. I >> don't >> want automatic updates; I want to control when and what gets >> updated. >> >> First I have to determine that a particular server needs updates. I >> suppose a daily script that would run "yum check-updates' and emails >> me >> the results could work, but then I would only want the email IF >> there >> was something to update, at my limited use of this option does not >> show >> anything to trigger a notify on changes. Does anyone know of a >> script >> that would do this? > In crontab: MAILTO=whomever@whatever MAILFROM=this_system@whatever JOBNAME="Check for updates and report if found" ; /usr/bin/yum check-update -q The -q suppresses output unless there is something to report. Cron handles the rest. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

disabling lame server logging
by Robert Moskowitz 26 Feb '13

26 Feb '13

Continuing to 'clean up' my new server by reviewing logged messages. Researching a common one: Feb 26 07:30:29 onlo named[19336]: error (unexpected RCODE SERVFAIL) resolving 'foo.com/MX/IN': 1.2.3.4#53 I get the drift that my server has been directed to a 'lame server' and logs that fact. Supposedly I am to lookup the SOA record and contact the admin to fix this. What I really want to do is stop all these messages as I suspect I will not be able to do anything to fix the problem. So far what I have found is to add to my global logging section: category lame-servers { null; }; Is there a finer scalpel? I believe there are other lame server failures? Like 'RCODE REFUSED' and 'RCODE 15' (these are the 3 I see in my messages)? Can I block logging by RCODE, so as new ones appear I can learn what they mean before /dev/null ing them?

1 1

IUS repositories
by Kaushal Shriyan 26 Feb '13

26 Feb '13

Hi, what does the word "Inline" mean in Inline with Upstream Stable as per http://iuscommunity.org/pages/FAQs.html#what-does-ius-stand-for? Regards, Kaushal

2 1

Nagios NRPE IPv6
by Tilman Schmidt 26 Feb '13

26 Feb '13

On my network management server I have Name : nagios-plugins-nrpe Arch : x86_64 Version : 2.13 Release : 1.el6 Size : 38 k Repo : installed From repo : epel To my dismay I noticed that this doesn't seem to support IPv6: [ts@bombur ~]$ host galadriel.example.com galadriel.example.com has IPv6 address 2001:db8:f004:8::32 [ts@bombur ~]$ /usr/lib64/nagios/plugins/check_nrpe -n -H galadriel.example.com Invalid host name 'galadriel.example.com' [ts@bombur ~]$ /usr/lib64/nagios/plugins/check_nrpe -n -H 2001:db8:f004:8::32 Invalid host name '2001:db8:f004:8::32' [ts@bombur ~]$ (With obvious sanitization.) What gives? -- Tilman Schmidt Phoenix Software GmbH Bonn, Germany

4 8

Re: [CentOS] running yum update on remote servers
by Tilman Schmidt 25 Feb '13

25 Feb '13

Am 25.02.2013 23:36, schrieb Reindl Harald: > > Am 25.02.2013 23:34, schrieb Tilman Schmidt: >> Am 25.02.2013 15:56, schrieb m.roth(a)5-cent.us: >>> Robert Moskowitz wrote: >> >>>> Then there is the actual update. I learned long ago NOT to run yum over >>>> an SSH connection, as WHEN that connection breaks in the middle of an >>>> update, you can have quite a problem to clean up. All I have done >>> >>> That sounds, to me, as though you have very serious communications issues >>> that need to be solved, and yesterday. We've used ssh here, and at my >>> previous two? three? contracts, for years, and almost *never* have an ssh >>> connection break. >> >> It does happen. SSH is not as forgiving to network glitches as one >> would wish sometimes. A firewall that drops idle or long-running >> TCP connections, a DSL link doing its daily PPPoE disconnect at an >> inopportune moment, a VPN tunnel dropping, a hole in UMTS coverage, >> have all killed a SSH connection for me one time or another > > and that is why "screen" was invented Well, not quite. IIRC screen is older than SSH and was actually invented to switch between multiple screens on a text mode terminal attached either via a modem or a null modem cable. But I agree that it comes in handy for this scenario, too. > everybody doing a yum-upgarde over WAN directly on SSH > instead use screen is a foll and should not maintain servers Sure. Whatever a "foll" is supposed to be ... :-) -- Tilman Schmidt Phoenix Software GmbH Bonn, Germany

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