Hi, I’ve recently installed Icinga2 and when I select “Check Now” against any check, it appears to run, but I get the following error message:
Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes) in /usr/share/icingaweb2/modules/icingadb/library/Icingadb/Command/Transport/CommandTransport.php on line 38
Fatal error: Uncaught ErrorException: ob_end_clean(): Failed to delete buffer. No buffer to delete in /usr/share/php/Icinga/Application/Web.php:460 Stack trace: #0 [internal function]: Icinga\Application\ApplicationBootstrap->Icinga\Application{closure}() #1 /usr/share/php/Icinga/Application/Web.php(460): ob_end_clean() #2 [internal function]: Icinga\Application\Web->Icinga\Application{closure}() #3 {main} thrown in /usr/share/php/Icinga/Application/Web.php on line 460
Icinga Web 2 version:
2.12.5
Used modules and their versions (System - About)
Loaded Modules
|director||1.11.5|
|doc||2.12.5|
|icingadb||1.2.2|
|incubator||0.23.0|
|migrate||2.12.5|
|translation||2.12.5|
Web browser used
Firefox Latest
Icinga 2 version used (icinga2 --version)
r2.15.0-1
PHP version used (php --version)
PHP 8.3.6
Server operating system and version
Ubuntu 24.04.3 LTS
Does this happen on any single check? I mean, you choose a single item and click “Check Now”?
Since you installed this only recently, I assume you also installed and configured the webserver as well just recently. It may be the case that the webserver strips away some of the request url parameters used when issuing the command, causing the backend to run all checks.
If you don’t spot anything suspicious in your webserver configuration, you can post it here, someone might be able to help out with it.
Use the browser’s DevTools Network tab and watch for a check-now? line after pressing the link.
Note the request URL and compare it to the request in your Apache log.
Maybe you can also get php-fpm to log the next layer and/or get the icingaweb2 to log the received request.