Discuss August 2020

discuss@lists.centos.org

95 participants
66 discussions

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2020