<div dir="ltr"><div>What I meant is that you sent logs created at different times so I was unable to match both ends (engine and vdsm.<br><br></div><div>It would be great if you could sent the logs from the same time.<br></div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 12, 2016 at 1:22 PM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Wed, Oct 12, 2016 at 1:08 PM, Piotr Kliczewski <span dir="ltr"><<a href="mailto:pkliczew@redhat.com" target="_blank">pkliczew@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Is it possible to login to the system and take a look at the logs.<br></div>If so please send me details offline.<br></div><div class="m_-8189189459291432698gmail-HOEnZb"><div class="m_-8189189459291432698gmail-h5"><div class="gmail_extra"><br><div class="gmail_quote"><br></div></div></div></div></blockquote><div><br></div></span><div>Unfortunately not to this particular system. The other one is one of my home systems and I can manage something perhaps.</div><div>But are you interested in any particular log? I can upload without problems.</div><div>The strange thing is that I have the same situation on two environments that are configured the same way (single host with self hosted engine) and both passed from initial configuration in 3.6.x to 4.0.x.</div><div>Possibly I made the same configuration errors on both, or the problem is passing from 3. to 4.0.</div><div>But the original originator of the thread perhaps had this problem (solved?) with diect installation in 4.0.</div><div>He said in one of his posts:</div><div><br></div><div>"</div><div><div>all nodes and engines are synced to the same timeserver. </div><div><br></div><div>as far as i can tell, the connection is from the node itself, to the vdsm on the node, so no time difference can occur.</div><div><br></div><div>the certificate that get's presented be vdsm on port 54321 looks ok. </div><div><br></div><div>For what it is worth, I changed the certificate of the hosted-engine web interface by reconfiguring apaches mod_ssl, not touching any certificate in hosted-engine:/etc/pki/ovirt-*</div></div><div>"</div><div><br></div><div>Does 3.6 to 4.0 involve anything similar to his situation?</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Gianluca</div><div> </div></font></span></div></div></div>
</blockquote></div><br></div>