Marc Powell wrote:
>
>> -----Original Message-----
>> From: [email protected] [mailto:nagios-devel-
>> [email protected]] On Behalf Of Gerd Mueller
>> Sent: Wednesday, February 07, 2007 9:40 AM
>> To: Nagios Developers List
>> Subject: [Nagios-devel] nagios-cvs: Too many open files?
>>
>> Hi,
>>
>> my systems are sometimes running out of open file handles. Is this
>> normal for a normal nagios process:
>>
>> nag01:~# lsof | grep "/tmp/nagios" | wc -l 41631
>
> I would say no, since nagios doesn't usually open files in /tmp.
>
> [root@dc1 root]# lsof | grep "/tmp/nagios"
> [root@dc1 root]#
>
> Is that the location of temp_file in nagios.cfg? Is the command shown in
> lsof for those processes nagios or some plugin? I suspect that it's
> going to be some misbehaving plugin that you're using.
>
Actually, Nagios has a new temp_path option that defines a directory
where Nagios will create temp files. Host and service checks in Nagios
3 write their output to temp files - that's how the plugin output length
restriction was done away with.
These temp files should be deleted once Nagios processed a host or
service check result. When Nagios stops, child processes may still be
running checks and writing output to temp files. These files won't get
processed/deleted up when Nagios restarts, so its a good idea to use
something like tmpwatch to delete temp files older than a few hours.
Gerd, the number of temp files is extremely high. How many Nagios
(child) processes are running when you check the count of temp files?
Something seems to be amiss. Either that or you're monitoring a ton of
services.
Ethan Galstad,
Nagios Developer
---
Email: [email protected]
Website: http://www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]