Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script crashes #36

Open
Niemand112233 opened this issue Aug 6, 2024 · 5 comments
Open

Script crashes #36

Niemand112233 opened this issue Aug 6, 2024 · 5 comments

Comments

@Niemand112233
Copy link

Niemand112233 commented Aug 6, 2024

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?

@cvk98
Copy link
Owner

cvk98 commented Aug 8, 2024

A detailed logging level can help answer your question.

@Niemand112233
Copy link
Author

Niemand112233 commented 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

@cvk98
Copy link
Owner

cvk98 commented Aug 9, 2024

Does the VM migrate in Proxmox logs?

@Niemand112233
Copy link
Author

As I said:

But the migration did work

Maybe because I am using only LXC?

@cvk98
Copy link
Owner

cvk98 commented Aug 13, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants