Hi Gilberto, It should as long as it's the same problem. It will be nice to share your experience in the mailing list. Best Regards,Strahil Nikolov On Sat, Nov 22, 2025 at 18:13, Gilberto Ferreira<[email protected]> wrote: Hi Should it work with Debian Trixie (13) as well? I will try it
--- Gilberto Nunes Ferreira+55 (47) 99676-7530 - Whatsapp / Telegram Em sáb., 22 de nov. de 2025 às 12:37, Strahil Nikolov <[email protected]> escreveu: Hi Gilberto, I think debian12 packages don't have https://github.com/gluster/glusterfs/pull/4404/commits/c433a178e8208e1771fea4d61d0a22a95b8bc74b Run on source and destination this command and try again: sed -i 's/readfp/read_file/g' /usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/gsyncdconfig.py In my test setup where source and destinations are each a single debian 12 with a hackishl created gluster_shared_storage volume and executing the sed, I got: # gluster volume geo-replication vol1 geoaccount@gluster2::georep create push-pem Creating geo-replication session between vol1 & geoaccount@gluster2::georep has been successful Best Regards, Strahil Nikolov В събота, 22 ноември 2025 г. в 16:34:30 ч. Гринуич+2, Gilberto Ferreira <[email protected]> написа: here the story about gluster 12dev faulty error: https://github.com/gluster/glusterfs/issues/4632 Em sáb., 22 de nov. de 2025 às 10:59, Gilberto Ferreira <[email protected]> escreveu: Hello there My testing was with proxmox 9 which has Debian 13.I tried with gluster 11.1 from Debian repo and then version 11.2 from git repo.I got statefile's name issue with both.Then I compiled the version 12dev and could create geo-replication session with success but got faulty status So that's it. --- Gilberto Nunes Ferreira +55 (47) 99676-7530 Proxmox VE Em sáb., 22 de nov. de 2025, 10:14, Strahil Nikolov <[email protected]> escreveu: Hi Gilberto, What version of os and gluster do you use exaclty ? Best Regards, Strahil Nikolov В петък, 21 ноември 2025 г. в 14:08:19 ч. Гринуич+2, Gilberto Ferreira <[email protected]> написа: Hello there If there is something else I could help, please let me know. Thanks Best Regards Em qua., 19 de nov. de 2025 às 15:21, Gilberto Ferreira <[email protected]> escreveu: 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@SLAVENODE::slavevol create push-pemgluster volume geo-replication MASTERVOL root@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 <[email protected]> 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 <[email protected]> написа: Any clue about this issue? Em seg., 10 de nov. de 2025 às 14:47, Gilberto Ferreira <[email protected]> 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 <[email protected]> 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. 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 [email protected] 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 [email protected] 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 [email protected] https://lists.gluster.org/mailman/listinfo/gluster-users
