BPI - Deadpool Spontaneously Put into BPI

[gregbeyer]

Looked at my BPI this morning, found these error messages. I have never had hg_host_deadpool in any BPI, ever. Why would anyone put deadpool in a BPI for crying out loud? Deadpool was just stuffed into the bpi configuration file by Nagios spontaneously.

I do not have a hg-storage_inventory BPI. It is also just spontaneously imagined by Nagios. I've checked the audit log. No record of either of these events. bpi.log is empty. grep of all of the bpi .conf files in /usr/local/nagiosxi/etc/components/bpi finds no deadpool.

I've told my organization that BPI is the place to go check the overall health of our HPC clusters. They are met with this. It's like XI has had an A.I. hallucination. And no record of it happening in bpi.log or nagios.log. This bizarre behavior really hurts XI credibility for my org. I am just floored.

BPI-deadpool.png

I

[danderson]

My guess is that you had the deadpool host group added when some items were moved to the deadpool. These get added to the "host-deadpool" hostgroup on Stage 1. I'm guessing you also set up a hostgroup called "storage-inventory". Then I'm guessing what happened was either you or someone else hit the "Sync Hostgroups" button which pulls from the existing hostgroups and will append "hg_" to the name. This is why you are seeing "hg_host-deadpool" and "hg_service-inventory" because they were created from hostgroups "host-deadpool" and "service-inventory".

[danderson]

Which is an unexpected interaction to say the least