Hide Forgot
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:
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?
(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.
(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 }
http://gerrit.usersys.redhat.com/#change,687
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 ]
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