Hi Nir,

Thank you for you input.

It was suggest that I try starting vdsm from the shell so I could see the
output in an effort to solve my issue:


On May 13, 2016, at 12:12 PM, Nir Soffer <nsof...@redhat.com> wrote:

On Fri, May 13, 2016 at 3:37 PM, Gervais de Montbrun
<gerv...@demontbrun.com> wrote:

Hi Charles,

I think the problem I am having is due to the setup failing and not
something in vdsm configs as I have never gotten this server to start up
properly and the BRIDGE ethernet interface + ovirt routes are not setup.

I put the logs here:

hosted-engine--deploy-logs.zip # Logs from when I tried to deploy and it
vdsm.tar.gz # /var/log/vdsm

Output from running vdsm from the command line:

[root@cultivar2 log]# su -s /bin/bash vdsm

This cannot work unless supervdsmd is running...

[vdsm@cultivar2 log]$ python /usr/share/vdsm/vdsm
(PID: 6521) I am the actual vdsm 4.17.26-1.el7
cultivar2.grove.silverorange.com (3.10.0-327.el7.x86_64)
VDSM will run with cpu affinity: frozenset([1])
/usr/bin/taskset --all-tasks --pid --cpu-list 1 6521 (cwd None)
SUCCESS: <err> = ''; <rc> = 0
Starting scheduler vdsm.Scheduler
Run and protect:
registerDomainStateChangeCallback(callbackFunc=<functools.partial object at
Run and protect: registerDomainStateChangeCallback, Return response: None
Trying to connect to Super Vdsm
Preparing MOM interface
Using named unix socket /var/run/vdsm/mom-vdsm.sock
Unregistering all secrests
trying to connect libvirt
recovery: started
Setting channels' timeout to 30 seconds.
Starting VM channels listener thread.
Listening at
Adding detector <rpc.bindingxmlrpc.XmlDetector instance at 0x3b4ecb0>
recovery: completed in 0s
Adding detector <yajsonrpc.stompreactor.StompDetector instance at 0x382e5a8>
Starting executor
Starting worker jsonrpc.Executor/0
Worker started
Starting worker jsonrpc.Executor/1
Worker started
Starting worker jsonrpc.Executor/2
Worker started
Starting worker jsonrpc.Executor/3
Worker started
Starting worker jsonrpc.Executor/4
Worker started
Starting worker jsonrpc.Executor/5
Worker started
Starting worker jsonrpc.Executor/6
Worker started
Starting worker jsonrpc.Executor/7
Worker started
XMLRPC server running
Starting executor
Starting worker periodic/0
Worker started
Starting worker periodic/1
Worker started
Starting worker periodic/2
Worker started
Starting worker periodic/3
Worker started
trying to connect libvirt
Panic: Connect to supervdsm service failed: [Errno 2] No such file or
Traceback (most recent call last):
File "/usr/share/vdsm/supervdsm.py", line 78, in _connect
 utils.retry(self._manager.connect, Exception, timeout=60, tries=3)
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 959, in retry
 return func()
File "/usr/lib64/python2.7/multiprocessing/managers.py", line 500, in
 conn = Client(self._address, authkey=self._authkey)
File "/usr/lib64/python2.7/multiprocessing/connection.py", line 173, in
 c = SocketClient(address)
File "/usr/lib64/python2.7/multiprocessing/connection.py", line 308, in
File "/usr/lib64/python2.7/socket.py", line 224, in meth
 return getattr(self._sock,name)(*args)
error: [Errno 2] No such file or directory

Vdsm tries to connect to supervdsmd on startup, and if it is not running
it will fail.

You can do:

systemctl start supervdsmd

And they you can run vdsmd from the shell.

But why do you need to run vdsm from the shell?

Users mailing list

Reply via email to