Nagios Support Forum

Hello,
After launch of NAGIOS 4.4.3 on redhat 7.6, there is some crash with only "Caught SIGTERM, shutting down..." in nagios.log
I try with this command "nagios /etc/nagios/nagios.cfg" with nagios user and after some seconds or minute i have this message and nagios stop:

Nagios Core 4.4.3
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2019-01-15
License: GPL

Website: https://www.nagios.org
Nagios 4.4.3 starting... (PID=24232)
Local time is Thu Sep 19 19:35:33 CEST 2019
wproc: Successfully registered manager as @wproc with query handler
wproc: Registry request: name=Core Worker 24236;pid=24236
wproc: Registry request: name=Core Worker 24234;pid=24234
…..
wproc: Registry request: name=Core Worker 24240;pid=24240
wproc: Registry request: name=Core Worker 24243;pid=24243
Event broker module '/usr/local/lib/mk-livestatus/livestatus14.o' initialized successfully.
Event broker module '/usr/lib64/mod_gearman/mod_gearman_nagios4.o' initialized successfully.
WARNING: RLIMIT_NPROC is 99727, total max estimated processes is 1057694! You should increase your limits (ulimit -u, or limits.conf)
2019-09-19 19:35:36 [6] updating log file index
2019-09-19 19:35:36 [6] updating log file index
Warning: Host performance file processing command 'process-host-perfdata-file' was not found - host performance data file will not be processed!
Warning: Service performance file processing command 'process-service-perfdata-file' was not found - service performance data file will not be processed!
Successfully launched command file worker with pid 24245
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not valid
Aborted (core dumped)

The last 3 lines cames only with this command line, not with systemctl start nagios in any log file.
Nagios came from RPM of EPEL Release for REDHAT 7.6 epel-rhel-x86_64-server-7

Any idea ?

Thanks

Please attach your nagios.cfg file so that we can review it.

Are you running mod_gearman?

Try running these commands (translate them to your files and send us the full output):

Hello,
We use a server for nagios core 4 with gearmand and mod-gearman-neb, and 4 server with mod gearman worker and 2 server for thruk ihm
We are upgrading from icinga 1.8 to nagios core 4.4.3.

We use nagios -pv and nagios -ud

I put nagios.cfg in attachment

The results of nagios -v :
Nagios Core 4.4.3
Copyright (c) 2009-present Nagios Core Development Team and Community Contributors
Copyright (c) 1999-2009 Ethan Galstad
Last Modified: 2019-01-15
License: GPL
Website: https://www.nagios.org
Reading configuration data...
Read main config file okay...
Read object config files okay...
Running pre-flight check on configuration data...
Checking objects...
Checked 166149 services.
Checked 12233 hosts.
Checked 5226 host groups.
Checked 0 service groups.
Checked 4 contacts.
Checked 2 contact groups.
Checked 368 commands.
Checked 337 time periods.
Checked 0 host escalations.
Checked 0 service escalations.
Checking for circular paths...
Checked 12233 hosts
Checked 0 service dependencies
Checked 0 host dependencies
Checked 337 timeperiods
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...
Total Warnings: 0
Total Errors: 0
Things look okay - No serious problems were detected during the pre-flight check

The result of nagios -d :
-bash-4.2$ nagios -d /etc/nagios/nagios.cfg
-bash-4.2$ ps -ef|grep nagios
root 11908 5646 0 14:00 pts/0 00:00:00 su - nagios
nagios 11909 11908 0 14:00 pts/0 00:00:00 -bash
nagios 11952 1 99 14:00 ? 00:00:08 nagios -d /etc/nagios/nagios.cfg
nagios 11953 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh
nagios 11954 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh
nagios 11955 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh
nagios 11956 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh
nagios 11957 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh
nagios 11958 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh
nagios 11959 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh
nagios 11960 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh
nagios 11961 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh
nagios 11962 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh
nagios 11963 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh
nagios 11964 11952 0 14:00 ? 00:00:00 nagios --worker /var/spool/nagios/cmd/nagios.qh

Actually nagios daemon stay up

Are you trying to install Nagios Core over the top of Icinga, upgrade the Nagios Core in Icinga, or is the just a new Nagios Core server?

It's a new nagios server without anything that NAGIOS, NAGIOS GUI, gearmand , livestatus and modgearman
VM Redhat 7.6 with 8vCPU, 23GO RAM, 2 Go RAMDISK, 80GO SSD
In the near future:
- total of 210000 services and 14000 hosts
- the performance data will go to grafana by the npcd process_perfdata.pl script

I looked up your account and a Nagios Core support plan has not been registered with this username. If this is an error, please let me know I’ll work with the sales department to get this resolved quickly.

The Customer > Nagios Core section is meant to be for support for customers who have purchased a Nagios Core support plan, if you're dealing with an XI system's backend Nagios Core then you should post in the Nagios XI Customer section.

Otherwise, if you’re interested in Nagios Core Support plan, please contact [email protected] or feel free to post your question on the Nagios Core general support forum.

Do you have a Nagios Core support plan? If not, I'll need to move this to the General section.

That being said, I'm thinking this may be a gearman/livestatus NEB module issue.

Try this, edit your /usr/local/nagios/etc/nagios.cfg and change these lines:
To this:
Then start up Nagios Core and see if it stays running this time, if it does, it's not a Nagios Core issue.

Hello,
We have one NAGIOS XI with support plan and some NAGIOS CORE without support plan.
Next month a second NAGIOS XI will be installed with support plan
Our Nagios Core included with NAGIOS XI have the same issue (Nagios Core 4.2.4).

Nagios launch without broker, waiting

Try leaving gearman enabled and disable the livestatus one and see if it stays running.

What you're trying to do here is determine where the issue is, it's either a Nagios Core issue, a mod_geaman neb module issue, or a livestatus neb module issue.

If it works with gearman, we know it's livestatus. Disable gearman then and do the same with livestatus so that you can see which is causing the problem.

Our Nagios Core included with NAGIOS XI have the same issue (Nagios Core 4.2.4).

Then you will need to do this on your XI server (instead of the Core one) and resend all previous info from your XI system instead of from the Core system. If you want help with this Core system (not an XI system) we will need to move this to the Nagios Core General Section as you do not have a Nagios Core support plan (a separate thing for Nagios Core), the Nagios Core that XI uses on the backend of XI is supported but not in the way you're trying to apply it (globally to all your Nagios Core servers as well). If you have questions, please reach out to [email protected] for more information.

Would you like to keep this post here and work on your XI stuff here (please include all the previously requested data from your XI server as we are not going to use output from one server to debug output from another server) OR would you like me to move it to the General section so that we can continue working on your Core issues for your Core server?

Hello,
we make a livestatus 1.2.8p25 with patch by SNI
https://github.com/sni/mod_gearman/issu ... -319336402
and now it's OK
thank's

sigmainformatique wrote:Hello,
we make a livestatus 1.2.8p25 with patch by SNI
https://github.com/sni/mod_gearman/issu ... -319336402
and now it's OK
thank's

great!

Locking thread