1 answer
- 210
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:
Change it over to matching MAC and IP address if that suits your needs
OR
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 1.12.8.1 you will also avoid the issue.
Hope this helps.
Happy Auditing.
Nick
- padouciel
Hi Nick
Thanks for your quick answer and for pointing me in the right ressource
Regards
Padou
Add your comment...
Hello,
Sorry for my bad english
We are evaluating open-audit (community-version 1.12.8.1) 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 192.16.1.1-10, by example), we don't see all the relative devices. In "Debug mode", we have the following logs :
First device
==> It's OK
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"
As far that we know, it's not recomended to change this dbus-identifier (see https://dbus.freedesktop.org/doc/dbus-uuidgen.1.html) :
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...
Regards
Padou