Updating this in response to the suggestions/questions posed on the list (sorry
I'm not sure how to tag this onto their posts)
Russel Van Tassell wrote
What type of system are you running this on, now? Anything of-note in
/etc/security/limits.conf (or similar) by chance? Any chance ulimit is being
set at the profile level? Anything interesting in ulimit -u by chance? (only
things off the top of my head at the moment - but, I should also be sleeping
about now) Hope that somehow helps... RussellAnswers:It's running on RHEL 6.0
The /etc/security/limits.conf is as follows
icinga soft nofile 1000000
icinga hard nofile 1000000
nagios soft nofile 1000000
nagios hard nofile 1000000
icinga soft nproc 1000000
icinga hard nproc 1000000
nagios soft nproc 1000000
nagios hard nproc 1000000
These limits seem to be applied to the icinga user properly, if I su - to the
icinga user I get those limits as per the following
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 257691
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1000000
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 1000000
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Michael Friedrich asked it would be interesting what you did to the config.
using the defaults or several tweaks? was icinga compiled with embedded perl
and is that enabled? is use_large_installation_tweaks enabled? how many icinga
processes are there at the stage the error happens? Answers are: Initially
icinga was compiled with a "vanilla" configuration (ie no config switches)
which I think includes the embedded perl interpreter.I have since recompiled it
with the embedded perl interpreter disabled (./configure
--disable-embedded-perl), the problem happens in bothcases. Initially I had the
large_installation_tweaks setting set to 1 (as it is on the old system), I've
tried it with that setting commented out and it makes no difference.As far as
I'm aware there are no neb modules installed, it's essentially a vanilla
install. I'm not sure how many icinga processes are running at the time (it
takes 6-8 hours for the problem to develop), I'll write a script to monitor
that. Thanks - Gavin
**********************************************************************
***** IMPORTANT INFORMATION *****
This document should be read only by those persons to whom it is
addressed and its content is not intended for use by any other persons.
If you have received this message in error, please notify us
immediately. Please also destroy and delete the message from your
computer. Any unauthorised form of reproduction of this message
is strictly prohibited.
BankSA - A Division of Westpac Banking Corporation AFSL 233714, is not
liable for the proper and complete transmission of the information
contained in this communication, nor for any delay in its receipt.
**********************************************************************
This message has been scanned for malware by SurfControl plc.
www.surfcontrol.com
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/icinga-users
