Re: [Gluster-users] Fwd: Re: VM going down
Il 25/05/2017 15:24, Joe Julian ha scritto: > You'd want to see the client log. I'm not sure where proxmox > configures those to go. > > On May 24, 2017 11:57:33 PM PDT, Alessandro Briosi> wrote: > > Il 19/05/2017 17:27, Alessandro Briosi ha scritto: >> Il 12/05/2017 12:09, Alessandro Briosi ha scritto: You probably should open a bug so that we have all the troubleshooting and debugging details in one location. Once we find the problem we can move the bug to the right component. https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS HTH, Niels >>> The thing is that when the VM is down and I check the logs there's >>> nothing. >>> Then when I start the VM the logs get populated with the seek error. >>> >>> Anyway I'll open a bug for this. >> >> Ok, as it happened again I have opened a bug: >> https://bugzilla.redhat.com/show_bug.cgi?id=1452766 >> >> I now have started the vm with gdb (maybe I can find more >> information) >> >> In the logs I still have "No such file or directory" which at >> this point seems to be the culprit of this (?) >> >> Alessandro > > It heppened again and now I have at least a gdb log which tells me > where the error is. > > I've attached the log to the bug. > > Logs strangely do not report any error, though the 2 VM disk files > seem to be going through a heal process: > > Brick srvpve1g:/data/brick1/brick > /images/101/vm-101-disk-2.qcow2 - Possibly undergoing heal > > /images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal > > Status: Connected > Number of entries: 2 > > Brick srvpve2g:/data/brick1/brick > /images/101/vm-101-disk-2.qcow2 - Possibly undergoing heal > > /images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal > > Status: Connected > Number of entries: 2 > > Brick srvpve3g:/data/brick1/brick > /images/101/vm-101-disk-2.qcow2 - Possibly undergoing heal > > /images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal > > Status: Connected > Number of entries: 2 > > > I really have no clue on why this is happening. > Thanks for your help. > > Alessandro > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. It's starting to be a bit frustrating as the VM now it crashed for thr forth time... I'm considering on moving the disks to a local storage untill the problem is solved. Buon lavoro. /Alessandro Briosi/ *METAL.it Nord S.r.l.* Via Maioliche 57/C - 38068 Rovereto (TN) Tel.+39.0464.430130 - Fax +39.0464.437393 www.metalit.com ___ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Fwd: Re: VM going down
Il 25/05/2017 15:24, Joe Julian ha scritto: > You'd want to see the client log. I'm not sure where proxmox > configures those to go. This is all the content of glusterfs/cli.log (previous file cli.log.1 is from 5 days ago) [2017-05-25 06:21:30.736837] I [cli.c:728:main] 0-cli: Started running gluster with version 3.8.11 [2017-05-25 06:21:30.787152] I [MSGID: 101190] [event-epoll.c:628:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2017-05-25 06:21:30.787186] I [socket.c:2403:socket_event_handler] 0-transport: disconnecting now [2017-05-25 06:21:30.825593] I [input.c:31:cli_batch] 0-: Exiting with: 0 [2017-05-25 06:21:40.067379] I [cli.c:728:main] 0-cli: Started running gluster with version 3.8.11 [2017-05-25 06:21:40.130303] I [MSGID: 101190] [event-epoll.c:628:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2017-05-25 06:21:40.130384] I [socket.c:2403:socket_event_handler] 0-transport: disconnecting now [2017-05-25 06:21:41.268839] I [input.c:31:cli_batch] 0-: Exiting with: 0 Alessandro ___ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Fwd: Re: VM going down
You'd want to see the client log. I'm not sure where proxmox configures those to go. On May 24, 2017 11:57:33 PM PDT, Alessandro Briosiwrote: >Il 19/05/2017 17:27, Alessandro Briosi ha scritto: >> Il 12/05/2017 12:09, Alessandro Briosi ha scritto: You probably should open a bug so that we have all the >troubleshooting and debugging details in one location. Once we find the problem we >can move the bug to the right component. https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS HTH, Niels >>> The thing is that when the VM is down and I check the logs there's >nothing. >>> Then when I start the VM the logs get populated with the seek error. >>> >>> Anyway I'll open a bug for this. >> >> Ok, as it happened again I have opened a bug: >> https://bugzilla.redhat.com/show_bug.cgi?id=1452766 >> >> I now have started the vm with gdb (maybe I can find more >information) >> >> In the logs I still have "No such file or directory" which at this >> point seems to be the culprit of this (?) >> >> Alessandro > >It heppened again and now I have at least a gdb log which tells me >where >the error is. > >I've attached the log to the bug. > >Logs strangely do not report any error, though the 2 VM disk files seem >to be going through a heal process: > >Brick srvpve1g:/data/brick1/brick >/images/101/vm-101-disk-2.qcow2 - Possibly undergoing heal > >/images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal > >Status: Connected >Number of entries: 2 > >Brick srvpve2g:/data/brick1/brick >/images/101/vm-101-disk-2.qcow2 - Possibly undergoing heal > >/images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal > >Status: Connected >Number of entries: 2 > >Brick srvpve3g:/data/brick1/brick >/images/101/vm-101-disk-2.qcow2 - Possibly undergoing heal > >/images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal > >Status: Connected >Number of entries: 2 > > >I really have no clue on why this is happening. >Thanks for your help. > >Alessandro -- Sent from my Android device with K-9 Mail. Please excuse my brevity.___ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Fwd: Re: VM going down
Il 19/05/2017 17:27, Alessandro Briosi ha scritto: > Il 12/05/2017 12:09, Alessandro Briosi ha scritto: >>> You probably should open a bug so that we have all the troubleshooting >>> and debugging details in one location. Once we find the problem we can >>> move the bug to the right component. >>> https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS >>> >>> HTH, >>> Niels >> The thing is that when the VM is down and I check the logs there's nothing. >> Then when I start the VM the logs get populated with the seek error. >> >> Anyway I'll open a bug for this. > > Ok, as it happened again I have opened a bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1452766 > > I now have started the vm with gdb (maybe I can find more information) > > In the logs I still have "No such file or directory" which at this > point seems to be the culprit of this (?) > > Alessandro It heppened again and now I have at least a gdb log which tells me where the error is. I've attached the log to the bug. Logs strangely do not report any error, though the 2 VM disk files seem to be going through a heal process: Brick srvpve1g:/data/brick1/brick /images/101/vm-101-disk-2.qcow2 - Possibly undergoing heal /images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal Status: Connected Number of entries: 2 Brick srvpve2g:/data/brick1/brick /images/101/vm-101-disk-2.qcow2 - Possibly undergoing heal /images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal Status: Connected Number of entries: 2 Brick srvpve3g:/data/brick1/brick /images/101/vm-101-disk-2.qcow2 - Possibly undergoing heal /images/101/vm-101-disk-1.qcow2 - Possibly undergoing heal Status: Connected Number of entries: 2 I really have no clue on why this is happening. Thanks for your help. Alessandro ___ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Fwd: Re: VM going down
Il 12/05/2017 12:09, Alessandro Briosi ha scritto: >> You probably should open a bug so that we have all the troubleshooting >> and debugging details in one location. Once we find the problem we can >> move the bug to the right component. >> https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS >> >> HTH, >> Niels > The thing is that when the VM is down and I check the logs there's nothing. > Then when I start the VM the logs get populated with the seek error. > > Anyway I'll open a bug for this. Ok, as it happened again I have opened a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1452766 I now have started the vm with gdb (maybe I can find more information) In the logs I still have "No such file or directory" which at this point seems to be the culprit of this (?) Alessandro ___ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users