Nagios Support Forum

I attempted to add two large clusters to BPI, a 1,400 and a 480 node cluster. BPI is now clocking (spinner progress thingie) for a week. How do I kill the BPI process so that I can try again?

Smaller clusters and groups of nodes that I previously added, I can't even view anymore, due to the clocking. Nothing loads.

I stopped httpd, mysqld, nagios and php-fpm, closed browser. Started all, opened browser, cleared cache -- still clocking.

grep bpi /usr/local/nagiosxi/var/cmdsubsys.log:

Wed, 18 Sep 2024 14:33:05 -0400 CMDLINE=php /usr/local/nagiosxi/html/includes/components/nagiosbpi/api_tool.php --cmd=syncall
PHP Fatal error: Allowed memory size of 4294967296 bytes exhausted (tried to allocate 262144 bytes) in /usr/local/nagiosxi/html/includes/components/nagiosbpi/classes/BpGroup_class.php on line 0

/etc/php.ini : memory_limit = 4096M 4096 isn't enough for BPI?

Most likely the spinner is spinnning waiting for a response that isn't coming (because of the out of memory problem you noted in the logs. I imagine the data structures for that size of a cluster could get rather large; 4GB could potentially not be enough. Without recommending using a support ticket, my initial recommendation is to increase the memory limit. I'm not entirely certain how high to have you set it at, so you'll have to experiment with it. Start with 8GB and see where you get.

No Joy with 8GB. I've rebooted the server.

After reboot spinner is still clocking! 16GB no joy.

Unfortunately Greg, for this one, since it seems as though the nodes are configured, I'm thinking your best bet might be to open up a support ticket

Figured out how to kill it. It would stink if I had established BPI, with history that I was loosing, but it worked for me. Rename /usr/local/nagiosxi/etc/components/bpi.conf to bpi.conf.junk. Then cycle php-fpm and nagios. Then start all over again with BPI. There should be a better way, but . . .