max_check_result_file_age

An open discussion forum for obtaining help with Nagios Core. Nagios Core users of all experience levels are welcome here. Subforum have been created for the discussion of Nagios Core and Nagios Plugin development.

NOTE: The SourceForge.net mailing lists have been deprecated in favor of this forum in order to expedite support and provide additional features not available on the old mailing list.

max_check_result_file_age

Postby sandeepatil » Tue Nov 05, 2019 1:59 am

Can we increase max_check_result_file_age=3600 to 100000

Due to checkresult not managing alarm flood, nagios partition inode getting full and this cause other partition full and at last server status is hung.
sandeepatil
 
Posts: 196
Joined: Tue Dec 27, 2016 3:12 am

Re: max_check_result_file_age

Postby scottwilkerson » Tue Nov 05, 2019 7:47 am

If you increase the max_check_result_file_age it would allow MORE files to accumulate, not less.

I would thing making it shorter would have a more desired effect
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
scottwilkerson
DevOps Engineer
 
Posts: 17023
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises

Re: max_check_result_file_age

Postby sandeepatil » Tue Nov 05, 2019 12:09 pm

If I set value less the 3600, it will prevent nagios partition inode full and checkresult dir full issue.
sandeepatil
 
Posts: 196
Joined: Tue Dec 27, 2016 3:12 am

Re: max_check_result_file_age

Postby scottwilkerson » Tue Nov 05, 2019 12:13 pm

sandeepatil wrote:If I set value less the 3600, it will prevent nagios partition inode full and checkresult dir full issue.

I'm not sure I understand the question

Here's some info about the setting
Max Check Result File Age

Format: max_check_result_file_age=<seconds>
Example: max_check_result_file_age=3600
This options determines the maximum age in seconds that Nagios will consider check result files found in the check_result_path directory to be valid. Check result files that are older that this threshold will be deleted by Nagios and the check results they contain will not be processed. By using a value of zero (0) with this option, Nagios will process all check result files - even if they're older than your hardware :-).

Note: Make sure that only a single instance of Nagios has access to the check result path. If multiple instances of Nagios have their check result path set to the same directory, you will run into problems with check results being processed (incorrectly) by the wrong instance of Nagios! Also note that because of the new core worker architecture in Nagios Core 4, this path is now only used for passive check results.

https://assets.nagios.com/downloads/nagioscore/docs/nagioscore/4/en/configmain.html
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
scottwilkerson
DevOps Engineer
 
Posts: 17023
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises

Re: max_check_result_file_age

Postby sandeepatil » Tue Nov 05, 2019 1:13 pm

Got it, thanks for sharing details.

Question : Why dir checkresult getting filled (physical and inode both) during alarm flood and how to prevent.
sandeepatil
 
Posts: 196
Joined: Tue Dec 27, 2016 3:12 am

Re: max_check_result_file_age

Postby scottwilkerson » Tue Nov 05, 2019 1:25 pm

sandeepatil wrote:Got it, thanks for sharing details.

Question : Why dir checkresult getting filled (physical and inode both) during alarm flood and how to prevent.

Are you receiving passive checks?

inodes are the number of allowed files on the drive, each passive check result is going to create a file that will get picked up by the nagios process (provided it is running properly).
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
scottwilkerson
DevOps Engineer
 
Posts: 17023
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises

Re: max_check_result_file_age

Postby sandeepatil » Tue Nov 05, 2019 1:44 pm

Yes, we are receiving passive checks.

In checkresult dir data not getting delete and its increase its increase size of dir to 100% also inode 100%.

You have solution to avoid this.
sandeepatil
 
Posts: 196
Joined: Tue Dec 27, 2016 3:12 am

Re: max_check_result_file_age

Postby scottwilkerson » Tue Nov 05, 2019 1:45 pm

What are the permissions of the directory?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
scottwilkerson
DevOps Engineer
 
Posts: 17023
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises

Re: max_check_result_file_age

Postby sandeepatil » Tue Nov 05, 2019 1:46 pm

Permissions is 755
sandeepatil
 
Posts: 196
Joined: Tue Dec 27, 2016 3:12 am

Re: max_check_result_file_age

Postby scottwilkerson » Tue Nov 05, 2019 1:59 pm

sandeepatil wrote:Permissions is 755

owner/group?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
scottwilkerson
DevOps Engineer
 
Posts: 17023
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises

Next

Return to Nagios Core

Who is online

Users browsing this forum: No registered users and 22 guests