Logs point to VMs not yet created

If we have a look at our /var/log/one/oned.log, we get a lot of spam…tens of rows ever second about different VMs:
Fri Jan 14 13:04:47 2022 [Z0][InM][W]: Unable to find VM, id: 4726471
Fri Jan 14 13:04:47 2022 [Z0][InM][W]: Unable to find VM, id: 7284
Fri Jan 14 13:04:47 2022 [Z0][InM][W]: Unable to find VM, id: 49322
Fri Jan 14 13:04:47 2022 [Z0][InM][W]: Unable to find VM, id: 2047511
Fri Jan 14 13:04:47 2022 [Z0][InM][W]: Unable to find VM, id: 2047512
Fri Jan 14 13:04:47 2022 [Z0][InM][W]: Unable to find VM, id: 2067002
And so forth. The odd thing is, this new instance of OpenNebula has only created 81k VMs, and thus the highest ID available is around 81k. So what are these ID numbers it is referring to?

Then let’s jump over to monitor.log:
Fri Jan 14 13:06:07 2022 [Z0][HMM][I]: Successfully monitored VM: 4127694
Fri Jan 14 13:06:07 2022 [Z0][HMM][I]: Successfully monitored VM: 4196976
Fri Jan 14 13:06:07 2022 [Z0][HMM][I]: Successfully monitored VM: 4726471
Fri Jan 14 13:06:10 2022 [Z0][HMM][I]: Successfully monitored host: 65
Fri Jan 14 13:06:11 2022 [Z0][HMM][I]: Successfully monitored VM: 53664
Fri Jan 14 13:06:11 2022 [Z0][HMM][I]: Successfully monitored VM: 75921
Fri Jan 14 13:06:11 2022 [Z0][HMM][I]: Successfully monitored VM: 75924
Fri Jan 14 13:06:11 2022 [Z0][HMM][I]: Successfully monitored VM: 78582
Fri Jan 14 13:06:11 2022 [Z0][HMM][I]: Successfully monitored VM: 80652
Fri Jan 14 13:06:11 2022 [Z0][HMM][I]: Successfully monitored VM: 80679
Again we have ID numbers that don’t match any VM currently running, but some do match:

root@one-master-202105:/var/log/one# onevm show 4726471
[one.vm.info] Error getting virtual machine [4726471].
root@one-master-202105:/var/log/one# onevm show 75921
VIRTUAL MACHINE 75921 INFORMATION
etc…

What’s going on here…where do those ID numbers come from?

Hi @tosaraja,

Is it possible that there’s some monitoring process at any hypervisor sending information to the wrong IP address? Have you reused any IP address for configuring that “new instance of OpenNebula”?

I would double check the monitoring configuration for the monitoring agents running in the hypervisors.