Open Niemand112233 opened 3 months ago
A detailed logging level can help answer your question.
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
Does the VM migrate in Proxmox logs?
As I said:
But the migration did work
Maybe because I am using only LXC?
Perhaps you are right. I have not tested such a case.
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?