mirror of
https://github.com/retspen/webvirtcloud.git
synced 2026-04-25 15:35:57 +03:00
[GH-ISSUE #20] Problem connecting via local socket #13
Labels
No labels
bug
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/webvirtcloud#13
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 @ghost on GitHub (Jun 8, 2015).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/20
I've installed webvirtcloud onto a machine as per the instructions in the readme. The machine already has a few KVM machines set up, so I'm able to run something like this without issue:
However, after adding a local socket entry on the computes tab of webvirtcloud, I get the following on the instances tab:
I've tried adding both my local and the www-data user accounts to the libvirtd group but I still get the same error.
Any ideas?
@retspen commented on GitHub (Jun 8, 2015):
@ghost commented on GitHub (Jun 8, 2015):
Thanks. Tried that but still getting the same error message.
I'm able to use TCP at the moment, so this isn't a huge deal. Would still be nice to solve though.
@retspen commented on GitHub (Jun 8, 2015):
After that need restart service nginx
@ghost commented on GitHub (Jun 8, 2015):
Refreshed the page but still getting the same error, even after clearing the cache.
@retspen commented on GitHub (Jun 8, 2015):
Can you add libvirtd group to www-data and then restart service nginx?
@ghost commented on GitHub (Jun 8, 2015):
No change unfortunately
@retspen commented on GitHub (Jun 8, 2015):
Can you reboot your server? Now I tested the Issue and my configuration work perfectly.
@ghost commented on GitHub (Jun 8, 2015):
Not able to right now but will give it a try later on and report back. Thanks for the help :)
@ghost commented on GitHub (Jun 11, 2015):
Apologies for the delay @retspen.
I rebooted as you suggested and it started working. Not quite sure what was wrong, but since things are working now I'll close this up.