SOLVED Service failures after upgrading system to CentOS version 7.6

[SergioIS]

Check this thread to see if it's useful to you:
SOLVED - Service failures after upgrading system to CentOS version 7.6

Hi,

This is the content of /etc/selinux/config

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
#SELINUX=disabled
SELINUX=disabled
# SELINUXTYPE= can take one of three two values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are pr$
# mls - Multi Level Security protection.
SELINUXTYPE=targeted


The version of centos is: CentOS Linux release 7.6.1810 (Core)

From what I understand of the post the problem is in the actualization of the centos itself, is it possible from cpanel to deactivate centos updates?

Thank you

 

[cPanelMichael]

On the last occasion the server was installed from 0 two weeks ago, and by restarting it from the WHM panel today it has corrupted the GRUB again.

Hi @SergioIS,

Can you provide more details about how GRUB was corrupted? Is there a specific error message you encountered?

Thank you.

 

[marcuszan]

Hello,

After updating cPanel to version v76.0.18 (Centos 7) and restarting the server it does not restart.

Apparently the update corrupts the GRUB, it has happened twice.

On the last occasion the server was installed from 0 two weeks ago, and by restarting it from the WHM panel today it has corrupted the GRUB again.

Any suggestion of the reason and / or solution?

Thank you

Did you try the solutions mentioned in this thread ?

 

[mickael]

Hello

There is now 1 month ago I have a new dedicated server from - Removed - which is a CentOS 7.6 with WHM / Cpanel, it was under Kernel (in hardware) and from 5 days WHM put me this note:

"You must reboot the server to apply software updates."

And today I restarted the dedicated server but it refuses to start (ping problem) so it now goes through a kernel home OVH (not hardware) and I really like that the kernel is in hardware.

Do you know where the problem might come from? Because I have no knowledge in all that is kernel.

OVH mail :
Here are the details of this operation:
Boot on diagnostic interface (rescue)
Date 2019-02-08 19:12:37 CET (UTC + 01: 00), maxence C did Boot on diagnostic interface (rescue):
  Here is the detail of the intervention carried out:
The server remains blocked during the boot phase on the message:
(GRUB>)
A restart on a standard OVH kernel ('netboot') corrects the problem.

Login server, ping and ports ok

recommendations:
Configuration / error to be corrected by the customer

Greetings

 

[mickael]

Hello,

I read everything, for my case it works with this:

grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg

Thank, salutations