mirror of
https://github.com/PegaProx/project-pegaprox.git
synced 2026-04-25 10:05:56 +03:00
[GH-ISSUE #98] Management while updating nodes #74
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#74
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 @WaarlandIT on GitHub (Feb 28, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/98
Not a real issue as in a bug but more a feature request.
I have 2 nodes: 192.168.111.73 and 192.168.111.74 working as a cluster.
When PegaProx connects to 192.168.111.73 I can manage both but when I update that node and it goes offline, I can manage none.
What I did to resolve that is I have setup haproxy and added haproxy as the cluster to PegaProx.
haproxy config:
frontend ft_8006
bind *:8006
default_backend bk_8006
backend bk_8006
balance roundrobin
option tcp-check
server node1 192.168.111.73:8006 check
server node2 192.168.111.74:8006 check
@MrMasterbay commented on GitHub (Feb 28, 2026):
Hi @WaarlandIT ,
there is actually already a fallback in place that triggers after I think 30 sec's of of being unreachable :).
This is because incase there is server a hickup pegaprox doesn't get blocked by any firewall.
Best regards,
Nico
@WaarlandIT commented on GitHub (Feb 28, 2026):
Then there is an issue, I lost management of the cluster when updating and the node did not came back correctly.
@MrMasterbay commented on GitHub (Feb 28, 2026):
Hi @WaarlandIT ,
if you could send us your support bundle under support@pegaprox.com we would dig into it.
But this here "updating and the node did not came back correctly." do you mean here the proxmox node itself wasn't anymore reachable in pegaprox or in general?
Because if you mean in general then this would be thing for the proxmox support.
@WaarlandIT commented on GitHub (Feb 28, 2026):
I updated my nod 192.168.111.73 that is also the IP that I used to connect PegaProx to my cluster. That proxmox node came not back and PegaProx lost the connection to the cluster. I connected to 192.168.111.74 and that worked fine.
The failing node is not a PegProx issue, that was a hardware issue :-)
@MrMasterbay commented on GitHub (Mar 1, 2026):
Hi @WaarlandIT ,
just wanted to quick shoot a question if it's already resolved?
Best Regards,
Nico
@WaarlandIT commented on GitHub (Mar 2, 2026):
For me it is. thanks