Bug 770447 - Startup on startup of vdsm
Summary: Startup on startup of vdsm
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 979765 979771 979772
TreeView+ depends on / blocked
 
Reported: 2011-12-26 16:40 UTC by mihawk
Modified: 2016-04-18 06:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-27 10:11:25 UTC
Target Upstream Version:


Attachments (Terms of Use)
vdsm start output (38.53 KB, application/octet-stream)
2011-12-27 09:57 UTC, mihawk
no flags Details

Description mihawk 2011-12-26 16:40:30 UTC
Description of problem:

VDSM refuses to start, due to dependent services

"initctl: Unknown job: libvirtd"
"vdsm: one of the dependent services did not start, error co[FAILED]"

Version-Release number of selected component (if applicable):

RHEL 6.2

How reproducible:

Using the "service" command :
# service vdsmd start


Steps to Reproduce:
1.# service vdsmd start
  
Actual results:

# service vdsmd start
Stopping libvirtd daemon:                                  [  OK  ]
vdsm: libvirt already configured for vdsm                  [  OK  ]
Starting iscsid:
initctl: Unknown job: libvirtd
vdsm: one of the dependent services did not start, error co[FAILED]


Expected results:

# service vdsmd start
vdsm: libvirt already configured for vdsm                  [  OK  ]
Starting iscsid:
Starting up vdsm daemon:
vdsm start                                                 [  OK  ]
[root@slh-fr-bench-hyp1 init.d]#


Additional info:

Comment 1 mihawk 2011-12-26 16:43:48 UTC
This problem is due to the init script on the directory /etc/init.d/vdsmd


I just change the lines 

    352     /sbin/initctl restart libvirtd 2>/dev/null || :
to
    352     service libvirtd restart 2>/dev/null || :


    411     startout=`/sbin/initctl start libvirtd 2>&1`
to
    411     startout=`service libvirtd start 2>&1`

Because using /sbin/initctl produce this :

# /sbin/initctl start libvirtd
initctl: Unknown job: libvirtd

Comment 3 Dan Kenigsberg 2011-12-27 07:46:26 UTC
How did you install Vdsm? It should have configured libvirt to run as an upstart daemon.

Please attach the output of `bash -xv /etc/init.d/vdsmd start`. What's `rpm -q upstart vdsm` ?

Comment 4 mihawk 2011-12-27 09:56:54 UTC
Hi!

VDSM has been installed using yum.

It has been installed automaticaly by RHEV-M.

vds_bootstrap.652864.log:Fri, 23 Dec 2011 16:49:55 DEBUG    ['/usr/bin/yum', '-y', 'install', 'vdsm']


You will find in attachment the output of `bash -xv /etc/init.d/vdsmd start`

Comment 5 mihawk 2011-12-27 09:57:36 UTC
Created attachment 549669 [details]
vdsm start output

Comment 6 Dan Kenigsberg 2011-12-27 10:11:25 UTC
You did not supply the installed vdsm version, but from the logs I see that it is an oldish beta version, not the vdsm-4.9-112.1 that we all should be using now.

I suspect that you are experiencing bug 733000, please uninstall vdsm, install vdsm-4.9-112.1, and reopen the bug if there is an(other) issue.


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