similar to: CEBA-2019:0504 CentOS 7 util-linux BugFix Update

CentOS Errata and Bugfix Advisory 2019:3983 Upstream details at : https://access.redhat.com/errata/RHBA-2019:3983 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c63153d62d1a3c58f74ff17e8a567ebedd4266cf07e57df50bd12eb3d3174a9e libblkid-2.23.2-61.el7_7.1.i686.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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

I have managed to find out what happened in the yum update and it turns out it was a mess. It looks like the server ran out of memory in the middle and things then started to fail. Any advice on how to recover from this would be greatly appreciated The log below shows: [root at vps2 ~]# yum history info 22 Loaded plugins: fastestmirror, langpacks Repository mariadb is listed more than once in

> On 1/22/20 3:57 PM, Gary Stainburn wrote: >> I have managed to find out what happened in the yum update and it turns >> out it was a mess. It looks like the server ran out of memory in the >> middle and things then started to fail. Any advice on how to recover >> from this would be greatly appreciated >> >> The log below shows: >> >> [root at

On 1/22/20 3:57 PM, Gary Stainburn wrote: > I have managed to find out what happened in the yum update and it turns out it was a mess. It looks like the server ran out of memory in the middle and things then started to fail. Any advice on how to recover from this would be greatly appreciated > > The log below shows: > > [root at vps2 ~]# yum history info 22 > Loaded plugins: