RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1010353 - libvirtd failed to restart after update
Summary: libvirtd failed to restart after update
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Eric Blake
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-20 15:12 UTC by Orion Poplawski
Modified: 2013-09-30 20:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-30 20:24:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Orion Poplawski 2013-09-20 15:12:02 UTC 
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 18:48:37 UTC 
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 20:36:50 UTC 
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 20:16:27 UTC 
(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>
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 20:24:42 UTC 
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.