search for: 106002

Hello list, I have defined a new MoH-class in musiconhold.conf : [default] mode=files directory=/var/lib/asterisk/moh random=yes ; *[106002] mode=files directory=/var/lib/asterisk/moh/106002 random=yes* In sip.conf I have this commented out : ;mohinterpret=default ;mohsuggest=default Asterisk sees these moh-classes and files : vps2301*CLI> moh show classes Class: default Mode: files Directory: /var/lib/asterisk/moh Cla...

Hello list, I'm using asterisk 1.4.30 and realtime sip. I notice that the field "musiconhold" is not working as when putting someone on hold, the default musiconhold class is always used. musiconhold.conf : [default] mode=files directory=/var/lib/asterisk/moh random=yes ; [106002] mode=files directory=/var/lib/asterisk/moh/106002 random=yes my realtime sip peers have the following in the column '*musiconhold*' : *106002* asterisk*CLI> moh show classes Class: default Mode: files Directory: /var/lib/asterisk/moh Class: 106002 Mode: files Di...

...ng on virt2) was stopped by qemu. Brick 1 (virt2) only experienced loss of quorum when starting gluster (glusterd.log confirms this): Dec 20 17:22:03 virt2 systemd[1]: Starting GlusterFS, a clustered file-system server... Dec 20 17:22:05 virt2 glusterd[739]: [2017-12-20 16:22:05.997472] C [MSGID: 106002] [glusterd-server-quorum.c:355:glusterd_do_volume_quorum_action] 0-management: Server quorum lost for volume filserver. Stopping local bricks. Dec 20 17:22:05 virt2 glusterd[739]: [2017-12-20 16:22:05.997666] C [MSGID: 106002] [glusterd-server-quorum.c:355:glusterd_do_volume_quorum_action] 0-manage...

...> > Brick 1 (virt2) only experienced loss of quorum when starting gluster > (glusterd.log confirms this): > Dec 20 17:22:03 virt2 systemd[1]: Starting GlusterFS, a clustered > file-system server... > Dec 20 17:22:05 virt2 glusterd[739]: [2017-12-20 16:22:05.997472] C > [MSGID: 106002] > [glusterd-server-quorum.c:355:glusterd_do_volume_quorum_action] > 0-management: Server quorum lost for volume filserver. Stopping local > bricks. > Dec 20 17:22:05 virt2 glusterd[739]: [2017-12-20 16:22:05.997666] C > [MSGID: 106002] > [glusterd-server-quorum.c:355:glusterd_do_...

Hey, Can you give us the volume info output for this volume? Why are you not able to get the xattrs from arbiter brick? It is the same way as you do it on data bricks. The changelog xattrs are named trusted.afr.virt_images-client-{1,2,3} in the getxattr outputs you have provided. Did you do a remove-brick and add-brick any time? Otherwise it will be trusted.afr.virt_images-client-{0,1,2} usually.

...virt2) only experienced loss of quorum when starting gluster >> (glusterd.log confirms this): >> Dec 20 17:22:03 virt2 systemd[1]: Starting GlusterFS, a clustered >> file-system server... >> Dec 20 17:22:05 virt2 glusterd[739]: [2017-12-20 16:22:05.997472] C >> [MSGID: 106002] >> [glusterd-server-quorum.c:355:glusterd_do_volume_quorum_action] >> 0-management: Server quorum lost for volume filserver. Stopping local >> bricks. >> Dec 20 17:22:05 virt2 glusterd[739]: [2017-12-20 16:22:05.997666] C >> [MSGID: 106002] >> [glusterd-server-q...

...oss of quorum when starting gluster > >> (glusterd.log confirms this): > >> Dec 20 17:22:03 virt2 systemd[1]: Starting GlusterFS, a clustered > >> file-system server... > >> Dec 20 17:22:05 virt2 glusterd[739]: [2017-12-20 16:22:05.997472] C > >> [MSGID: 106002] > >> [glusterd-server-quorum.c:355:glusterd_do_volume_quorum_action] > >> 0-management: Server quorum lost for volume filserver. Stopping local > >> bricks. > >> Dec 20 17:22:05 virt2 glusterd[739]: [2017-12-20 16:22:05.997666] C > >> [MSGID: 106002] &g...