search for: 8d1b

...============ ================ ================ SIP/8484-00000000 Am conf-adminmenu 8484 SIP/8484-00000001 m conf-menu 8484 SIP/8484-00000002 Am conf-adminmenu 8484 -- Channel SIP/8484-00000001 left 'softmix' base-bridge <485fcffc-49ad-4e86-8d1b-4655631a232a> -- Channel CBAnn/1701414-00000000;2 joined 'softmix' base-bridge <485fcffc-49ad-4e86-8d1b-4655631a232a> -- <CBAnn/1701414-00000000;1> Playing 'confbridge-leave.gsm' (language '') -- Channel CBAnn/1701414-00000000;2 left 'softmix...

...d by some volfile/checksum mismatch. try to look glusterd log file(/var/log/glusterfs/glusterd.log) in REJECTED node, and find some log like below [2014-06-17 04:21:11.266398] I [glusterd-handler.c:2050:__glusterd_handle_incoming_friend_req] 0-glusterd: Received probe from uuid: 81857e74-a726-4f48-8d1b-c2a4bdbc094f [2014-06-17 04:21:11.266485] E [glusterd-utils.c:2373:glusterd_compare_friend_volume] 0-management: Cksums of volume supportgfs differ. local cksum = 52468988, remote cksum = 2201279699 on peer 172.26.178.254 [2014-06-17 04:21:11.266542] I [glusterd-handler.c:3085:glusterd_xfer_friend_...

Hi, I have a 3 nodes replica (including arbiter) volume with GlusterFS 3.8.11 and this night one of my nodes (node1) had an out of memory for some unknown reason and as such the Linux OOM killer has killed the glusterd and glusterfs process. I restarted the glusterd process but now that node is in "Peer Rejected" state from the other nodes and from itself it rejects the two other nodes

...ile/checksum mismatch. try to look > glusterd log file(/var/log/glusterfs/glusterd.log) in REJECTED node, and > find some log like below > [2014-06-17 04:21:11.266398] I [glusterd-handler.c:2050:__glusterd_handle_incoming_friend_req] 0-glusterd: Received probe from uuid: 81857e74-a726-4f48-8d1b-c2a4bdbc094f > [2014-06-17 04:21:11.266485] E [glusterd-utils.c:2373:glusterd_compare_friend_volume] 0-management: Cksums of volume supportgfs differ. local cksum = 52468988, remote cksum = 2201279699 on peer 172.26.178.254 > [2014-06-17 04:21:11.266542] I [glusterd-handler.c:3085:glusterd_xf...

Hi I cant start a hvm domU with more than 3 nic's configured... why? it is a bug? With previous versions it was possible... here the config - it is an opnsense (openbsd) hvm domU: name = "fenrir.chao5.int" uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859" maxmem = 2048 memory = 2048 loader = '/usr/lib64/xen/boot/hvmloader' type = "hvm" vcpus = 2 rtc_timeoffset = 0 localtime = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vnc = 1 vncunused = 0 vncdisplay = 100 v...

Hi can someone say me whats wrong in this config: <domain type='xen'> <name>fenrir.chao5.int</name> <uuid>7aedcd03-54e8-4055-8d1b-37dd34194859</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='static'>2</vcpu> <os> <type arch='x86_64' machine='xenfv'>hvm<...

Hi I cant start a hvm domU with more than 3 nic's configured... why? it is a bug? With previous versions it was possible... here the config - it is an opnsense (openbsd) hvm domU: name = "fenrir.chao5.int" uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859" maxmem = 2048 memory = 2048 loader = '/usr/lib64/xen/boot/hvmloader' type = "hvm" vcpus = 2 rtc_timeoffset = 0 localtime = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vnc = 1 vncunused = 0 vncdisplay = 100 v...

...t; Hi > > I cant start a hvm domU with more than 3 nic's configured... why? it is > a bug? > With previous versions it was possible... > > here the config - it is an opnsense (openbsd) hvm domU: > > name = "fenrir.chao5.int" > uuid = "7aedcd03-54e8-4055-8d1b-37dd34194859" > maxmem = 2048 > memory = 2048 > loader = '/usr/lib64/xen/boot/hvmloader' > type = "hvm" > vcpus = 2 > rtc_timeoffset = 0 > localtime = 1 > on_poweroff = "destroy" > on_reboot = "restart" > on_crash = "rest...