search for: glustera

...use NetworkManager ? After all ,anything network related should be done by it. [root at system ~]# nmcli connection add con-name dummy0 ifname dummy0 type dummy ? Connection 'dummy0' (9fdd74fa-c143-4991-9bac-0e542704ac89) successfully added. [root at system ~]# reboot Shared connection to glustera closed. [root at system ~]# uptime 03:23:44 up 0 min, ?1 user, ?load average: 1,57, 0,48, 0,17 [root at glustera ~]# nmcli connection show ? NAME ???UUID ?????????????????????????????????TYPE ?????DEVICE ? dummy0 ?9fdd74fa-c143-4991-9bac-0e542704ac89 ?dummy ????dummy0 [root at system ~]# ip a s...

...-Guide/Geo-Replication/#password-less-ssh I have a volume called "ansible" which is only a small volume and seemed like an ideal test case. Firstly, for a bit of feedback (this isn't my issue as I worked around it) I had this problem with instructions from the above guide: root at glusterA:/data/brick# gluster volume geo-replication ansible geoaccount at glusterX::ansible create push-pem gluster command not found on glusterX for user geoaccount. geo-replication command failed Once I'd made a symlink to the gluster executable into the path for the geoaccount user, I ran the com...

...all ,anything network related should be done by it. > > [root at system ~]# nmcli connection add con-name dummy0 ifname dummy0 type dummy > Connection 'dummy0' (9fdd74fa-c143-4991-9bac-0e542704ac89) successfully added. > > [root at system ~]# reboot > Shared connection to glustera closed. > > > [root at system ~]# uptime > 03:23:44 up 0 min, 1 user, load average: 1,57, 0,48, 0,17 > [root at glustera ~]# nmcli connection show > NAME UUID TYPE DEVICE > dummy0 9fdd74fa-c143-4991-9bac-0e542704ac89 dummy dummy0...

...all ,anything network related should be done by it. > > [root at system ~]# nmcli connection add con-name dummy0 ifname dummy0 type dummy > Connection 'dummy0' (9fdd74fa-c143-4991-9bac-0e542704ac89) successfully added. > > [root at system ~]# reboot > Shared connection to glustera closed. > > > [root at system ~]# uptime > 03:23:44 up 0 min,? 1 user,? load average: 1,57, 0,48, 0,17 > [root at glustera ~]# nmcli connection show > NAME? ? UUID? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? TYPE? ? ? DEVICE > dummy0? 9fdd74fa-c143-4991-9bac-0e542704ac89? dummy? ? dummy0...

Anyone have any ideas? It's rather annoying that I can't get these to persist across reboots without using some kind of helper script. On Fri, Oct 16, 2020 at 6:37 AM Frank Even <lists+centos.org at elitists.org> wrote: > > Hello all, hoping someone can help me out here. > > I cannot get dummy interfaces on a new Cent8 build to persist across reboots. > > On Cent7

Hello all, hoping someone can help me out here. I cannot get dummy interfaces on a new Cent8 build to persist across reboots. On Cent7 - this is the process I use: Create Dummies: # cat /etc/modules-load.d/dummy.conf dummy # cat /etc/modprobe.d/dummyopts.conf options dummy numdummies=4 # ip link add dummy0 type dummy ## - repeating a/ ascending dummyN adapters for as many needed # service

...; > I have a volume called "ansible" which is only a small volume and > seemed like an ideal test case. > > > Firstly, for a bit of feedback (this isn't my issue as I worked > around it) I had this problem with instructions from the above guide: > > root at glusterA:/data/brick# gluster volume geo-replication ansible > geoaccount at glusterX::ansible create push-pem > gluster command not found on glusterX for user geoaccount. > geo-replication command failed > > > Once I'd made a symlink to the gluster executable into the path for >...

...: fbf0ebb8-deab-4388-9d8a-f722618a624b > Status: Started > Snapshot Count: 0 > Number of Bricks: 5 > Transport-type: tcp > Bricks: > Brick1: pplxgluster01.x.y.z:/glusteratlas/brick001/gv0 > Brick2: pplxgluster02..x.y.z:/glusteratlas/brick002/gv0 > Brick3: pplxgluster03.x.y.z:/glusteratlas/brick003/gv0 > Brick4: pplxgluster04.x.y.z:/glusteratlas/brick004/gv0 > Brick5: pplxglus...