Oops, reading my message I find an error : the problem occurs at 1:21AM not 1:01 :/

Frank

Le Jeudi, Octobre 25, 2018 17:55 CEST, "fsoyer" <fsoyer@systea.fr> a écrit:

Hi,
related (or maybe not) with my problem "VMs unexpectidly restarted", I have one VM (only one) which was paused then killed this morning (1:01AM).
This is the second time (first time about 15 days ago), only this one (it is on a domain with 5 others VMs, and it is not the most used of them. And it was at night, without any particular treatment at this time). The others VMs on the same storage were not impacted at all. And it is not on the same storage domain as the other VM of "VMs unexpectidly restarted"...
At the same time, gluster seems to have seen absolutly nothing. Is there really a storage issue ??

Here are some revelant logs
/var/log/messages of the node
vdsm.log
engine.log
glusterd.log
data01-brick.log

For recall, this is a 3 nodes 4.2.3 cluster, on Gluster 3.12.13 (2+arbiter).
Any idea where or what I must search for ?

Thanks
--

Cordialement,

Frank