After creating droplet i usually update the OS by using yum update. but, centos 7.4 stuck when i do update.
Running transaction Updating : libgcc-4.8.5-16.el7_4.2.x86_64 1/42 Updating : systemd-libs-219-42.el7_4.10.x86_64 2/42 Updating : systemd-219-42.el7_4.10.x86_64 3/42 Updating : 12:dhcp-libs-4.2.5-58.el7.centos.3.x86_64 4/42 Updating : 12:dhcp-common-4.2.5-58.el7.centos.3.x86_64 5/42 Updating : selinux-policy-3.13.1-166.el7_4.9.noarch 6/42 Updating : libteam-1.25-6.el7_4.3.x86_64 7/42 Updating : kernel-tools-libs-3.10.0-693.21.1.el7.x86_64 8/42 Installing : linux-firmware-20170606-58.gitc990aae.el7_4.noarch 9/42 Installing : kernel-3.10.0-693.21.1.el7.x86_64 10/42 Updating : kernel-tools-3.10.0-693.21.1.el7.x86_64 11/42 Updating : teamd-1.25-6.el7_4.3.x86_64 12/42 Updating : selinux-policy-targeted-3.13.1-166.el7_4.9.noarch 13/42 Updating : 12:dhclient-4.2.5-58.el7.centos.3.x86_64 14/42 Updating : cloud-init-0.7.9-9.el7.centos.6.x86_64 15/42 Updating : systemd-sysv-219-42.el7_4.10.x86_64 16/42 Updating : 1:nfs-utils-1.3.0-0.48.el7_4.2.x86_64 17/42 Updating : libstdc+±4.8.5-16.el7_4.2.x86_64 18/42 Updating : iptables-1.4.21-18.3.el7_4.x86_64 19/42 Updating : tzdata-2018d-1.el7.noarch 20/42 Updating : libgomp-4.8.5-16.el7_4.2.x86_64 21/42 Updating : python-perf-3.10.0-693.21.1.el7.x86_64 22/42 Cleanup : 12:dhclient-4.2.5-58.el7.centos.1.x86_64 23/42 Cleanup : 12:dhcp-common-4.2.5-58.el7.centos.1.x86_64 24/42 Cleanup : 12:dhcp-libs-4.2.5-58.el7.centos.1.x86_64 25/42 Cleanup : selinux-policy-targeted-3.13.1-166.el7_4.7.noarch 26/42 Cleanup : systemd-sysv-219-42.el7_4.7.x86_64 27/42 Cleanup : cloud-init-0.7.9-9.el7.centos.2.x86_64 28/42 Cleanup : kernel-tools-3.10.0-693.17.1.el7.x86_64 29/42 Cleanup : teamd-1.25-5.el7.x86_64 30/42 Cleanup : libstdc+±4.8.5-16.el7_4.1.x86_64 31/42 Cleanup : 1:nfs-utils-1.3.0-0.48.el7_4.1.x86_64 32/42 Cleanup : selinux-policy-3.13.1-166.el7_4.7.noarch 33/42 Cleanup : tzdata-2018c-1.el7.noarch 34/42 Cleanup : systemd-219-42.el7_4.7.x86_64 35/42 Cleanup : systemd-libs-219-42.el7_4.7.x86_64 36/42 Cleanup : libgcc-4.8.5-16.el7_4.1.x86_64 37/42 Cleanup : libteam-1.25-5.el7.x86_64 38/42 Cleanup : kernel-tools-libs-3.10.0-693.17.1.el7.x86_64 39/42 Cleanup : iptables-1.4.21-18.2.el7_4.x86_64 40/42 Cleanup : libgomp-4.8.5-16.el7_4.1.x86_64 41/42 Cleanup : python-perf-3.10.0-693.17.1.el7.x86_64 42/42
nothing happened after that, tried several times.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Try DigitalOcean for free
Click below to sign up and get $100 of credit to try our products over 60 days!
Hello, mhmehedi
You can check if there are other processes that are locking yum at the same time. You can quickly check that using something like:
You can then kill/restart this process (if it’s safe to do so, e.g the process is not vital to the server system and will not cause issues to your sites/apps).
Additionally you can try to rebuild the RPM database and give it another go:
Hope that this helps! Regards, Alex
How long did you wait when reaching this point? I just attempted to replicate this issue on a fresh CentOS 7.4 droplet and found that while it did pause at this point for a couple minutes it did resume and complete.