Nagios Support Forum

There is no performance difference between "standalone" and "xinetd". Either way nrpe runs as a listener service. The benefit of the xinetd method is that you can install by the ./fullinstall script which will take care of installing dependencies and configuration steps. Install NRPE using the following guide on one of your remote hosts and go from there.

https://support.nagios.com/kb/article.php?id=8

Thank you!

bolson wrote:There is no performance difference between "standalone" and "xinetd". Either way nrpe runs as a listener service. The benefit of the xinetd method is that you can install by the ./fullinstall script which will take care of installing dependencies and configuration steps. Install NRPE using the following guide on one of your remote hosts and go from there.

https://support.nagios.com/kb/article.php?id=8

Thank you!

The guide has nagiosxi should that matter since I'm running nagios core? Because when i tried to run ./fullinstall as root i got the this

./fullinstall
-bash: ./fullinstall: Permission denied

From linux-nrpe-agent directory run:
And post the result.

bolson wrote:From linux-nrpe-agent directory run:

Code: Select all

ls -l

And post the result.

ls -l
total 56
-rwxrwxrwx 1 root root 2409 Jun 23 2016 0-repos
-rwxrwxrwx 1 root root 1086 Jan 5 2015 1-prereqs
-rwxrwxrwx 1 root root 1340 Jan 5 2015 2-usersgroups
-rwxrwxrwx 1 root root 458 Jan 5 2015 3-services
-rwxrwxrwx 1 root root 3964 Aug 16 2016 4-firewall
-rwxrwxrwx 1 root root 969 Jul 13 2016 A-subcomponents
-rwxrwxrwx 1 root root 1064 Sep 12 2016 CHANGES.txt
-rwxrwxrwx 1 root root 4752 Jun 23 2016 fullinstall
-rwxrwxrwx 1 root root 1832 Jan 5 2015 get-os-info
-rwxrwxrwx 1 root root 1197 Apr 2 2015 init.sh
-rwxrwxrwx 1 root root 240 Jan 5 2015 nagios.firewallapps
drwxrwxrwx 2 root root 108 Jan 5 2015 packages
drwxrwxrwx 6 root root 81 Jan 5 2015 subcomponents
drwxrwxrwx 2 root root 6 Jan 5 2015 xinrpe
-rwxrwxrwx 1 root root 768 Jan 5 2015 xi-sys.cfg
-rwxrwxrwx 1 root root 610 Jan 5 2015 xivar

This would appear to be an issue relating to your operating system. Your permissions are set correctly so there's really no reason you should be getting that error. And I'm unable to recreate the issue on my end. Perhaps try a different machine?