Hi,
I might be going into a wrong direction here, but can you please provide
the following information:
(1)
Output of "uname -a"
(2)
Output of "cat /proc/meminfo" when the crash happens
Also please provide output of "free -m" for faster/better overview
(3)
Output of "dmesg" after the crash happened
(4)
If possible, somehow provide how much memory was consumed by the Icinga2
processes when they died
32 Bit systems have a special approach regarding memory management (low
mem, high mem).
So when you provide the requested information, we can double-check that
part (I don't think this is the issue here, but just to make sure..).
Another question:
Is there a reason why you go with 32bit machines? I am just curious.
Best regards
Valentin
On 30.06.2017 17:34, Antony Stone wrote:
Hi.
I've been using Icinga2 for several months now, and I've got quite a few
servers configured in a hierarchy.
This week I've just added a new machine for monitoring a customer's network,
and Icinga keeps on falling over saying "cannot allocate memory".
The machine is a Virtual Server with 4Gbytes of RAM, and at the time icinga
falls over, "free" tells me:
Mem: 4194304
Used: 345328
Free: 3848976
So, I certainly do not believe Icinga has run out of RAM.
The machine is an identical specification VM to one that I've been using since
October 22nd as my Master instance, with all the configuration files on it.
Icinga2 has been running perfectly happily on that since I set it up.
Both machines are running Debian 7 "wheezy", 32 bit, and I've installed
Icinga2 from the debmon repository.
Version: 2.6.3-1~debmon70+1
The server with the problem is running a few standard "local" checks on
itself, and is also running 13 plugin checks over SSH to 18 other servers
(which I think is not a big workload...)
When Icinga shuts down claiming it can't allocate memory, it generates two
reports in /var/log/icinga2/crash; I've attached the latest examples of these
for info. The same sort of thing also goes into /var/log/icinga2/icinga2.log
Googling for the error message, I've found https://dev.icinga.com/issues/10655
and https://dev.icinga.com/issues/10839 however those seem to indicate that
the problem was fixed in Icinga 2.4.2?
Is there any further information I can provide to help pin down what's going
on here?
Can anyone suggest how to fix the problem? It seems strange that I have it on
one machine but not another, both identical spec, identical O/S install, and
identical Icinga2 versions...
Thanks,
Antony.
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
--
Valentin Höbel
Senior Consultant IT Infrastructure
mobil 0711-95337077
open*i GmbH
Talstraße 41 70188 Stuttgart Germany
Geschäftsführer Tilo Mey
Amtsgericht Stuttgart, HRB 729287, Ust-IdNr DE264295269
Volksbank Stuttgart EG, BIC VOBADESS, IBAN DE75600901000340001003
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
