CentOS-6.7 Problem Updating Kernel

Home » CentOS » CentOS-6.7 Problem Updating Kernel
CentOS 2 Comments

We have four identical hardware system. On one of them the most recent kernel update yields this error:

# yum history info 332
Loaded plugins: etckeeper, fastestmirror, priorities Transaction ID : 332
Begin time : Wed May 4 10:21:07 2016
Begin rpmdb : 831:9ef9185577e3d2adb2d1ff0045619e1e0d9ed23a User : root
Return-Code : ** Aborted **
Command Line : update -y Transaction performed with:
Installed rpm-4.8.0-47.el6.x86_64 @base
Installed yum-3.2.29-69.el6.CentOS.noarch @base
Installed yum-metadata-parser-1.1.2-16.el6.x86_64 @base
Installed yum-plugin-fastestmirror-1.1.30-30.el6.noarch @base Packages Altered:
** Updated initscripts-9.03.49-1.el6.CentOS.4.x86_64 @updates
Update 9.03.49-1.el6.CentOS.5.x86_64 installed
** Erase kernel-2.6.32-573.7.1.el6.x86_64 @updates
Install kernel-2.6.32-573.26.1.el6.x86_64 installed
** Updated kernel-firmware-2.6.32-573.22.1.el6.noarch @updates
Update 2.6.32-573.26.1.el6.noarch installed
** Updated kernel-headers-2.6.32-573.22.1.el6.x86_64 @updates
Update 2.6.32-573.26.1.el6.x86_64 installed
** Updated perf-2.6.32-573.22.1.el6.x86_64 @updates
Update 2.6.32-573.26.1.el6.x86_64 installed Scriptlet output:
1 error: %posttrans(kernel-2.6.32-573.26.1.el6.x86_64) scriptlet failed, signal 1
2 /sbin/dracut: line 1: 7063 Hangup ! ( umask
077; cd “$initdir”; find . | cpio -R 0:0 -H newc -o –quiet | $gzip
-9 > “$outfile” )
history info

Any ideas as to what happened and how to fix it?

2 thoughts on - CentOS-6.7 Problem Updating Kernel

  • It looks like your package update was interrupted by a SIGHUP signal
    (that’s what the Hangup is from). The %posttrans scriptlet for the kernel package was interrupted by the SIGHUP signal. No idea what might have broken, but I’d suggest reinstalling that package ‘yum resintall kernel-2.6.32-573.26.1.el6.x86_64’ and make sure it worked.

    A HUP signal is often sent when the terminal closes. Perhaps you were running the update over SSH and disconnected prematurely? Or your configuration management was interrupted?

  • Thank you.

    I have reinstalled the kernel package as instructed and will reboot the system after close of business today to see if that clears things up.