I'm running into an odd problem that I've never encountered before. On any of our Centos 7.3x or 7.4x after I do a yum update and restart the VM will eventually come back up, but hangs during the boot process and d-bus and login service fails so you cannot log into the via ssh post reboot.

All of our centos VM's that are sub Centos 7.5 are exhibiting this behavior even between different minor kernel varients. However any Centos VM that is above 7.5 has been able to update normally.

Some examples of current running kernel variants that will run into this problem on an update include: $ uname -r 3.10.0-693.17.1.el7.x86_64

# uname -r 3.10.0-514.2.2.el7.x86_64

however on 7.6.1810 I was able to update kernel and reboot just fine from

$ cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) [@ws ~]$ uname -r 3.10.0-862.14.4.el7.x86_64


[@ws ~]$ cat /etc/redhat-release CentOS Linux release 7.6.1810 (Core) [@ws ~]$ uname -r 3.10.0-957.1.3.el7.x86_64

On servers that have a problem I see the following screen below and they can take upwards of 30 minutes to get to the login screen and aren't very responsive when I attempt to login via vmsphere console.

CentOs bootup

I never run into an issue like this before and checking systemctl status after I can get back into the VM didn't provide much information. Has anyone experienced this before or can point me in a direction for how to fix this? Most of these are production environments that I can't justify having offline for hours to troubleshoot, but I"m trying to avoid bringing up fresh machines and migrating services over if possible.

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.