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

Manage VMs slow/not working #1186

Open
Crunchn opened this issue Aug 20, 2016 · 2 comments
Open

Manage VMs slow/not working #1186

Crunchn opened this issue Aug 20, 2016 · 2 comments

Comments

@Crunchn
Copy link

Crunchn commented Aug 20, 2016

When attempting to manage my existing VMs with Archipel, the following happens:

  • High CPU usage on browser
  • Login gets kicked off forcing to log back in
  • Hypervisor now causes high CPU usage on browser when I click on the Virtual Machines section of the hypervisor
  • This slowness does not stop until I remove the new VMs and the hypervisor from ejabberd and restart the agent.

While it appears that no errors are occurring and ejabberd creates the XMPP profiles for the VMs properly and Archipel sees my existing VMs, this happens whenever I attempt to manage a VM with Archipel, this includes making a new one.

I am currently running Archipel on an ArchLinux host with an existing KVM/QEMU hypervisor that I manage through virt-manager.

@Ulrar
Copy link

Ulrar commented Mar 4, 2017

I'm running into the same problem, did you ever find a workaround ?
I've just installed Archipel, managed to add my hypervisor, and since I tried to create a VM from Archipel that menu just keeps crashing my browser tabs, over and over. Tried both firefox and chrome, just in case, but doesn't look like it's usable at all :(

@Ulrar
Copy link

Ulrar commented Mar 4, 2017

Okay, I figured it out. For some reason my /var/lib/archipel/avatars was empty, and it looks like that makes the vCard creation process fail. Apparently no-one ever planned for that, the web interface goes crazy as soon as there is a "failed" VM. To solve that I killed archipel and the central agent, unregistered the VM from ejabberd and downloaded the missing jpegs. Then I re-started archipel and the central agent, and they re-created the user with the vCard correctly, and everything started working.

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