search for: 94ef

...tted this and provided me with the attached patch that solved the problem. We'd be grateful if you could also fix this issue upstream. Thanks, -- Andrew :-) Support Free Java! Contribute to GNU Classpath and the OpenJDK http://www.gnu.org/software/classpath http://openjdk.java.net PGP Key: 94EFD9D8 (http://subkeys.pgp.net) Fingerprint: F8EF F1EA 401E 2E60 15FA 7927 142C 2591 94EF D9D8 -------------- next part -------------- A non-text attachment was scrubbed... Name: llvm-argument_header.patch Type: text/x-patch Size: 327 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/...

...5 17:50:40 6523] DEBUG (XendDomainInfo:3428) Storing VM details: {''on_xend_stop'': ''ignore'', ''pool_name'': ''Pool-0'', ''shadow_memory'': ''2'', ''uuid'': ''35a5c3a2-5261-fd1e-94ef-710c70ca2a62'', ''on_reboot'': ''restart'', ''start_time'': ''1351201840.05'', ''on_poweroff'': ''destroy'', ''bootloader_args'': '''', ''on_xend_start'...

I'm guessing there's something wrong w.r.t address resolution on node 1. >From the logs it's quite clear to me that node 1 is unable to resolve the address configured in /etc/hosts where as the other nodes do. Could you paste the gluster peer status output from all the nodes? Also can you please check if you're able to ping "pri.ostechnix.lan" from node1 only? Does

Hello, i installed glusterfs 3.11.3 version 3 nodes ubuntu 16.04 machine. All machines have same /etc/hosts. node1 hostname pri.ostechnix.lan node2 hostname sec.ostechnix.lan node2 hostname third.ostechnix.lan 51.15.77.14 pri.ostechnix.lan pri 51.15.90.60 sec.ostechnix.lan sec 163.172.151.120 third.ostechnix.lan third volume create command is root at