10:55 a.m.
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
2:07 p.m.
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(a)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
2:15 a.m.
New subject: VM paused then killed with "device vda reported I/O error"
2018-10-25 01:21:07,944+0200 INFO (libvirt/events) [virt.vm]
(vmId='14fb9d79-c603-4691-b19e-9133c6bd5e22') abnormal vm stop device
ua-134c4848-6897-46fc-b346-dd4a180ac653 error eio (vm:5158)
2018-10-25 01:21:07,944+0200 INFO (libvirt/events) [virt.vm]
(vmId='14fb9d79-c603-4691-b19e-9133c6bd5e22') CPU stopped: onIOError
(vm:6199)
2018-10-25 01:21:08,030+0200 INFO (libvirt/events) [virt.vm]
(vmId='14fb9d79-c603-4691-b19e-9133c6bd5e22') CPU stopped: onSuspend
(vm:6199)
This indicates an I/O error from storage layer most likely. Can you
also provide the mount logs for the gluster volume that hosts these
VM's disks (under
/var/log/glusterfs/rhev-data-center-mnt-glusterSD-<mount path>.log)
On Fri, Oct 26, 2018 at 12:38 AM fsoyer <fsoyer(a)systea.fr> wrote:
>
> 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(a)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
>
>
>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3BI45NBQTKN...
3:59 a.m.
New subject: VM paused then killed with "device vda reported I/O error"
Hi,
unfortunatly, at the time of this error there was no messages. In fact, this file
(rhev-data-center-mnt-glusterSD-victor.local.systea.fr:_DATA01.log) contains only :
[2018-10-21 01:41:11.646681] I [glusterfsd-mgmt.c:1894:mgmt_getspec_cbk] 0-glusterfs: No
change in volfile,continuing
[2018-10-28 02:08:10.081010] I [MSGID: 100011] [glusterfsd.c:1446:reincarnate]
0-glusterfsd: Fetching the volume file from server...
As I said in my another post "VMs unexpectidly restarted" which is maybe related
to this one (not exactly the same things but close enough... Please see this posts as they
can give some additional informations ? Especially the messages since sunday 28 12:42,
after I tried an export/import of a VM on saturday 27) I see no revelant error in gluster
logs at time of the problems occur on the VMs.
Though, looking on this files, I find some messages in the mount log of the second volume
DATA02, concerned by the second problem on oct-27. I'll add this messages on the other
post "VMs unexpectidly restarted" to avoid confusion. I might not have open this
new post after this one, but on the moment I couldn't be sure that this was a unique
problem.
Thank you for your time,
--
Regards,
Frank
Le Mercredi, Octobre 31, 2018 08:15 CET, Sahina Bose <sabose(a)redhat.com> a écrit:
2018-10-25 01:21:07,944+0200 INFO (libvirt/events) [virt.vm]
(vmId='14fb9d79-c603-4691-b19e-9133c6bd5e22') abnormal vm stop device
ua-134c4848-6897-46fc-b346-dd4a180ac653 error eio (vm:5158)
2018-10-25 01:21:07,944+0200 INFO (libvirt/events) [virt.vm]
(vmId='14fb9d79-c603-4691-b19e-9133c6bd5e22') CPU stopped: onIOError
(vm:6199)
2018-10-25 01:21:08,030+0200 INFO (libvirt/events) [virt.vm]
(vmId='14fb9d79-c603-4691-b19e-9133c6bd5e22') CPU stopped: onSuspend
(vm:6199)
This indicates an I/O error from storage layer most likely. Can you
also provide the mount logs for the gluster volume that hosts these
VM's disks (under
/var/log/glusterfs/rhev-data-center-mnt-glusterSD-<mount path>.log)
On Fri, Oct 26, 2018 at 12:38 AM fsoyer <fsoyer(a)systea.fr> wrote:
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(a)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
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3BI45NBQTKN...
2410
days inactive
2416
days old
3 comments
2 participants
participants (2)
-
fsoyer -
Sahina Bose