Here is the contents of the entire
cat /etc/default.grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=0
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="crashkernel=auto
rd.md.uuid=066ffecb:69137a0b:4e579b4f:dfbf1696
Running yum update on a CentOS 7.9 server today I encountered the following
error:
PHP Warning: PHP Startup: Unable to load dynamic library 'imap.so' (tried:
/usr/lib64/php/modules/imap.so (/usr/lib64/php/modules/imap.so: cannot open
shared object file: No such file or directory),
On 14/03/2023 17:22, James Pearson wrote:
I'm getting 'Forbidden You don't have permission to access this resource.' when
accessing https://vault.centos.org/
Is it down ?
Thanks
James Pearson
___
CentOS mailing list
CentOS@centos.org
It works for me.
On 3/14/2023 11:22 AM, James Pearson wrote:
I'm getting 'Forbidden You don't have permission to access this resource.' when
accessing https://vault.centos.org/
Is it down ?
Thanks
James Pearson
___
CentOS mailing list
I'm getting 'Forbidden You don't have permission to access this resource.' when
accessing https://vault.centos.org/
Is it down ?
Thanks
James Pearson
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Am 14.03.23 um 12:30 schrieb Rob Kampen:
OK,
found out the problem as to why it doesn't boot any kernel except 36.2
the system reports that it cannot find
vmlinuz-3.10.0-1160.88.1.el7.x86_64
or any one of the others, except for vmlinuz-3.10.0-1160.36.2.el7.x86_64
hence a manual selection
I had something like this happen some years ago on a workstation with
2-disk (software/Linux) RAID 1. Turns out one of the disks had been ejected
from the raid array. It was that ejected disk that was getting the updates,
but since it was no longer in the array it wasn't being booted, but rather
On 3/8/2023 4:08 PM, Chris Adams wrote:
Once upon a time, Bowie Bailey said:
What is going to happen when I try to mount a drive that the system
thinks is part of an existing array?
I don't _think_ anything special will happen - md RAID doesn't go
actively looking for drives like that AFAIK.
OK,
found out the problem as to why it doesn't boot any kernel except 36.2
the system reports that it cannot find
vmlinuz-3.10.0-1160.88.1.el7.x86_64
or any one of the others, except for vmlinuz-3.10.0-1160.36.2.el7.x86_64
hence a manual selection from the grub menu when in front of the
Change it to
GRUB_DEFAULT=0
(I encountered the same issue week ago with a workstation booted for three month with an older
kernel because of https://bugzilla.redhat.com/show_bug.cgi?id=2143438 , and solved it this way)
Regards,
Petko
On 3/14/23 10:51, Rob Kampen wrote:
Can I edit
This issue has been around for some months, but other things keep
crowding out a fix.
uname give me
3.10.0-1160.36.2.el7.x86_64 #1 SMP Wed Jul 21 11:57:15 UTC 2021
yet I have
3.10.0-1160.76.1.el7.x86_64
3.10.0-1160.81.1.el7.x86_64
3.10.0-1160.83.1.el7.x86_64
3.10.0-1160.88.1.el7.x86_64
11 matches
Mail list logo