Bug 1010353 - libvirtd failed to restart after update
libvirtd failed to restart after update
Status: CLOSED INSUFFICIENT_DATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt (Show other bugs)
6.4
x86_64 Linux
unspecified Severity medium
: rc
: ---
Assigned To: Eric Blake
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-20 11:12 EDT by Orion Poplawski
Modified: 2013-09-30 16:24 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-30 16:24:42 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Orion Poplawski 2013-09-20 11:12:02 EDT
Description of problem:

On update got:

Non-fatal POSTIN scriptlet failure in rpm package libvirt-0.10.2-18.el6_4.14.x86_64
warning: %post(libvirt-0.10.2-18.el6_4.14.x86_64) scriptlet failed, exit status 1

and libvirtd was not running.  Could not find anything in either /var/log/messages or /var/log/libvirt/libvirtd.log.

This happened on 1 of my 2 virt hosts.  On the one that failed, I get:

Sep 20 09:01:51 saga libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: No such file or directory

on start up (which succeeds), which I do not see in the other machine's logs.  Cannot find any other configuration differences between the machines.
Comment 2 Eric Blake 2013-09-20 14:48:37 EDT
I'm not familiar enough with yum to know if yum logs scriptlet contents and failures in more detail in some other log - if so, it would be nice to see what part of the scriptlet is failing.

On the machine that failed, is this reproducible with 'yum reinstall libvirt'?
Comment 3 Orion Poplawski 2013-09-20 16:36:50 EDT
The scriptlet status will come from the status of the last command, which in this case is:

        /sbin/service libvirtd condrestart > /dev/null 2>&1

(which is why it wasn't running after the upgrade)

I'm afraid I can't reproduce with reinstall, or with downgrade/upgrade.
Comment 4 Eric Blake 2013-09-30 16:16:27 EDT
(In reply to Orion Poplawski from comment #0)
> 
> This happened on 1 of my 2 virt hosts.  On the one that failed, I get:
> 
> Sep 20 09:01:51 saga libvirtd: Could not find keytab file:
> /etc/libvirt/krb5.tab: No such file or directory

This appears to be a red herring - it doesn't affect actual libvirt operation.  We have an upstream patch that silences this (see bug 745203).  Backporting that patch would silence the message, but wouldn't help the real problem of determining why condrestart failed for you.  I'm inclined to close this as INSUFFICIENT_DATA if we can't come up with a way to reliably reproduce the failure.

commit fe772f24a6809b3d937ed6547cbaa9d820e514b6
Author: Cole Robinson <crobinso@redhat.com>
Date:   Sat Oct 20 14:10:03 2012 -0400

    daemon: Avoid 'Could not find keytab file' in syslog
    
    On F17 at least, every time libvirtd starts we get this in syslog:
    
    libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: No such file or directory
    This comes from cyrus-sasl, and happens regardless of whether the
    gssapi plugin is requested, which is what actually uses
    /etc/libvirt/krb5.tab.
    
    While cyrus-sasl shouldn't complain, we can easily make it shut up by
    commenting out the keytab value by default.
    
    Also update the keytab comment to the more modern one from qemu's
    sasl config file.
Comment 5 Eric Blake 2013-09-30 16:24:42 EDT
It appears that 'service libvirtd start' was able to recover; and thus that the installed version is not broken other than a glitch during the upgrade.  Without more details of what failed or a way to reproduce the failure, the workaround of manually starting libvirtd if the upgrade glitches seems like the least risky approach.

Note You need to log in before you can comment on or make changes to this bug.