Hi.
Does anyone have any further ideas on what can be causing this, or how I can
get more information about how to fix it?
I'm still getting crashes with the error message shown in the subject line.
Sometimes they occur within a few minutes of the previous one; or the system
can keep going for several hours without a problem.
Any ideas are most welcome.
(Oh, and by the way, the suggestion of adding some swap space, despite the
machine already having 4Gbytes RAM and only using 10% of it, turns out not to
be possible, because the hosting provider doesn't allow swap to be turned
on...)
Thanks,
Antony.
On Saturday 01 July 2017 at 13:56:28, Antony Stone wrote:
> On Saturday 01 July 2017 at 10:34:28, Antony Stone wrote:
> > On Saturday 01 July 2017 at 01:32:34, Neil Katin wrote:
> > > Alternately: run 'sar -r 10' (sar is in the sysstat package, -r
> > > reports on memory usage) capturing the output to a file. If you see
> > > committed memory (%commit) usage growing towards 100%, and then
> > > freeing up after icinga dies then you have a reasonable diagnosis.
> >
> > I'll log to a file and wait...
>
> Crash report attached - time of failure 13:42:11
>
> sar report from 13:30 onwards also attached.
>
> I see no indication of all 4Gbytes getting used up.
>
> The only thing I would mention is that this crash occurred 1 minute 6
> seconds after I performed an "icinga2 reload" on the master server.
>
>
> However, the crash I got last night, timed at 00:02:33 was ~20 minutes
> after the previous reload (23:43:10 - I have timestamps on my bash
> history).
>
> Any further ideas please, people?
>
>
> Antony.
--
Users don't know what they want until they see what they get.
Please reply to the list;
please *don't* CC me.
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
