Nagios Core 4.0.1 Problem

[NAfzali]

Hello,

i have nagios core 3.5.1 in my network and it monitors 1256 hosts and 1630 services. two weeks before i have wanted to install new version 4.0.1 and restore all my configuration files on it. after install new version i have some more problem... in "Status Information" of each service or host, it show me : "(No output on stdout) stderr:" and it has not save logs of yesterday and other before days. now how can i fix this problem? i installed nagios-plugins-1.5 and after see these problem downgrade to nagios-plugins-1.4.16 but it not solve my problem, is there any solution?

thank you

[sreinhardt]

To clarify, you were having this issue previously on 3.5, then installed a new core 4 system and transferred the configs there? At that time, this same issues presented itself? Did you install core4 on the same system as 3.5 or an entirely new system? What OS is this on?

[NAfzali]

Hello,

OS is centos 5.5. it works fine with nagios-core-3.5.1, then i upgrade nagios version to 4.0, it has many issue ( as you seen in previous post ), so i upgrade version 4.0 to 4.0.1, but this version has those problems too. so i test it with another installation: install a new centos 5.5 and install nagios-core-4.0.1 on it, now i have those problems too. so install nagios-core-3.5.1 to monitor my network now, but our department policy is updating all our applications and until now i cant do it. is there any solution?

thank you

[sreinhardt]

This is a reported bug with core 4. One of our core devs is already looking into it, and thinks it may be an open file issue, when hitting the max limit. http://tracker.nagios.org/view.php?id=484

Try running the following commands when you are seeing the issue:

Code: Select all

cat /proc/sys/fs/file-nr 
su - nagios -c "ulimit -Hn; ulimit -Sn" 

[NAfzali]

hello,
thanks for your reply, my outputs are:
cat /proc/sys/fs/file-nr
3776 0 205901

su - nagios -c "ulimit -Hn; ulimit -Sn"
1024
1024

no history information and no output on stdout yet.

thank you

[sreinhardt]

Looks like this might be the same case, you are definitely out of "open files". Let's increase the limits and restart the nagios service.

edit /etc/security/limits.conf
Add or modify these two lines

Code: Select all

*                hard    nofile         10000
*                soft    nofile         5000

Log out of your current terminal, log back in. Restart all nagios services. If you only have nagios and no npcd, ndoutils, or anything, it would just be:

Code: Select all

service nagios restart

You can also check the limits on the nagios user with:

Code: Select all

su - nagios -c "ulimit -Hn; ulimit -Sn"

[NAfzali]

hello,
thank you for solution, i do that but not resolve my problem.

Status Information for services and host is:
(No output on stdout) stderr: (No output on stdout) stderr:

and my Alert History show that:

No history information was found in this archived log file

[sreinhardt]

Can you validate the ulimits for the nagios user have increased please? Otherwise at this time, we may have to wait for the core devs to come up with a resolve as it is considered a bug.

Code: Select all

su - nagios -c "ulimit -Hn; ulimit -Sn"

[NAfzali]

hello,
after do that, ulimits for my nagios is:

10000
5000

is there any other solution?
thank you

[abrist]

Can you give us a tail of /var/log/messages?

Code: Select all

tail -25 /var/log/messages