Discuss

discuss@lists.centos.org

8 participants
34745 discussions

8.2.2004 Quick recovery and fix for unbootable machines
by Alan McRae 03 Aug '20

03 Aug '20

This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that is, the one from the latest installation media. I am running on an x86_64 architecture (see uname -i). Please use the correct shim file for your architecture (shim-<arch>-15-11.el8.<arch>.rpm) I have tested this by breaking a machine and then recovering it. It works for me. I hope someone finds it useful. Let me know. Regards Alan HOW TO BOOT AN UNBOOTABLE MACHINE ================================= 1) Download a copy of rEFind. This is a UEFI boot manager. Burn it to a USB key. # wget -O refind.zip http://sourceforge.net/projects/refind/files/0.12.0/refind-flashdrive-0.12.… # unzip refind.zip # cd refind-flashdrive-0.12.0 # dd if=refind-flashdrive-0.12.0.img bs=4096 of=/dev/sdX (sdX is the device for your USB key, this will be erased, use the whole device use sdX not sdX1) 1800+0 records in 1800+0 records out 7372800 bytes (7.4 MB, 7.0 MiB) copied, 0.980893 s, 7.5 MB/s 2) Turn off secureboot in your UEFI hardware. 3) Boot the USB key. You should get a colourful screen with icons and a filename below. Use the left/right arrow keys to select the correct grubx64.efi. Hit space to boot. Your usual grub menu should appear and the system should boot normally. HOW TO FIX THE PROBLEM ===================== 1) We need to downgrade the shim package. Now your system is running get an older copy of the correct shim package for your architecture from the CentOS installation media (e.g. CentOS-8.2.2004-x86_64-dvd1.iso) and install it. # mount CentOS-8.2.2004-x86_64-dvd1.iso /mnt # cd /mnt/BaseOS/Packages # cp shim-x64-15-11.el8.x86_64.rpm /root # cd /root # umount /mnt OR Get the package from a CentOS mirror: # cd /root # wget http://ucmirror.canterbury.ac.nz/linux/CentOS/8.2.2004/BaseOS/x86_64/os/Pac… 2) We can now reinstall the older shim package using yum. This will downgrade the package to the working version. # yum install shim-x64-15-11.el8.x86_64.rpm Last metadata expiration check: 2:11:11 ago on Sun 02 Aug 2020 11:31:06 NZST. Dependencies resolved. ==================================================================================================================================================================================== Package Architecture Version Repository Size ==================================================================================================================================================================================== Downgrading: shim-x64 x86_64 15-11.el8 @commandline 647 k Transaction Summary ==================================================================================================================================================================================== Downgrade 1 Package Total size: 647 k Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Downgrading : shim-x64-15-11.el8.x86_64 1/2 Cleanup : shim-x64-15-13.el8.x86_64 2/2 Verifying : shim-x64-15-11.el8.x86_64 1/2 Verifying : shim-x64-15-13.el8.x86_64 2/2 Installed products updated. Downgraded: shim-x64-15-11.el8.x86_64 Complete! 3) Your system should now boot normally. 4) add "exclude=shim*" to /etc/yum.conf to prevent the broken one being reinstalled. You should now be able to run 'yum update'. Remove the exclude= when a proper fix becomes available.

5 5

GUI boot failure after latest shim (etc) updates
by Fred Smith 03 Aug '20

03 Aug '20

This isn't the problem everyone else has been talking about, but... I made sure that yum update offered the packages Johnny said it should then updated. when I rebooted everything looked normal except it was taking a long time to bring up the login screen. Flipped over to ALT-F2 and saw a message about waiting for Plymouth boot screen to quit. I waited a while and it went up to (and past) 15 minutes. It said "no limit" so it apparently would have gone on forever. I couldn't get to a text-mode screen with ALT-f[2-6] so I went down to my Linux laptop to see if I could ssh into this box. Lo and behold, ssh worked fine. So I ran top and saw a plymouth (or plymouthd, I forget which) at the top of the list. killed it, came back upstairs and it was no longer spewing that message. now ALT-f2 gave me a text login, that I'm using now. I ran startx and after a long-seeming wait I get a desktop, but it is NOT my normal Mate desktop. Might be Gnome (since I installed a Centos Gnome system and retrofitted Mate from EPEL). Johnny had said we needed to make sure the kernel was installed along with the shim, et al. I looked at the list of files YUM wanted to install and saw some kernel files, so I assumed all was well. But maybe I missed something. What info can I provide to help figure this out? Or, what Kernel files should I force to be (re)installed? Also, I don't very often manually force a kernel install, but I know that some of the files are updates and some are installs, I'd appreciate a reminder of which is which so I can force it. Thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- The eyes of the Lord are everywhere, keeping watch on the wicked and the good. ----------------------------- Proverbs 15:3 (niv) -----------------------------

