similar to: Exploit

I have a VPS running C7. I ran a 'yum update' which included a kernel update. The yum update wasn't a total success because mariadb updates failed. However everything else appeared to work. However, when I rebooted the server it did not restart. I have managed to get the ISP's support desk to boot the server by selecting the previous kernel, and I now have access to my box again.

CentOS Errata and Security Advisory 2019:2586 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:2586 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: e26407ebb5fcabf2648e2036852c569b4b86d01d926d4227e1aad1547025690a ghostscript-9.25-2.el7_7.2.i686.rpm

CentOS Errata and Security Advisory 2019:3888 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:3888 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 7c6fcd05c85f65ecb5d0bf35a474228907d6338d5a536a4e7672a02fa933c78e ghostscript-9.25-2.el7_7.3.i686.rpm

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:

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