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 720359 - [vdsm] [Init-script] vdsmd startup hangs forever while libvirt-guests service is running.
Summary: [vdsm] [Init-script] vdsmd startup hangs forever while libvirt-guests service...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: David Naori
QA Contact: David Naori
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-11 13:58 UTC by David Naori
Modified: 2011-12-06 07:31 UTC (History)
8 users (show)

Fixed In Version: vdsm-4.9-82
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 07:31:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:1782 0 normal SHIPPED_LIVE new packages: vdsm 2011-12-06 11:55:51 UTC

Description David Naori 2011-07-11 13:58:23 UTC
Description of problem:

When starting vdsmd and libvirt-guests service is running. vdsmd init script tries to stop libvirt-guests (CONFLICTING_SERVICES) and hangs forever on:

Running guests on default URI:

it is possible to get out of this hang by pressing enter:
vdsm: libvirt already configured for vdsm                  [  OK  ]
Starting iscsid: 
Running guests on default URI: 
error: Failed to reconnect to the hypervisor
error: no valid connection
error: authentication failed: Failed to step SASL negotiation: -1 (SASL(-1): generic failure: All-whitespace username.)


**possible sulotion is shutdown this servise instead of stop:
shutdown_conflicting_srv() {
    local srv 

    for srv in $CONFLICTING_SERVICES
    do  
        /sbin/chkconfig $srv off 
        if /sbin/service $srv status > /dev/null 2>&1;
        then
             if [ "$srv" == "libvirt-guests" ]; then
                 /sbin/service $srv shutdown
             else
                 /sbin/service $srv stop
             fi  
        fi  
    done
    return 0
}

Version-Release number of selected component (if applicable):
vdsm-4.9-81.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.service libvirt-guests start
2.service vdsmd start
  
Actual results:
startup hangs forever

Expected results:


Additional info:

Comment 2 Dan Kenigsberg 2011-07-11 14:31:16 UTC
Are you sure that `/sbin/service $srv shutdown` does not block, too? It needs sasl just as much.

Instead, I suggest

rm -f /var/lock/subsys/libvirt-guests

which would signify to libvirt-guests that it is not running. Could you verify that?

Comment 3 David Naori 2011-07-12 07:17:46 UTC
(In reply to comment #2)
> Are you sure that `/sbin/service $srv shutdown` does not block, too? It needs
> sasl just as much.
> 
> Instead, I suggest
> 
> rm -f /var/lock/subsys/libvirt-guests
> 
> which would signify to libvirt-guests that it is not running. Could you verify
> that?

tried that.

shutdown_conflicting_srv() {
    local srv

    for srv in $CONFLICTING_SERVICES
    do
        /sbin/chkconfig $srv off
        if /sbin/service $srv status > /dev/null 2>&1;
        then
             if [ "$srv" == "libvirt-guests" ]; then
                 rm -f /var/lock/subsys/libvirt-guests
             fi
             /sbin/service $srv stop
        fi
    done
    return 0
}

this dose not solve the problem.

Comment 4 David Naori 2011-07-12 08:45:53 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > Are you sure that `/sbin/service $srv shutdown` does not block, too? It needs
> > sasl just as much.
> > 
> > Instead, I suggest
> > 
> > rm -f /var/lock/subsys/libvirt-guests
> > 
> > which would signify to libvirt-guests that it is not running. Could you verify
> > that?
> 
> tried that.
> 
> shutdown_conflicting_srv() {
>     local srv
> 
>     for srv in $CONFLICTING_SERVICES
>     do
>         /sbin/chkconfig $srv off
>         if /sbin/service $srv status > /dev/null 2>&1;
>         then
>              if [ "$srv" == "libvirt-guests" ]; then
>                  rm -f /var/lock/subsys/libvirt-guests
>              fi
>              /sbin/service $srv stop
>         fi
>     done
>     return 0
> }
> 
> this dose not solve the problem.

i had a mistake. this solution works.

 shutdown_conflicting_srv() {
    local srv 

    for srv in $CONFLICTING_SERVICES
    do  
        /sbin/chkconfig $srv off 
        if /sbin/service $srv status > /dev/null 2>&1;
        then
             if [ "$srv" == "libvirt-guests" ]; then
                 rm -f /var/lock/subsys/libvirt-guests
             else
                 /sbin/service $srv stop
             fi  
        fi  
    done
    return 0
}

Comment 5 David Naori 2011-07-12 13:58:50 UTC
http://gerrit.usersys.redhat.com/#change,687

Comment 7 David Naori 2011-07-18 08:17:09 UTC
Verified  vdsm-4.9-82


[root@camel-vdsa vdsm]# /etc/init.d/vdsmd stop
Shutting down vdsm daemon: 
vdsm watchdog stop                                         [  OK  ]
vdsm stop                                                  [  OK  ]
[root@camel-vdsa vdsm]# /etc/init.d/libvirt-guests start
[root@camel-vdsa vdsm]# /etc/init.d/vdsmd start
vdsm: libvirt already configured for vdsm                  [  OK  ]
Starting iscsid: 
Starting up vdsm daemon: 
vdsm start                                                 [  OK  ]

Comment 8 errata-xmlrpc 2011-12-06 07:31:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2011-1782.html


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