Discuss August 2020

discuss@lists.centos.org

95 participants
63 discussions

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2020