Ad Widget

Collapse

Vmware template import

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dedisoft
    Junior Member
    • Dec 2013
    • 18

    #1

    Vmware template import

    Hi,

    I've migrated to Zabbix 5.0 LTS and updating my templates using Github repository.

    I've imported the template for VMware from https://git.zabbix.com/projects/ZBX/...XNEXT-6275-5.0

    But during import, I have this error:
    • pg_query(): Query failed: ERREUR: une valeur NULL viole la contrainte NOT NULL de la colonne « description »
    • DETAIL: La ligne en échec contient (10648, null, {#HV.UUID}, 0, 0, , 0, 0, 0, -1, 2, , , 0, 0, 0, 0, null, 0, 0, 0, 0, 0, , , 0, 0, 0, , {#HV.NAME}, 2, null, null, 1, 1, , , , , , 1, 0). [conf.import.php:89 → CApiWrapper->__call() → CFrontendApiWrapper->callMethod() → CApiWrapper->callMethod() → CFrontendApiWrapper->callClientMethod() → CLocalApiClient->callMethod() → CConfiguration->import() → CConfigurationImport->import() → CConfigurationImport->processDiscoveryRules() → CHostPrototype->create() → CHostPrototype->createReal() → DB::insert() → DBexecute() → pg_query() in include/db.inc.php:348]
    • Error in query [INSERT INTO hosts (host,name,status,discover,flags,hostid) VALUES ('{#HV.UUID}','{#HV.NAME}','0','0','2','10648')] [ERREUR: une valeur NULL viole la contrainte NOT NULL de la colonne « description »
    • DETAIL: La ligne en échec contient (10648, null, {#HV.UUID}, 0, 0, , 0, 0, 0, -1, 2, , , 0, 0, 0, 0, null, 0, 0, 0, 0, 0, , , 0, 0, 0, , {#HV.NAME}, 2, null, null, 1, 1, , , , , , 1, 0).]
    • L'exécution de l'instruction SQL a échoué"INSERT INTO hosts (host,name,status,discover,flags,hostid) VALUES ('{#HV.UUID}','{#HV.NAME}','0','0','2','10648')".

    I've updated many other templates without any issue.

    I'm using PostgreSQL.

    Can you help me ?

    Thanks

    Regards,
  • pinkysri
    Junior Member
    • Nov 2020
    • 1

    #2
    Starting with Zabbix version 2.4.4 the collected data is divided into 2 types: VMware configuration data and VMware performance counter data. Both types are collected independently by vmware collectors. Because of this it is recommended to enable more collectors than the monitored VMware services. Otherwise retrieval of VMware performance counter statistics might be delayed by the retrieval of VMware configuration data (which takes a while for large installations). power director pour pc
    Last edited by pinkysri; 26-11-2020, 04:51.

    Comment

    • Tuor
      Junior Member
      • Feb 2015
      • 16

      #3
      I do have the same problem.

      Comment

      • Tuor
        Junior Member
        • Feb 2015
        • 16

        #4
        edit: wrong thread
        Last edited by Tuor; 09-03-2022, 15:28.

        Comment

        • Tuor
          Junior Member
          • Feb 2015
          • 16

          #5
          For me, deleting the old templates and then importing fixed the issue. That is not optimal, because I lost old Monitoring data.

          Comment

          • Tuor
            Junior Member
            • Feb 2015
            • 16

            #6
            I found the problem:
            This problem only occurs, if there are any hosts assigned to the official VMware template. If you first unlink and clear all hosts (you loos data!), then you will be able to import the new template or change the the existing template. I tried to modify the groups, a VMware hypervisor gets put into when it is discovered, and this didn't work for the same reason. Had to clone the template, make my changes and assign the vCenters to the cloned template, while cleaning all data from the old version the template. Maybe it is due to using crompression with TimescaleDB?

            Comment

            • HubertJ
              Junior Member
              • Mar 2022
              • 5

              #7
              Hello guys, did a new template working fine for you? I successfuly upgraded to 6.0.2 and template import w/o problem, also autodiscover found all of my vCenter hosts and vm's. Only issue is that some of items are unsuported for vm's "Unknown virtual machine uuid" for esx hosts "Unknown hypervisor uuid"

              However i found that in this template items are duplicated like:

              VMware Hypervisor name - vmware.vm.hv.name[{$VMWARE.URL},{$VMWARE.VM.UUID}] - no data Unknown hypervisor uuid
              Hypervisor name - vmware.vm.hv.name[{$URL},{HOST.HOST}] - data collected successfuly where in fact discovered host name is hypervisor UUID

              Similar sytuation is with discovered vm's, is that how it should be working? like VMWARE.VM.UUID items are for standalone host and HOST.HOST for vcenter enviroment?
              I am just a bit confused if my configuration working as intend.

              Hubert
              Last edited by HubertJ; 29-03-2022, 13:00.

              Comment

              Working...