<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Aug 15, 2014 at 12:30 PM, Dan Kenigsberg <span dir="ltr">&lt;<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><br>
<br>
</div></div>ifcfg-ovirtmgmt network should be found on disk after a successful<br>
installation of a host. However, if network configuration phase fails,<br>
ifcfg files should be reverted to their original values.<br></blockquote><div><br></div><div>ok.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<br>
Could you see your super/vdsm.log if that is the case?<br>
Could you explain when did &quot;hypervisor part goes in timeout&quot;. Can you<br>
correlate this to something in vdsm.log?<br>
<span><font color="#888888"><br>
Dan.<br>
</font></span></blockquote></div><br></div><div class="gmail_extra">So, initial config was no dns and I forgot the /etc/hosts part too.</div><div class="gmail_extra">So engine-setup complained about hostname input and asked again.</div>

<div class="gmail_extra">At this point I filled up /etc/hosts and confirmed hostname in engine-setup prompt.</div><div class="gmail_extra">It complained about dns part but continued.</div><div class="gmail_extra">As this is an all-in-one setup it arrived at the hypervisor config part.</div>

<div class="gmail_extra">It gave in engine-setup output the message about time out in having hypervisor host up a few times and at the end</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">
[ INFO  ] Still waiting for VDSM host to become operational...</div><div class="gmail_extra">[ ERROR ] Timed out while waiting for host to start. Please check the logs.</div></div><div class="gmail_extra"><br></div><div class="gmail_extra">
During these recurring time-out warnings I see in vdsm.log</div>
<div class="gmail_extra"><div class="gmail_extra">Detector thread::ERROR::2014-08-13 17:48:59,482::protocoldetector::104::vds.MultiProtocolAcceptor::(serve_forever) Unhandled exception</div><div class="gmail_extra">Traceback (most recent call last):</div>
<div class="gmail_extra">  File &quot;/usr/share/vdsm/protocoldetector.py&quot;, line 100, in serve_forever</div><div class="gmail_extra">    self._process_events()</div><div class="gmail_extra">  File &quot;/usr/share/vdsm/protocoldetector.py&quot;, line 117, in _process_events</div>
<div class="gmail_extra">    self._accept_connection()</div><div class="gmail_extra">  File &quot;/usr/share/vdsm/protocoldetector.py&quot;, line 180, in _accept_connection</div><div class="gmail_extra">    client_socket, _ = self._socket.accept()</div>
<div class="gmail_extra">  File &quot;/usr/lib64/python2.6/site-packages/vdsm/sslutils.py&quot;, line 121, in accept</div><div class="gmail_extra">    raise SSL.SSLError(&quot;%s, client %s&quot; % (e, address[0]))</div><div class="gmail_extra">
SSLError: unexpected eof, client 192.168.122.51</div><div class="gmail_extra"><br></div><div class="gmail_extra">engine-setup went ahead with these messages:</div><div class="gmail_extra"><div class="gmail_extra"><br></div>
<div class="gmail_extra">[WARNING] Local storage domain not added because the VDSM host was not up. Please add it manually.</div><div class="gmail_extra">[ INFO  ] Stage: Clean up</div><div class="gmail_extra">          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140813173448-i47i1l.log</div>
<div class="gmail_extra">[ INFO  ] Generating answer file &#39;/var/lib/ovirt-engine/setup/answers/20140813174959-setup.conf&#39;</div><div class="gmail_extra">[ INFO  ] Stage: Pre-termination</div><div class="gmail_extra">
[ INFO  ] Stage: Termination</div><div class="gmail_extra">[ INFO  ] Execution of setup completed successfully</div><div class="gmail_extra"><br></div><div class="gmail_extra">inside supervdsm.log no error message. See it here:</div>
<div class="gmail_extra"><a href="https://drive.google.com/file/d/0BwoPbcrMv8mvRVpxR3UzYU9hUmM/edit?usp=sharing">https://drive.google.com/file/d/0BwoPbcrMv8mvRVpxR3UzYU9hUmM/edit?usp=sharing</a><br></div><div class="gmail_extra">
<br></div><div class="gmail_extra">in connectivity.log I see only:</div><div class="gmail_extra"><div class="gmail_extra">2014-08-13 17:39:41,206:DEBUG:recent_client:True, lo:(operstate:up speed:0 duplex:unknown), ;vdsmdum</div>
<div class="gmail_extra">my;:(operstate:down speed:0 duplex:unknown), bond0:(operstate:down speed:0 duplex:unknown), eth0:(operstate:up speed:0 duplex:unknown)</div><div class="gmail_extra">2014-08-13 17:40:11,360:DEBUG:recent_client:False</div>
<div><br></div><div>At this moment it seems I can&#39;t do anything on the host, nor reinstall or activate or anything...</div><div><br></div><div>BTW: the VM fo all-in-one has 6Gb of ram configured... could it be the cause in any way?</div>
</div><div class="gmail_extra"><br></div><div class="gmail_extra">Gianluca</div></div></div><div class="gmail_extra"><br></div><div class="gmail_extra"> </div><div class="gmail_extra"><br></div></div>