Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
To get nagios to start on boot, you need to add it to the init system in the same way you added iptables (except for downloading the init script as it already exists in /etc/init.d):
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
I tried to add Nagios to startup but now I can not start apache2.
Nagios can be started/stopped but I am not able to access it on web.
[*]srvnagios:~# /etc/init.d/apache2 start
Starting web server: apache2(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
Action 'start' failed.
The Apache error log may have more information.
failed!
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
The issue is that NSClient (0.3.8) is not sending information to Nagios.
By default NSClient is an active check, which means Nagios (on your Debian machine) starts the connection and receives a reply. Since Nagios initiates the communication, this is probably not an issue with firewalls or listening ports.
where xx.xx.xx.xx is the ip address of you nsclient machine.
also, the location of check_nrpe may be different if you compiled from source, but it should be in the same location as check_ping which you've been using.