Sorry for my bad english (sad)

We are evaluating open-audit (community-version on a vmWare iinfrastructure. We use the VM cloning feature very often...

When we use the "Discovy device" with a "device IP" as a subnet format (ie, by example), we don't see all the relative devices. In "Debug mode", we have the following logs :

First device

  ==> It's OK (smile)

But, next, a second device is processing, and we see :

So, the script update the device with System ID 1304 (instead of inserting it in DB), because this device "HIT on dbus-identifer" (sad)

As far that we know, it's not recomended to change this dbus-identifier (see https://dbus.freedesktop.org/doc/dbus-uuidgen.1.html) :

If you try to change an existing machine-id on a running system, it will probably result in bad things happening

So, is it possible to deactivate this matching on dbus identifier somewhere ? In the config page, we don't have seen anything about that...

Thank you...


    CommentAdd your comment...

    1 answer


      Hello Padou,

      We have seen the DBUS_ID issue for VMware Clones with the latest release.  You have two options, you can either simply change the way Open Audit matches devices or you could upgrade versions.  It is discussed in this Wiki Article:

      Information about how Open-AudIT processes and stores data

      Particularly in this section:

      Information about how Open-AudIT processes and stores data#AudITprocessesandstoresdata-Howdowedeterminedeviceuniqueness?

      Change it over to matching MAC and IP address if that suits your needs


      The DBUS_ID matching was a recent version introduction which we changed away from again for the exact reason of cloning in VMWare.  So if you were to upgrade past you will also avoid the issue.

      Hope this helps.

      Happy Auditing.


      1. padouciel

        Hi Nick

        Thanks for your quick answer and for pointing me in the right ressource (wink)



      CommentAdd your comment...