search for: 40a1

Hi, Thanks for the beautiful product, i use it for a long time. Very stable! I would like in a new version that IPv6 fully works like IPv4 <bind-address>. Now we can only use :: With multiple interfaces the use it all on that port, this is difficult for multi icecast account on same server. Best regards, Michel -------------- next part -------------- An HTML attachment was scrubbed...

...389 Checking 0 100 389 ris-dom-contr01.MYDOMAIN.com. against SRV _ldap._tcp.dc._msdcs.MYDOMAIN.com mysamba4dc.MYDOMAIN.com 389 Checking 0 100 389 mysamba4dc.MYDOMAIN.com. against SRV _ldap._tcp.dc._msdcs.MYDOMAIN.com mysamba4dc.MYDOMAIN.com 389 Looking for DNS entry SRV _ldap._tcp.d47b6ec5-8976-40a1-ad85-6479d007ebb2.domains._msdcs.MYDOMAIN.com mysamba4dc.MYDOMAIN.com 389 as _ldap._tcp.d47b6ec5-8976-40a1-ad85-6479d007ebb2.domains._msdcs.MYDOMAIN.com. Checking 0 100 389 ris-dom-contr02.MYDOMAIN.com. against SRV _ldap._tcp.d47b6ec5-8976-40a1-ad85-6479d007ebb2.domains._msdcs.MYDOMAIN.com mysa...

...xactly sure what your problem is. Icecast supports binding to > several addresses individually. E.g. this works for me: > <listen-socket> > <bind-address>::1</bind-address> > </listen-socket> > <listen-socket> > <bind-address>2a01:*:*:*:*:*:6453:40a1</bind-address> > </listen-socket> > > Resulting in: > Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name > tcp6 0 0 ::1:8000 :::* LISTEN 12043/icecast > tcp6 0...

...exactly sure what your problem is. Icecast supports binding to several addresses individually. E.g. this works for me: <listen-socket> <bind-address>::1</bind-address> </listen-socket> <listen-socket> <bind-address>2a01:*:*:*:*:*:6453:40a1</bind-address> </listen-socket> Resulting in: Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp6 0 0 ::1:8000 :::* LISTEN 12043/icecast tcp6 0...

...We are using latest version of XCP on 6 hosts. While issuing VM.start or VM.start_on xmlrpc functional call , it says : {''Status'': ''Failure'', ''ErrorDescription'': [''SESSION_INVALID'', ''OpaqueRef:cfb6df14-387d-40a1-cc27-d5962cba7712'']} However if I put VM.start in a loop maybe after 20-30 tries it succeeds . But VM.start_on does not succeed even after 70 tries. One more observation - VM.clone succeeds after 7-8 tries VM.hard_shutdown works fine Can you guide me on this issue, Akshay...

Hi, I got the same problem as Juergen, My volume is a simple replicated volume with 2 host and GlusterFS 3.2.0 Volume Name: poolsave Type: Replicate Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: ylal2950:/soft/gluster-data Brick2: ylal2960:/soft/gluster-data Options Reconfigured: diagnostics.brick-log-level: DEBUG network.ping-timeout: 20 performance.cache-size: 512MB

Hi All, I've been having a little trouble with creating a loop that will run a a series of t.tests for inspection, Below is the code i've tried, and some checks i've looked at. I've used the get(paste()) idea as i was told previously that the use of the eval should try and be avoided. I've run a single syntax to check that my systax is correct and works without any problems

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

...-8859-48e3-96ca-60a988eb9358/AC0A736395001305C2F3644ACB0CC604E1E65070 (6ae23edb-390d-42b5-8cff-c312084ee3d8) on home-client-2 [2017-10-25 10:14:11.768041] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/1D40A1C9EFE40F52C0CBCCC7D81E9F605892CAFE (92681dd9-48ed-4af6-9e91-cb60d81c52da) on home-client-2 [2017-10-25 10:14:11.777926] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/460636CDED1990BEA1EDFBA55825993A97A3A...