On Friday 30 June 2017 at 19:16:14, Antony Stone wrote:
> On Friday 30 June 2017 at 18:26:43, Valentin Höbel wrote:
> > Hi,
> >
> > I might be going into a wrong direction here, but can you please provide
> > the following information:
> >
> > (1)
> > Output of "uname -a"
>
> Linux red.ac.ted 3.2.41-042stab120.20 #1 SMP Fri Mar 10 16:52:50 MSK 2017
> i686 GNU/Linux
>
> > (2)
> > Output of "cat /proc/meminfo" when the crash happens
>
> Okay, will wait for another occurrence and then post the output.
Finally had another one - had to wait a few hours this time...
Crash report attached again.
# cat /proc/meminfo
MemTotal: 4194304 kB
MemFree: 3790444 kB
Cached: 270952 kB
Buffers: 0 kB
Active: 253436 kB
Inactive: 118100 kB
Active(anon): 45384 kB
Inactive(anon): 55200 kB
Active(file): 208052 kB
Inactive(file): 62900 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 16 kB
Writeback: 0 kB
AnonPages: 100584 kB
Shmem: 4036 kB
Slab: 28244 kB
SReclaimable: 18104 kB
SUnreclaim: 10140 kB
> > Also please provide output of "free -m" for faster/better overview
# free -m
total used free shared buffers cached
Mem: 4096 396 3699 0 0 264
-/+ buffers/cache: 132 3963
Swap: 0 0 0
> > (3)
> > Output of "dmesg" after the crash happened
>
> Hm, that's odd - "dmesg" outputs nothing - on either of these VMs.
>
> > (4)
> > If possible, somehow provide how much memory was consumed by the Icinga2
> > processes when they died
I have no idea how to determine that.
> That's hard to say, but given that 400Mbytes is being used in total (out of
> 4Gbytes available), I can certainly say "less than 10% of available, and
> less than 400Gbytes" for Icinga2.
>
> > 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..).
>
> Okay. Please remember I have another Icinga2 instance running perfectly
> okay on a different but identical server, so if there's anything useful I
> can compare, that's entirely possible.
>
> > Another question:
> > Is there a reason why you go with 32bit machines? I am just curious.
>
> That's what the VM hoster (strato.de) provides...
>
>
> Antony.
--
Behind the counter a boy with a shaven head stared vacantly into space,
a dozen spikes of microsoft protruding from the socket behind his ear.
- William Gibson, Neuromancer (1984)
Please reply to the list;
please *don't* CC me.
Caught unhandled exception.
Current time: 2017-07-01 00:02:33 +0200
Application information:
Application version: r2.6.3-1
Installation root: /usr
Sysconf directory: /etc
Run directory: /run
Local state directory: /var
Package data directory: /usr/share/icinga2
State path: /var/lib/icinga2/icinga2.state
Modified attributes path: /var/lib/icinga2/modified-attributes.conf
Objects path: /var/cache/icinga2/icinga2.debug
Vars path: /var/cache/icinga2/icinga2.vars
PID path: /run/icinga2/icinga2.pid
System information:
Platform: Debian GNU/Linux
Platform version: 7 (wheezy)
Kernel: Unknown
Kernel version: Unknown
Architecture: Unknown
Build information:
Compiler: GNU 4.7.2
Build host: moe
Error: Function call 'fork' failed with error code 12, 'Cannot allocate memory'
***
* This would indicate a runtime problem or configuration error. If you believe
this is a bug in Icinga 2
* please submit a bug report at https://github.com/Icinga/icinga2 and include
this stack trace as well as any other
* information that might be useful in order to reproduce this problem.
***
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
