[Gluster-users] Failed to Establish Geo-replication Session Please check gsync config file. Unable to get statefile's name

Gilberto Ferreira gilberto.nunes32 at gmail.com
Wed Nov 19 18:21:30 UTC 2025


Hi there

So there is no special script.
First I try to using this:
https://github.com/aravindavk/gluster-georep-tools, and then I notice the
issue.
But after try do it by myself, I called for help.
I tried:

gluster volume geo-replication MASTERVOL root at SLAVENODE::slavevol
create push-pem

gluster volume geo-replication MASTERVOL root at SLAVENODE::slavevol start


And got the issue.


Thanks


---


Gilberto Nunes Ferreira
+55 (47) 99676-7530 - Whatsapp / Telegram






Em qua., 19 de nov. de 2025 às 15:09, Strahil Nikolov <hunter86_bg at yahoo.com>
escreveu:

> Hi Gilberto,
>
> I have no idea why my previous message was not sent (sorry about that).
> I suspect it's a bug. If you have some script or ansible playbook for the
> setup, it could help me reproduce it locally.
>
>
> Best Regards,
> Strahil Nikolov
>
> В вторник, 11 ноември 2025 г. в 16:55:59 ч. Гринуич+2, Gilberto Ferreira <
> gilberto.nunes32 at gmail.com> написа:
>
>
> Any clue about this issue?
>
>
>
>
>
>
> Em seg., 10 de nov. de 2025 às 14:47, Gilberto Ferreira <
> gilberto.nunes32 at gmail.com> escreveu:
>
> I still don't get it, because with Debian BookWorm and Gluster 10, geo-rep
> works perfectly.
> It's something about Trixie and Gluster 11.x.
>
>
>
>
>
> Em seg., 10 de nov. de 2025 às 14:45, Karl Kleinpaste <karl at kleinpaste.org>
> escreveu:
>
> On 11/10/25 12:21 PM, Gilberto Ferreira wrote:
>
> And yes. With gluster 11.2 from github repo, the very some error:
> gluster vol geo VMS gluster3::VMS-REP create push-pem
> Please check gsync config file. Unable to get statefile's name
> geo-replication command failed
>
>
> I had this problem a year ago, Aug 2024
> <https://lists.gluster.org/pipermail/gluster-users/2024-August/040625.html>.
> I went rounds and rounds with Strahil for a week, trying to find why I
> couldn't cross the finish line of successful georep. It always ends in:
>
> Please check gsync config file. Unable to get statefile's name
> geo-replication command failed
>
> The volumes were set up properly, the commands for georep were done
> correctly, per guidelines, but georep was left forever in a state of
> Created, never Active.
>
> Finally I just gave up. I can't use gluster if it won't work with me. I
> found that gluster would not give enough adequate diagnostics to provide a (
> *useful*!) explanation of what is actually wrong.
> ________
>
>
>
> Community Meeting Calendar:
>
> Schedule -
> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://meet.google.com/cpu-eiue-hvk
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
>
> ________
>
>
>
> Community Meeting Calendar:
>
> Schedule -
> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://meet.google.com/cpu-eiue-hvk
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20251119/aed0ffb0/attachment.html>


More information about the Gluster-users mailing list