Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4883

Same VM added multiple times in VM list

Details

    • Help
    • Resolution: Fixed
    • Trivial
    • None
    • Professional Edition
    • Poller
    • None

    Description

      Hello, the list of VMs on VMware ESXi shows the same VMs multiple times. This doesn’t happen on all ESX servers, but I haven’t been able to determine if it only occurs on certain versions of ESX. Is the problem exclusively on the ESX side, or could it be coming from OBSERVIUM? If so, is there a way to fix the issue? Thank you in advance.

      Attachments

        Activity

          [OBS-4883] Same VM added multiple times in VM list

          Ok, I think it is definitely fixed now.

          There was a query fetching the current VM from the database to compare, but it was using a query which was too narrow, returning values from other VMs with the same UUID.

          It should work properly now!

          adama Adam Armstrong added a comment - Ok, I think it is definitely fixed now. There was a query fetching the current VM from the database to compare, but it was using a query which was too narrow, returning values from other VMs with the same UUID. It should work properly now!

          Hi, did you update observium to latest rolling (not stable)?

          https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains

          landy Mike Stupalov added a comment - Hi, did you update observium to latest rolling (not stable)? https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains

          It shouldn't cause issues at that size, but it's still broken!

          Are you able to give SSH/HTTP access to this system? It's probably a simple issue to fix, but I don't have any vmware to test.

          Thanks,

          adam.

          adama Adam Armstrong added a comment - It shouldn't cause issues at that size, but it's still broken! Are you able to give SSH/HTTP access to this system? It's probably a simple issue to fix, but I don't have any vmware to test. Thanks, adam.

          Hello. The list of VMs keeps growing. I’m at 11,502 VMs, while there are barely 200. I’m afraid this might eventually cause issues with OBSERVIUM. How can I delete all of this in the meantime while we look for a solution? Thanks in advance.

          InovacomTS Thierry Sauce added a comment - Hello. The list of VMs keeps growing. I’m at 11,502 VMs, while there are barely 200. I’m afraid this might eventually cause issues with OBSERVIUM. How can I delete all of this in the meantime while we look for a solution? Thanks in advance.

          Hello. Would you be so kind as to help me solve this problem? Thank you in advance. Thierry

          InovacomTS Thierry Sauce added a comment - Hello. Would you be so kind as to help me solve this problem? Thank you in advance. Thierry

          Hello Adam. Did you see my last post ?

          Can you help me solve this problem?

          Thank you

           

          InovacomTS Thierry Sauce added a comment - Hello Adam. Did you see my last post ? Can you help me solve this problem? Thank you  

          Hello.

          Many different versions are affected by the issue. Here is a non-exhaustive list. Moreover, it is not systematic. I mean that for the same version of VMware, some servers have a correct list of VMs while others have a list with duplicated VMs, sometimes with the same VM appearing more than 20 times.

          7.0.2 build-17867351

          6.7.0 build-13006603

          6.7.0 build-16773714

          5.5.0 build 2403361

           

          InovacomTS Thierry Sauce added a comment - Hello. Many different versions are affected by the issue. Here is a non-exhaustive list. Moreover, it is not systematic. I mean that for the same version of VMware, some servers have a correct list of VMs while others have a list with duplicated VMs, sometimes with the same VM appearing more than 20 times. 7.0.2 build-17867351 6.7.0 build-13006603 6.7.0 build-16773714 5.5.0 build 2403361  

          You need to provide more information. What version vmware?

          adama Adam Armstrong added a comment - You need to provide more information. What version vmware?

          General questions and device support can be discussed in our Discord channel, click here to join.


          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            adama Adam Armstrong
            InovacomTS Thierry Sauce
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: