similar to: CESA-2015:1623 Important CentOS 6 kernel Security Update

Send CentOS-announce mailing list submissions to centos-announce at 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 at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

On Sunday, I did a "yum update" which installed kernel 2.6.32-573.3.1.el6.i686 on half a dozen virtual machines running CentOS 6.7. Since then, two of them have gone into "meltdown", and started spewing "ABRT Daemon" emails: one on Tuesday, and one tonight. The machines have a very light workload -- one runs "trac", and a handful of development systems,

After the upgrade, I was encountering a "network unreachable" error. This happens on kernel versions -> 2.6.32-573.1 .1-el6.x86_64 and 2.6.32-573.3.1-el6.x86_64. If I revert back to 2.6.32.504.30.3.el6.x86_64, the problem goes away. I've been searching frantically without much luck. I have found references to the same error on bugs.centos.org but no resolution as of yet. Has

Greetings, Today, I decided to reboot one of my CentOS machines after it had been running for 219 days. In this time, I had done yum updates several times. When I tried rebooting the machine, none of the kernels would work except for the oldest one. Here are the installed kernels: kernel-2.6.32-504.23.4.el6.x86_64 kernel-2.6.32-573.3.1.el6.x86_64 kernel-2.6.32-573.7.1.el6.x86_64

On Saturday 15 August 2015 06:59:36 Gilbert Sebenste wrote: > Hello everyone, > > I had a CentOS 6.5 CD for a clean install, and I did a desktop > install. Then I did a yum update to bring it up to 6.7. So far, so > good. > > I run a bunch of scientific programs that use C++ compilers and > libraries. But, the programs were failing becaause in /usr/lib, > the

Can you provide a bit more detail? What hardware are you using, what network driver is in use, etc.. On 09/03/2015 02:52 PM, John Tebbe wrote: > After the upgrade, I was encountering a "network unreachable" error. > This happens on kernel versions -> 2.6.32-573.1 .1-el6.x86_64 and > 2.6.32-573.3.1-el6.x86_64. If I revert back to > 2.6.32.504.30.3.el6.x86_64, the problem

Hello, >>> after an update from 6.6 to 6.7 the following error message is logged to >>> /var/log/messages when I login (per ssh): >>> >>> Aug 11 16:31:21 a1234 automount[1598]: set_tsd_user_vars: failed to get >>> passwd info from getpwuid_r Did some more tests: Compiled autofs with logging of UID/GID in autofs-function "set_tsd_user_vars".

On Feb 3, 2016, at 12:24 PM, Max Pyziur <pyz at brama.com> wrote: > > When I tried rebooting the machine, none of the kernels would work except for the oldest one. Define ?would not work?. Post a photo of the error message somewhere if you can?t describe it better than that. You might have to turn off rhgb mode to get a useful error message. > Here are the installed kernels:

On Wed, 3 Feb 2016, Warren Young wrote: > On Feb 3, 2016, at 12:24 PM, Max Pyziur <pyz at brama.com> wrote: >> >> When I tried rebooting the machine, none of the kernels would work except for the oldest one. > > Define ?would not work?. Post a photo of the error message somewhere if you can?t describe it better than that. You might have to turn off rhgb mode to get a

Dear all, On a new server (postfix dovecot postfixadmin Centos) I did define quota=0 in postfixadmin However suddenly a user with more than 9Gb of mail got his mailbox new/cur empty and maillog shows: Sep 3 15:43:56 mail16 dovecot: lda(brouwerb at scholarium.nl): Error: sieve: msgid=<alpine.LRH.2.20.1509031543050.16381 at streaming2.antenna.nl>: failed to store into mailbox

Sorry, forgot to mention: version 2.0.9 (dovecot.x86_64 1:2.0.9-19.el6.1) On Thu, 3 Sep 2015, Support Antenna wrote: > Dear all, > > On a new server (postfix dovecot postfixadmin Centos) > I did define quota=0 in postfixadmin > > However suddenly a user with more than 9Gb of mail got his mailbox new/cur > empty and maillog shows: > > Sep 3

Full_Name: Felix Hernandez-Campos Version: R-1.5.0 OS: IRIX, FreeBSD, Solaris Submission from: (NULL) (208.30.174.32) [R-1.5.0] The installation of the package cluster fails in FreeBSD (4.2) and IRIX (6.5) (but it works fine for Solaris). In FreeBSD, the installation hangs right after f77 -fPIC -g -O2 -c clara.f -o clara.o (the first FORTRAN compile). In IRIX, the program also hangs at

Hello listmates, I have encountered a rather peculiar situation. We have a Centos 6 VM (64 bit) running on a VMware vSphere 5.5 server. It was running just fine until one day I decided to reboot it and it just would not boot up. Effectively, dracut failed to initialize the LVM, much like under the scenario described here:

On Mon, Aug 17, 2015 at 8:39 AM, Phelps, Matthew <mphelps at cfa.harvard.edu> wrote: > > > On Tue, Aug 11, 2015 at 10:55 AM, Ralf Aum?ller < > Ralf.Aumueller at informatik.uni-stuttgart.de> wrote: > >> Hello, >> >> after an update from 6.6 to 6.7 the following error message is logged to >> /var/log/messages when I login (per ssh): >>

Hello everyone, I had a CentOS 6.5 CD for a clean install, and I did a desktop install. Then I did a yum update to bring it up to 6.7. So far, so good. I run a bunch of scientific programs that use C++ compilers and libraries. But, the programs were failing becaause in /usr/lib, the libraries simply weren't there. The directory was fairly sparsely populated with about 10 directories of