[Gluster-users] geo-rep will not initialize

[Karl Kleinpaste]

On 8/22/24 14:08, Strahil Nikolov wrote:
> I can try to reproduce it if you could provide the gluster version, 
> operating system and volume options.

Most kind.

Fedora39,  Packages:

$ grep gluster /var/log/rpmpkgs
gluster-block-0.5-11.fc39.x86_64.rpm
glusterfs-11.1-1.fc39.x86_64.rpm
glusterfs-cli-11.1-1.fc39.x86_64.rpm
glusterfs-client-xlators-11.1-1.fc39.x86_64.rpm
glusterfs-cloudsync-plugins-11.1-1.fc39.x86_64.rpm
glusterfs-coreutils-0.3.2-1.fc39.x86_64.rpm
glusterfs-events-11.1-1.fc39.x86_64.rpm
glusterfs-extra-xlators-11.1-1.fc39.x86_64.rpm
glusterfs-fuse-11.1-1.fc39.x86_64.rpm
glusterfs-geo-replication-11.1-1.fc39.x86_64.rpm
glusterfs-resource-agents-11.1-1.fc39.noarch.rpm
glusterfs-server-11.1-1.fc39.x86_64.rpm
glusterfs-thin-arbiter-11.1-1.fc39.x86_64.rpm
libglusterfs0-11.1-1.fc39.x86_64.rpm
libvirt-daemon-driver-storage-gluster-9.7.0-4.fc39.x86_64.rpm
python3-gluster-11.1-1.fc39.x86_64.rpm
qemu-block-gluster-8.1.3-5.fc39.x86_64.rpm

(Somewhere along the way, I'm sure I just did "dnf install *gluster*".)

The two volumes were created using the quick start guide:
https://docs.gluster.org/en/main/Quick-Start-Guide/Quickstart/
which means that, after establishing peering, I used these simple commands:

(on pjs) gluster volume create j pjs:/xx/brick
(on pms) gluster volume create n pms:/xx/brick

where /xx on these 2 systems are small, spare, otherwise empty, 
identical filesystems of about 40G, formatted ext4. No other options 
were used in creation.

As I said in my initial note, it seems that the underlying problem (from 
logged complaints) is lack of ageo-reptemplate configuration from which 
to set up, and I simply don't know where/how/when that should have been 
created. But this is just a surmise on my part.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20240822/1cf37aa0/attachment.html>