Re: [External] Re: ovirt metrics - vm dashboard not working
by Jayme
I just get a blank output from that command. I'm running oVirt Node NG
4.3.3.1 hosts
On Mon, Jun 3, 2019 at 3:48 PM Morris, Roy <roy.morris(a)ventura.org> wrote:
> Jayme,
>
>
>
> Can you run the following command and report back with the results?
>
>
>
> #systemctl status selinux* -l
>
>
>
> Best regards,
>
> Roy Morris
>
> GSA Virtualization Systems Analyst
>
> County of Ventura
>
> (805) 654-3625
>
> (805) 603-9403
>
> [image: cid:7c03dd9d67a9cfb78447b56087323d91a66d7c29.camel@ventura.org]
>
>
>
> *From:* Jayme <jaymef(a)gmail.com>
> *Sent:* Monday, June 3, 2019 11:40 AM
> *To:* users <users(a)ovirt.org>
> *Subject:* [External] [ovirt-users] Re: ovirt metrics - vm dashboard not
> working
>
>
>
> *CAUTION: *This email contains links. If it looks suspicious or is not
> expected, DO NOT click and immediately forward to Spam.Manager(a)ventura.org
> .
>
>
>
>
> I'm seeing this in the journal for collectd on all of my hosts:
>
>
>
> collectd[18380]: write_syslog plugin: error with wr_send_message
> collectd[18380]: write_syslog plugin: Connecting to localhost:44514
> failed. The last error was: Connection refused
> collectd[18380]: write_syslog plugin: wr_callback_init failed.
> collectd[18380]: write_syslog plugin: error with wr_send_message
> collectd[18380]: write_syslog plugin: send failed with status -1
> (Connection reset by peer)
> collectd[18380]: write_syslog plugin: error with wr_send_message
> collectd[18380]: write_syslog plugin: send failed with status -1
> (Connection reset by peer)
>
>
>
> collectd and rsyslog are running, I tried restarting both. I can also
> telnet to port 44514 on localhost and it's responding.
>
>
>
>
>
> On Mon, Jun 3, 2019 at 3:12 PM Jayme <jaymef(a)gmail.com> wrote:
>
> I finally managed to get oVirt metrics store running. I loaded sample
> dashboards, searches and visualizations in to Kibana from
> /etc/ovirt-engine-metrics/dashboards-examples. When importing searches and
> visualizations there are warnings about missing index patterns.
>
>
>
> It appears that the "VM" dashboard is completely broken, no stats are
> showing on it at all including simple stats such as running VM count.
>
>
>
> The other two dashboards Hosts and System are working and showing all
> stats (sans VM count on the host dashboard).
>
>
>
> I believe I have a cash here of either missing indexes or potentially an
> issue with the example dashboards? I can see that collectd is running on
> all hosts and has the virt plugin loaded.
>
>
>
> What part of the config is responsible for suppling the VM
> information/indexes?
>
>
2 years, 11 months
ovirt metrics - vm dashboard not working
by Jayme
I finally managed to get oVirt metrics store running. I loaded sample
dashboards, searches and visualizations in to Kibana from
/etc/ovirt-engine-metrics/dashboards-examples. When importing searches and
visualizations there are warnings about missing index patterns.
It appears that the "VM" dashboard is completely broken, no stats are
showing on it at all including simple stats such as running VM count.
The other two dashboards Hosts and System are working and showing all stats
(sans VM count on the host dashboard).
I believe I have a cash here of either missing indexes or potentially an
issue with the example dashboards? I can see that collectd is running on
all hosts and has the virt plugin loaded.
What part of the config is responsible for suppling the VM
information/indexes?
2 years, 11 months
Re: option to remove a specific VM greyed out
by Strahil
Maybe, there is a deletion protection?
Just go to edit and uncheck it.
Best Regards,
Strahil NikolovOn Jun 3, 2019 17:46, Jayme <jaymef(a)gmail.com> wrote:
>
> Running latest stable 4.3. I have one particular VM that is shutdown but options for removal are greyed out in the admin gui. I tried starting it and shutting it down again but still the options are not-selectable. However, they are for other VMs.
>
> Any idea what is different about this VM that is preventing removal from the GUI?
>
>
2 years, 11 months
option to remove a specific VM greyed out
by Jayme
Running latest stable 4.3. I have one particular VM that is shutdown but
options for removal are greyed out in the admin gui. I tried starting it
and shutting it down again but still the options are not-selectable.
However, they are for other VMs.
Any idea what is different about this VM that is preventing removal from
the GUI?
2 years, 11 months
Re: Gluster Deployment Failed - No Medium Found
by Strahil
Aanother option - you do not have blacklist section in multipath (requires rebuild of initramfs + reboot).
Best Regards,
Strahil NikolovOn Jun 3, 2019 14:49, Sachidananda URS <surs(a)redhat.com> wrote:
>
> Hi Stephen,
>
>
> On Mon, Jun 3, 2019 at 3:57 PM <smcintosh(a)tradeprint.co.uk> wrote:
>>
>> Good Morning,
>>
>> I'm completely new to this and I'm testing setting up a Gluster environment with Ovirt. However, my deployment keeps fails and I don't understand what it means. Any assistance would be much appreciated. Please see error below...
>>
>> Error Message
>>
>> TASK [gluster.infra/roles/backend_setup : Create volume groups] ****************
>> failed: [ov1.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5}
>
>
> One of the reasons for this is, the device could be having an existing partition table information.
>
> Can you please run the command:
>
> wipefs -a /dev/sdb
>
> On all the nodes and try again?
>
> -sachi
>
2 years, 11 months
Westmere CPU Family
by Vrgotic, Marko
Dear oVirt,
For a strange reason I am convinced I have read somewhere that with 4.3 oVirt, the CPU family Westmere will not be supported any longer.
Still, I see it in dropdown list after upgradingfrom 4.2 to 4.3, also after installing fresh 4.3.
I also see it in oVirt documentation.
Can someone tell me if its actually supported and if its going to be “discontinued” in 4.4 maybe?
Thank you.
Marko Vrgotic
ActiveVideo
2 years, 11 months
Gluster Deployment Failed - No Medium Found
by smcintosh＠tradeprint.co.uk
Good Morning,
I'm completely new to this and I'm testing setting up a Gluster environment with Ovirt. However, my deployment keeps fails and I don't understand what it means. Any assistance would be much appreciated. Please see error below...
Error Message
TASK [gluster.infra/roles/backend_setup : Create volume groups] ****************
failed: [ov1.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5}
failed: [ov3.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5}
failed: [ov2.test1.lan] (item={u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}) => {"changed": false, "err": " /dev/sdb: open failed: No medium found\n Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5}
NO MORE HOSTS LEFT *************************************************************
NO MORE HOSTS LEFT *************************************************************
to retry, use: --limit @/usr/share/cockpit/ovirt-dashboard/ansible/hc_wizard.retry
PLAY RECAP *********************************************************************
ov1.test1.lan : ok=10 changed=0 unreachable=0 failed=1
ov2.test1.lan : ok=10 changed=0 unreachable=0 failed=1
ov3.test1.lan : ok=10 changed=0 unreachable=0 failed=1
Any assistance would be much appreciated.
Regards
Stephen
2 years, 11 months
Nvme over fabric array support through OVirt MANAGED_BLOCK_STORAGE Domain
by amit1.kumar＠intel.com
for an NVMe over fabric storage array that supports Cinder backend plugin, is it possible to use MANAGED_BLOCK_STORAGE domain to configure Virtual disk? in this case, is it required to have a single Virtual disk accessible from all the VDSM hosts (within the cluster) to support VM migration?
Thanks,
Amit
2 years, 11 months
Re: libvirt memory leak?
by Strahil
Hi Alex,
As a sys admin - I would rexommend to thoroughly check the 'journalctl' if it is permanent.
If not - check libvirt logs (/var/log/something/qemu/VM-name.log -> this is based on memory).
Also, if you run out of memory - the OOM killer kicked in and it will be reporting details kn /var/log/messages.
Best Regards,
Strahil NikolovOn Jun 2, 2019 06:37, Alex McWhirter <alex(a)triadic.us> wrote:
>
> After moving from 4.2 -> 4.3 libvirtd seems to be leaking memory, it
> recently crashed a host by eating 123GB of RAM. Seems to follow one
> specific VM around, this is the only VM i have created since 4.3, the
> others were all made in 4.2 them upgraded to 4.3
>
> What logs would be applicable?
>
> Libvirt 4.5.0
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/SB75R63BMUE...
2 years, 12 months
