Re: [CentOS] connection refused resolving - after 5.4 upgrade

2009-11-02 Thread Jens Ahlin
Hi,

We see the same thing. Massive amounts of entries in Logwatch report.

Is logging lame servers to /dev/null the answer here ?

  Jens

 Hi all,
 prior to 5.4 upgrade, my two DNS servers would only get
 'connection refused resolving .'
 on rare infrequent occasions (once or twice a month)
 after upgrade to 5.4 I get 500+ per day.
 Google has suggestions for
 |logging
category lame-servers null; ;
 ;

 |however this strikes me as severe overkill as it will mask genuine
 problems.
 Anyone else noticed this?
 Suggestions as to why or what is causing?
 Thanks
 Rob

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] update 5.4 problem using yum

2009-10-23 Thread Jens Ahlin
Hi,

I have tried to update one of my servers to 5.4. I read the release notes
and ran yum clean all followed by yum update glibc\* without any problem,
I then ran yum update glibc\* which failed.

Resolving Dependencies
-- Running transaction check
--- Package python-devel.i386 0:2.4.3-27.el5 set to be updated
--- Package rpm-libs.i386 0:4.4.2.3-18.el5 set to be updated
-- Processing Dependency: popt = 1.10.2.3-18.el5 for package: rpm-libs
--- Package python.i386 0:2.4.3-27.el5 set to be updated
--- Package yum-metadata-parser.i386 0:1.1.2-3.el5.centos set to be updated
--- Package rpm-python.i386 0:4.4.2.3-18.el5 set to be updated
--- Package rpm-devel.i386 0:4.4.2.3-18.el5 set to be updated
--- Package yum.noarch 0:3.2.22-20.el5.centos set to be updated
--- Package rpm.i386 0:4.4.2.3-18.el5 set to be updated
--- Package rpm-build.i386 0:4.4.2.3-18.el5 set to be updated
-- Running transaction check
--- Package popt.i386 0:1.10.2.3-18.el5 set to be updated
*** glibc detected *** /usr/bin/python: free(): invalid pointer:
0x0a98d660 ***
*** glibc detected *** /usr/bin/python: double free or corruption (out):
0x092e04c8 ***

Now I cannot run yum or rpm to restore the updated glibc packages. Any
idea's ? Did I miss something ?

  Jens
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos