Today when I ran yum update two packages came up microcode_ctl and unbound-libs. The updating process went fine until it outputted Running transaction Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 then it just froze. I could no longer ssh to the machine and the console was just blank. I had to shut down it hard. It came back up seemingly fine. But yum update doesn't work anymore. It says "Error importing repomd.xml from base/7/x86_64: Damaged repomd.xml file" I looked at the logs, but journalctl only shows the latest boot on this machine. So I guess I have three questions - Any idea what happened with the update process? - How can I repair repomd.xml? - How do I configure journalctl to store more boots? /Robin
Hello Robin, On Fri, 12 Jun 2020 09:20:34 +0200 Robin Lee <robinlee at mailbox.org> wrote:> Today when I ran yum update two packages came up microcode_ctl > and unbound-libs. The updating process went fine until it outputted > > Running transaction > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > then it just froze. I could no longer ssh to the machine and the > console was just blank. I had to shut down it hard. It came back up > seemingly fine. But yum update doesn't work anymore. It says "Error > importing repomd.xml from base/7/x86_64: Damaged repomd.xml file" > I looked at the logs, but journalctl only shows the latest boot on this > machine. > > So I guess I have three questions > - Any idea what happened with the update process?I got the exact same problem few updates of microcode_ctl away but the consequences where terribly different (system broken at fs level, low level package files zero'ed, had to reconstruct from manually downloaded packages). How lucky your are, your yum transaction was including very few changes otherwise it could have broken much more. Since then, I excluded it this package from my yum updates. I reported this issue to the list: Date: Wed, 25 Dec 2019 12:43:11 +0100 From: wwp <subscript at free.fr> Subject: [CentOS] CEEA-2019:4161 CentOS 7 microcode_ctl-2.1-53.7.el7_7.x86_64 update vs Dell Precision 7530> - How can I repair repomd.xml? > - How do I configure journalctl to store more boots?Sorry can't help there :-(. Regards, -- wwp https://useplaintext.email/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20200612/d27bb311/attachment.sig>
On Fri, Jun 12, 2020 at 09:20:34AM +0200, Robin Lee wrote:> Today when I ran yum update two packages came up microcode_ctl > and unbound-libs. The updating process went fine until it outputted > > Running transaction > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > then it just froze. I could no longer ssh to the machine and the > console was just blank. I had to shut down it hard.Maybe related to https://www.hivelocity.net/blog/centos-update-advisory/ (discarding the blame game) it might be a bad combination of kernel/microcode/bios... my 2 cents, Tru -- Tru Huynh http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20200612/bcc51682/attachment.sig>
On Fri, 2020-06-12 at 10:24 +0200, Tru Huynh wrote:> On Fri, Jun 12, 2020 at 09:20:34AM +0200, Robin Lee wrote: > > Today when I ran yum update two packages came up microcode_ctl > > and unbound-libs. The updating process went fine until it > > outputted > > > > Running transaction > > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > > > then it just froze. I could no longer ssh to the machine and the > > console was just blank. I had to shut down it hard. > > Maybe related to > https://www.hivelocity.net/blog/centos-update-advisory/ > (discarding the blame game) it might be a bad combination of > kernel/microcode/bios...Thanks for the link. Very interesting as I also have a Supermicro motherboard. My journalctl outputs: kernel: DMI: Supermicro Super Server/X11SSM-F, BIOS 2.2 05/23/2018 /Robin
On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote:> Today when I ran yum update two packages came up microcode_ctl > and unbound-libs. The updating process went fine until it outputted > > Running transaction > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > then it just froze. I could no longer ssh to the machine and the > console was just blank. I had to shut down it hard. It came back up > seemingly fine. But yum update doesn't work anymore. It says "Error > importing repomd.xml from base/7/x86_64: Damaged repomd.xml file" > I looked at the logs, but journalctl only shows the latest boot on > this > machine. > > So I guess I have three questions > - Any idea what happened with the update process? > - How can I repair repomd.xml?No suggestions about the best way to restore repomd.xml? /Robin
On 14/06/2020 17:09, Robin Lee wrote:> On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote: >> Today when I ran yum update two packages came up microcode_ctl >> and unbound-libs. The updating process went fine until it outputted >> >> Running transaction >> Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 >> >> then it just froze. I could no longer ssh to the machine and the >> console was just blank. I had to shut down it hard. It came back up >> seemingly fine. But yum update doesn't work anymore. It says "Error >> importing repomd.xml from base/7/x86_64: Damaged repomd.xml file" >> I looked at the logs, but journalctl only shows the latest boot on >> this >> machine. >> >> So I guess I have three questions >> - Any idea what happened with the update process? >> - How can I repair repomd.xml? > > > No suggestions about the best way to restore repomd.xml? > > /Robin >Try: yum --enablerepo=\* clean all
On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote:> Today when I ran yum update two packages came up microcode_ctl > and unbound-libs. The updating process went fine until it outputted > > Running transaction > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > then it just froze. I could no longer ssh to the machine and the > console was just blank. I had to shut down it hard. It came back up > seemingly fine. But yum update doesn't work anymore. It says "Error > importing repomd.xml from base/7/x86_64: Damaged repomd.xml file" > I looked at the logs, but journalctl only shows the latest boot on > this > machine. > > So I guess I have three questions > - Any idea what happened with the update process? > - How can I repair repomd.xml?Now that yum is up and running again it tells me the following "There are unfinished transactions remaining. You might consider running yum-complete-transaction, or "yum-complete-transaction -- cleanup-only" and "yum history redo last", first to finish them. If those don't work you'll have to try removing/installing packages by hand (maybe package-cleanup can help)." Doing "yum-complete-transaction --cleanup-only" should be safe, right? To clean up the botched microcode_ctl update and after that set it among excluded packages. /Robin
On Mon, 2020-06-15 at 22:25 +0200, Robin Lee wrote:> On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote: > > Today when I ran yum update two packages came up microcode_ctl > > and unbound-libs. The updating process went fine until it > > outputted > > > > Running transaction > > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > > > then it just froze. I could no longer ssh to the machine and the > > console was just blank. I had to shut down it hard. It came back up > > seemingly fine. But yum update doesn't work anymore. It says "Error > > importing repomd.xml from base/7/x86_64: Damaged repomd.xml file" > > I looked at the logs, but journalctl only shows the latest boot on > > this > > machine. > > > > So I guess I have three questions > > - Any idea what happened with the update process? > > - How can I repair repomd.xml? > > Now that yum is up and running again it tells me the following > > "There are unfinished transactions remaining. You might consider > running yum-complete-transaction, or "yum-complete-transaction -- > cleanup-only" and "yum history redo last", first to finish them. If > those don't work you'll have to try removing/installing packages by > hand (maybe package-cleanup can help)." > > Doing "yum-complete-transaction --cleanup-only" should be safe, > right? > To clean up the botched microcode_ctl update and after that set it > among excluded packages.Is there some more information about this issue? I've found this ticket https://bugs.centos.org/view.php?id=17452 I'm wondering how safe it is to update the microcode_ctl package on other Centos machines I have? They don't have a Supermicro motherboard. Cheers Robin