I know that, but it was announced that something like livestatus will be integrated in Nagios 4.3 ... so I hopped
On the other hand maybe someone found a solution for reading livedata out of nagios like livestatus oder mod_german can do it.
Nagios 4.2.3 Crash every few hors
-
- Posts: 1597
- Joined: Tue Sep 27, 2016 4:57 pm
Re: Nagios 4.2.3 Crash every few hors
I don't think that was announced anywhere.
You can see the changelog for Nagios Core here:
https://raw.githubusercontent.com/Nagio ... /Changelog
You can see the changelog for Nagios Core here:
https://raw.githubusercontent.com/Nagio ... /Changelog
Previous Nagios employee
Re: Nagios 4.2.3 Crash every few hors
With the help of a german forum I finally found out, what the problem was:
Thruk has a logic called: Business-Process which casues livestatus to directly insert data into the nagios-process
This causes the problems. But you can change Thruk that it doesn't use the livestatus feature ... it posts it via the command-queue of nagios.
This works perfectly - no crashes anymore.
So to fix the problem, change in the thruk_local.conf the following lines:
OLD:
NEW
Thruk has a logic called: Business-Process which casues livestatus to directly insert data into the nagios-process
This causes the problems. But you can change Thruk that it doesn't use the livestatus feature ... it posts it via the command-queue of nagios.
This works perfectly - no crashes anymore.
So to fix the problem, change in the thruk_local.conf the following lines:
OLD:
Code: Select all
# Business Process
<Component Thruk::Plugin::BP>
# Results will be send back by using the spool folder.
# This folder should point to the 'check_result_path' of your core.
spool_dir = /var/log/nagios/spool/checkresults
# as alternative to the spool_dir, a livestatus connection can be used
# to send results to the core.
# result_backend = yourServer
NEW
Code: Select all
# Business Process
<Component Thruk::Plugin::BP>
# Results will be send back by using the spool folder.
# This folder should point to the 'check_result_path' of your core.
spool_dir = /var/log/nagios/spool/checkresults
# as alternative to the spool_dir, a livestatus connection can be used
# to send results to the core.
# result_backend = yourServer
-
- Former Nagios Staff
- Posts: 4583
- Joined: Wed Sep 21, 2016 10:29 am
- Location: NoLo, Minneapolis, MN
- Contact:
Re: Nagios 4.2.3 Crash every few hors
Thanks for the post! I'm sure it will be helpful to others.
The roadmap did have something about a mod_gearman replacement, so that may be what you are remembering. I'm not sure about the ETA on that.
Ok to go ahead and lock this one up?
The roadmap did have something about a mod_gearman replacement, so that may be what you are remembering. I'm not sure about the ETA on that.
Ok to go ahead and lock this one up?
Re: Nagios 4.2.3 Crash every few hors
Yes I think this workaround can be used without any problems ... for me the problem is solved at the moment.
I'm looking forward to the german inclusion ... but it isn't urgent for me any more!
I'm looking forward to the german inclusion ... but it isn't urgent for me any more!