mirror of
https://github.com/PegaProx/project-pegaprox.git
synced 2026-04-25 10:05:56 +03:00
[GH-ISSUE #19] 🐞 Bug: cross migration #14
Labels
No labels
Approved
Q2-3 2026 Development
bug
documentation
enhancement
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/project-pegaprox-PegaProx#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @PhiGi87 on GitHub (Jan 29, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/19
Good morning,
unfortunately something still isn’t working with the cross migration. The disk is migrated successfully to the second cluster, but—if I understand it correctly—when the RAM is supposed to be synced, the tunnel cannot be re-established because the authorization fails.
Look here in the log: https://pastebin.com/EA5gPumt
Thank you for your work.
@MrMasterbay commented on GitHub (Jan 30, 2026):
Heyha @PhiGi87 ,
We've checked this out and we've modified there our delay. @mkellermann97 configured this already and this should work with our newer version then.
Best Regards,
Nico
@mkellermann97 commented on GitHub (Jan 30, 2026):
Hi @PhiGi87,
As Nico mentioned above, we've adjusted the timeout limit. It should work without any issues now.
Regards,
Marcus
@PhiGi87 commented on GitHub (Feb 1, 2026):
Even after the update, I still have the exact same problem :-/
@mkellermann97 commented on GitHub (Feb 1, 2026):
Hi @PhiGi87 ,
please send us a detailed log and maybe even a screenshare to support@pegaprox.com .
Please note due high demand currently we are currently slow with replying.
Regards,
Marcus