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

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20251110/34d64535/attachment.html>

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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20251110/8c55c4f7/attachment.html>