1 0

Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
by david 02 Aug '20

02 Aug '20

At 07:57 AM 8/2/2020, you wrote: >On Sun, 2 Aug 2020 at 10:20, david <david(a)daku.org> wrote: > > > > > > ><snip> > > > > > > > > > > > >> Yes .. it should be on mirror.centos.org now .. you could change the > > > >> repo where your updates come from.Ã OR > .. wait for that mirror to get > > > >> updated. > > > > > > > > > > > > I just did > > > > yum clean all > > > > yum update > > > > > > > > and 15-8 showed up.Ã Maybe the 'clean all' > > > did it, or maybe just showed up. > > > > > > > > I applied the update (yum update), rebooted and... > > > > no boot.Ã Just a blank screen. > > > > > > > > Hardware is a Mac-Mini :-( > > > > > > > > This is not an essential machine, so I could re-install (from > > > > netinstall) if you think it's worth the effort. > > > > > > > > Or what? > > > > > > > > David > > > > > >You just need to reinstall the kernel and it should work. > > > > > > > Sorry for being so ignorant, but I don't > > understand "just reinstall the kernel". I don't > > know how to translate that into a specific yum or rpm command. > >I agree it is a lot of shorthand because of expectations. In the end >we (the list) don't know what you have on your system or what state it >is in. In order to get that information to help we would need you to >try the following: > >1. boot using a working USB/cdrom/netboot path and installer >2. choose the rescue mode >3. have the rescue mount the disks as local and chroot into the >system. << if possible have the system also bring up networking >> > >Then >yum list kernel shim grub2 mokutil > >It would also help to know which kind of Mac Mini it is (year, model, >firmware versions). Apple changes the internal hardware of these >things and how they boot so if there it may be that a particular model >is more affected than others. How does one obtain that information? There's nothing written on the box. David

2 1

Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable
by david 02 Aug '20

02 Aug '20

><snip> > >> Yes .. it should be on mirror.centos.org now .. you could change the > >> repo where your updates come from.Â OR .. wait for that mirror to get > >> updated. > > > > > > I just did > > yum clean all > > yum update > > > > and 15-8 showed up.Â Maybe the 'clean all' > did it, or maybe just showed up. > > > > I applied the update (yum update), rebooted and... > > no boot.Â Just a blank screen. > > > > Hardware is a Mac-Mini :-( > > > > This is not an essential machine, so I could re-install (from > > netinstall) if you think it's worth the effort. > > > > Or what? > > > > David > >You just need to reinstall the kernel and it should work. Sorry for being so ignorant, but I don't understand "just reinstall the kernel". I don't know how to translate that into a specific yum or rpm command. However, since this is a crash-and-burn system, I'm going back to a virgin install with netinstall of 7 2003. I'll let you know what the results are. --------------- On a Mac-Mini, which got hit by the bug in shim, I re-installed Centos 7 2003 from netinstall, selecting minimal as the software selection. The reboot worked fine. So, I next tried "yum -y update", noticed shim 7-8 got selected. However, at the completion of the update, I did a reboot and got a blank screen. No grub choices. Not good. David

1 0

Boot failed on latest CentOS 7 update
by Kay Schenk 02 Aug '20

02 Aug '20

Totally and completely on my HP microfiber. Wouldn't get past anything to even get me into the grub menu. NOT AMUSED! _______________________ Kay Schenk

2 2

pgbouncer.pid Permissions on CentOS 7
by Bee.Lists 01 Aug '20

01 Aug '20

I’ve installed pgbouncer on CentOS7 and it’s reliant upon a .pid file: 2020-07-31 04:58:34.082 EDT [3682] DEBUG parse_ini_file: 'logfile' = '/var/log/pgbouncer/pgbouncer.log' 2020-07-31 04:58:34.082 EDT [3682] DEBUG parse_ini_file: 'logfile' = '/var/log/pgbouncer/pgbouncer.log' ok:1 2020-07-31 04:58:34.082 EDT [3682] DEBUG parse_ini_file: 'pidfile' = '/var/run/pgbouncer/pgbouncer.pid' 2020-07-31 04:58:34.082 EDT [3682] DEBUG parse_ini_file: 'pidfile' = '/var/run/pgbouncer/pgbouncer.pid' ok:1 However the service isn’t starting because the ownership of the parent directory, pgbouncer:pgbouncer results in some permissions issues: 2020-07-31 04:58:34.089 EDT [3682] FATAL could not open pidfile '/var/run/pgbouncer/pgbouncer.pid': Permission denied /var/run/ has special flushing behaviour which I want to retain, but I need to get around this permission issue. Changing ownership on this directory just results in an automatic ownership set by the service, so that’s not an option. - Is there another location that can achieve this? - Is there any other way to solve this? I can’t find anything online, other than the same permissions issue for .pid files in this location. Cheers, Bee

2 1

8.2.2004 Latest yum update renders machine unbootable
by Alan McRae 01 Aug '20

01 Aug '20

I am running an Intel x64 machine using UEFI to boot an SSD. Installing the latest yum update which includes grub2 and kernel 4.18.0-193.14.2.el8_2.x86_64 renders the machine unbootable, blank screen where grub should be, no error messages, just hangs. After some hours I managed to modify another bootable partition (containing older software) and boot it from there. After that, I found out it is a known problem. The main point of this message is to make people aware of the problem and suggest admins don't run 'yum update' until they understand the problem and have a fix at hand. See 'UEFI boot blank screen post update' for a solution and directions to the redhat article. Regards Alan

10 15

Re: [CentOS] OpenJDK vulnerability and best way to find status of package that remediates vulnerability for CentOS
by Boushy, Phillip 31 Jul '20

31 Jul '20

>> 2. Is there a page like Ubuntu's CVE Tracker site where it shows the >> CVE, the package name, and the status > > Red Hat (CentOS's upsream) posts advisories for these sorts of things: > > https://access.redhat.com/errata/RHSA-2020:2969 > > This is the security advisory for this package. Yeah, I found this page cause harbor even links these, I apparently left out the important piece in this question "and the status per OS" - e.g. CentOS 7 "pending", CentOS 8 "released" I'm guessing there's not a central place? >> 3. If 2 is no, How can I look up the status of a package that has >> been released by upstream on CentOS? (e.g. it's been released in >> Upstream, it's available in CentOS, it's pending backport for CentOS 7) > As I mentioned earlier, the Red Hat errata site is a good place to > look. You can search for CVEs there too. This doesn't show the more critical piece though: "What is the status of the package being released per CentOS?" Leon mentioned: > https://git.centos.org/rpms/java-11-openjdk/releases Which (assuming I'm reading this right) seems like 11.0.8 was released for CentOS 7 15 days ago...? c7 = CentOS 7 But 11.0.8 isn't in the YUM repo, so that doesn't seem accurate. I'm trying to find out "Ok, it's been released for CentOS 8, what's the status of CentOS 7 - is it not vulnerable? Is it deferred? Is it pending?" Essentially I want to find out how you know that "No, but it's in the process of being built and distributed." - cause I can't tell that based on any info I've found so far.

1 0

OpenJDK vulnerability and best way to find status of package that remediates vulnerability for CentOS
by Boushy, Phillip 31 Jul '20

31 Jul '20

I have a docker image based off centos:7 with java-11-openjdk-devel. It appears that the current java-11-openjdk-devel available in the CentOS 7 Yum repo is 1:11.0.7.10-4.el7_8 11.0.7 is reported to have some high vulnerabilities RHSA-2020:2969 that are fixed in 11.0.8, but 11.0.8 is not available for CentOS 7. 1. Is there a 11.0.8 update for java-11-openjdk-devel available for CentOS 7? 2. Is there a page like Ubuntu's CVE Tracker site where it shows the CVE, the package name, and the status (e.g. https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-14578.html) 3. If 2 is no, How can I look up the status of a package that has been released by upstream on CentOS? (e.g. it's been released in Upstream, it's available in CentOS, it's pending backport for CentOS 7)

3 2

systemd syslog.target
by ctcard 31 Jul '20

31 Jul '20

I've noticed that there are several systemd unit files in CentOS 7 and 8 with the optionAfter=syslog.targetin the [Unit] section, but since systemd version 198 syslog.target has not existed.I deduce from this that "After=syslog.target" is ignored by systemd and can therefore be removed. Is this correct? I am writing some systemd unit files for our own services which previously used init.d scripts, so I want to ensure I'm not causing problems by omitting "After=syslog.target"ChrisSent from Samsung Mobile on O2

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss