mirror of
https://github.com/cvk98/Proxmox-load-balancer.git
synced 2026-04-25 12:35:52 +03:00
[GH-ISSUE #10] Master node #6
Labels
No labels
documentation
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxmox-load-balancer#6
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 @cvk98 on GitHub (Oct 25, 2022).
Original GitHub issue: https://github.com/cvk98/Proxmox-load-balancer/issues/10
python3 plb.py
INFO | START Load-balancer!
Traceback (most recent call last):
File "/root/plb.py", line 484, in
main()
File "/root/plb.py", line 454, in main
cluster = Cluster(server_url)
File "/root/plb.py", line 95, in init
self.cl_nodes: dict = self.cluster_hosts() # All cluster nodes
File "/root/plb.py", line 167, in cluster_hosts
self.master_node = rr.json()['data']['manager_status']['master_node']
KeyError: 'master_node'
proxmox cluster info if that helps:
root@prompt:~# pvecm status
Cluster information
Name: hws10
Config Version: 9
Transport: knet
Secure auth: on
Quorum information
Date: Tue Oct 25 10:36:14 2022
Quorum provider: corosync_votequorum
Nodes: 3
Node ID: 0x00001072
Ring ID: 1.7975
Quorate: Yes
Votequorum information
Expected votes: 3
Highest expected: 3
Total votes: 3
Quorum: 2
Flags: Quorate
Membership information
0x00000001 1 192.168.4.12
0x00000faa 1 192.168.4.10
0x00001072 1 192.168.4.210 (local)
Originally posted by @ubu17 in https://github.com/cvk98/Proxmox-load-balancer/issues/7#issuecomment-1290192617
@cvk98 commented on GitHub (Oct 25, 2022):
Most likely you have only_on_master: ON in the config.
But the point of this parameter is to install a balancer on all nodes using ansible. So that they don't all start working at once, you need to set "ON".
Then only the one that is running on the master node of the HA cluster will work. If you don't have HA - raise 1 instance of the balancer and set only_on_master: OFF.
@trentech commented on GitHub (Jan 11, 2023):
EDIT: Disregard - I figured it out.
@cvk98 commented on GitHub (Jan 13, 2023):
I'm glad that everything worked out for you.
Don't forget to leave a screenshot if it doesn't bother you.