What I meant is that you sent logs created at different times so I was
unable to match both ends (engine and vdsm.
It would be great if you could sent the logs from the same time.
On Wed, Oct 12, 2016 at 1:22 PM, Gianluca Cecchi <gianluca.cec...@gmail.com>
> On Wed, Oct 12, 2016 at 1:08 PM, Piotr Kliczewski <pklic...@redhat.com>
>> Is it possible to login to the system and take a look at the logs.
>> If so please send me details offline.
> Unfortunately not to this particular system. The other one is one of my
> home systems and I can manage something perhaps.
> But are you interested in any particular log? I can upload without
> 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.
> Possibly I made the same configuration errors on both, or the problem is
> passing from 3. to 4.0.
> But the original originator of the thread perhaps had this problem
> (solved?) with diect installation in 4.0.
> He said in one of his posts:
> all nodes and engines are synced to the same timeserver.
> 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.
> the certificate that get's presented be vdsm on port 54321 looks ok.
> 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
> Does 3.6 to 4.0 involve anything similar to his situation?
Users mailing list