starred/Proxmox-load-balancer
1
0
Fork 0
mirror of https://github.com/cvk98/Proxmox-load-balancer.git synced 2026-04-25 04:25:50 +03:00
Code Issues 18 Projects Releases 8 Packages Wiki Activity

[GH-ISSUE #36] Script crashes #19

New issue
Open
opened 2026-02-26 17:46:08 +03:00 by kerem · 5 comments
kerem commented 2026-02-26 17:46:08 +03:00
Owner
Copy link

Originally created by @Niemand112233 on GitHub (Aug 6, 2024).
Original GitHub issue: https://github.com/cvk98/Proxmox-load-balancer/issues/36

I tried to use your script (awesome work btw!) first as a service, but it didn't work.

When I use it in screen directly, then I get somewhen this error:

INFO | VM Migration: 1051... 60 sec. INFO | VM Migration: 1051... 60 sec. INFO | VM Migration: 1051... 60 sec. INFO | VM Migration: 1051... 60 sec. INFO | VM Migration: 1051... 60 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. ERROR | Something went wrong during the migration. Response code200

Any ideas?

It does not matter which VM/LXC it is. But the migration did work after the script stopped.
Maybe because I am using HA as well?

Originally created by @Niemand112233 on GitHub (Aug 6, 2024). Original GitHub issue: https://github.com/cvk98/Proxmox-load-balancer/issues/36 I tried to use your script (awesome work btw!) first as a service, but it didn't work. When I use it in screen directly, then I get somewhen this error: `INFO | VM Migration: 1051... 60 sec. INFO | VM Migration: 1051... 60 sec. INFO | VM Migration: 1051... 60 sec. INFO | VM Migration: 1051... 60 sec. INFO | VM Migration: 1051... 60 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 70 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 80 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 90 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. INFO | VM Migration: 1051... 100 sec. ERROR | Something went wrong during the migration. Response code200 ` Any ideas? It does not matter which VM/LXC it is. But the migration did work after the script stopped. Maybe because I am using HA as well?
kerem commented 2026-02-26 17:46:09 +03:00
Author
Owner
Copy link

@cvk98 commented on GitHub (Aug 8, 2024):

A detailed logging level can help answer your question.

<!-- gh-comment-id:2274956932 --> @cvk98 commented on GitHub (Aug 8, 2024): A detailed logging level can help answer your question.
kerem commented 2026-02-26 17:46:09 +03:00
Author
Owner
Copy link

@Niemand112233 commented on GitHub (Aug 9, 2024):

which logging level do you want/need?

This is DEBUG level:

python3 plb.py
/usr/local/lib/python3.11/dist-packages/requests/init.py:102: RequestsDependencyWarning: urllib3 (1.26.12) or chardet (5.1.0)/charset_normalizer (2.0.12) doesn't match a supported version!
warnings.warn("urllib3 ({}) or chardet ({})/charset_normalizer ({}) doesn't match a supported "
INFO | START Load-balancer!
DEBUG | Authorization attempt...
DEBUG | Successful authentication. Response code: 200
DEBUG | init when creating a Cluster object
DEBUG | Starting Cluster.cluster_name
DEBUG | Information about the cluster name has been received. Response code: 200
DEBUG | Launching Cluster.cluster_items
DEBUG | Attempt to get information about the cluster...
DEBUG | Information about the cluster has been received. Response code: 200
DEBUG | Launching Cluster.cluster_hosts
DEBUG | Attempt to get information about the cluster HA manager...
DEBUG | Information about the cluster HA Manager has been received. Response code: 200
DEBUG | Launching Cluster.cluster_vms
DEBUG | Launching Cluster.cluster_membership
DEBUG | Launching Cluster.cluster_cpu
DEBUG | Starting cluster_load_verification
DEBUG | Starting need_to_balance_checking
INFO | Need to balance: True
DEBUG | Running temporary_dict
DEBUG | Starting calculating
INFO | Number of options = 11
DEBUG | Starting vm_migration
DEBUG | VM:139 migration from hp to hp2
INFO | Migration VM:139 (0.57 GB mem) from hp to hp2...
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 10 sec.
INFO | VM Migration: 139... 20 sec.
ERROR | Something went wrong during the migration. Response code200
NoneType: None

<!-- gh-comment-id:2277264049 --> @Niemand112233 commented on GitHub (Aug 9, 2024): which logging level do you want/need? This is DEBUG level: > python3 plb.py > /usr/local/lib/python3.11/dist-packages/requests/__init__.py:102: RequestsDependencyWarning: urllib3 (1.26.12) or chardet (5.1.0)/charset_normalizer (2.0.12) doesn't match a supported version! > warnings.warn("urllib3 ({}) or chardet ({})/charset_normalizer ({}) doesn't match a supported " > INFO | START ***Load-balancer!*** > DEBUG | Authorization attempt... > DEBUG | Successful authentication. Response code: 200 > DEBUG | init when creating a Cluster object > DEBUG | Starting Cluster.cluster_name > DEBUG | Information about the cluster name has been received. Response code: 200 > DEBUG | Launching Cluster.cluster_items > DEBUG | Attempt to get information about the cluster... > DEBUG | Information about the cluster has been received. Response code: 200 > DEBUG | Launching Cluster.cluster_hosts > DEBUG | Attempt to get information about the cluster HA manager... > DEBUG | Information about the cluster HA Manager has been received. Response code: 200 > DEBUG | Launching Cluster.cluster_vms > DEBUG | Launching Cluster.cluster_membership > DEBUG | Launching Cluster.cluster_cpu > DEBUG | Starting cluster_load_verification > DEBUG | Starting need_to_balance_checking > INFO | Need to balance: True > DEBUG | Running temporary_dict > DEBUG | Starting calculating > INFO | Number of options = 11 > DEBUG | Starting vm_migration > DEBUG | VM:139 migration from hp to hp2 > INFO | Migration VM:139 (0.57 GB mem) from hp to hp2... > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 10 sec. > INFO | VM Migration: 139... 20 sec. > ERROR | Something went wrong during the migration. Response code200 > NoneType: None >
kerem commented 2026-02-26 17:46:09 +03:00
Author
Owner
Copy link

@cvk98 commented on GitHub (Aug 9, 2024):

Does the VM migrate in Proxmox logs?

<!-- gh-comment-id:2278057697 --> @cvk98 commented on GitHub (Aug 9, 2024): Does the VM migrate in Proxmox logs?
kerem commented 2026-02-26 17:46:09 +03:00
Author
Owner
Copy link

@Niemand112233 commented on GitHub (Aug 12, 2024):

As I said:

But the migration did work

Maybe because I am using only LXC?

<!-- gh-comment-id:2284324253 --> @Niemand112233 commented on GitHub (Aug 12, 2024): As I said: > But the migration did work Maybe because I am using only LXC?
kerem commented 2026-02-26 17:46:09 +03:00
Author
Owner
Copy link

@cvk98 commented on GitHub (Aug 13, 2024):

Perhaps you are right. I have not tested such a case.

<!-- gh-comment-id:2285466660 --> @cvk98 commented on GitHub (Aug 13, 2024): Perhaps you are right. I have not tested such a case.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v.0.6.4-betta
v.0.6.3-betta
v.0.6.2-betta
v.0.6.1-Cylindric
v.0.6.0-Cylindric
0.5.2-betta
0.5.1-betta
v0.5.0-betta
v0.4.2-betta
v0.4.1-betta
v0.4.0-betta
v0.3.0-betta
Labels
Clear labels   
documentation

   
pull-request

Mirrored from GitHub Pull Request

No labels
documentation
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxmox-load-balancer#19
No description provided.