10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Got this error when starting nrpe
Starting nagios-nrpe: nagios-nrpe/usr/sbin/nrpe: error while loading shared libraries: libssl.so.0.9.8:
Pls advise
---------- Post updated at 04:05 PM ---------- Previous update was at 04:05 PM ----------
os is Debian lenny
---------- Post updated... (1 Reply)
Discussion started by: lhareigh890
1 Replies
2. UNIX and Linux Applications
Hi I navigated to this forum thanks to this thread:
/hp-ux/140594-couldnt-start-nrpe-services-unknown-service.html
I don't know why is closed without a solution.
Whatever...
Feb 22 17:00:43 localhost daemon:err|error inetd: nrpe/tcp: unknown serviceMeans, you need to add something like... (0 Replies)
Discussion started by: ndarkduck
0 Replies
3. Solaris
I am trying to compile nrpe 2.12 against openssl 1.0 on Solaris 10 however I am getting core dumps for some reason. Anyone know a way to fix this?
Here is the output of make:
bash-3.00# make all
cd ./src/; make ; cd ..
gcc -g -fPIC -Wall -O2 -I/usr/local/ssl/include... (0 Replies)
Discussion started by: _JPL_
0 Replies
4. UNIX and Linux Applications
Good morning folks,
I'm having a problem with check_disk with mounted 3TB volumes. It appears that the value being returned by stavfs is too large to be processed by the check_disk plugin. Does anyone know of an updated check_disk plugin?
Solaris 10:
# /usr/local/nagios/libexec/check_disk -w... (0 Replies)
Discussion started by: avronius
0 Replies
5. Infrastructure Monitoring
（1）check the service of nrpe
# libexec/check_nrpe -H 59.26.240.63
NRPE v2.8.1
（2）check the resource of nrpe's host
# libexec/check_nrpe -H 59.26.240.63 -c check_df
DISK OK - free space: / 8241 MB (77% inode=98%); /var 5239 MB (95% inode=99%); /usr 11971 MB (86%... (0 Replies)
Discussion started by: zhengsenlin
0 Replies
6. AIX
I have NRPE running on AIX 5.3. Right now I have it running as a stand alone daemon, but I want to configure it to be controlled by inetd. I add the service to the /etc/services file and /etc/inetd.conf, but it will now show up in the list of subservers that I can start in smit. I know I must be... (1 Reply)
Discussion started by: acascianelli
1 Replies
7. Infrastructure Monitoring
HI guyz,
I have a nagios 3.0.6 server which is running on fedora 5. I had already added some windows clients and monitoring it. Now i want to add a unix client.
Steps done till now : -
1.nagios-plugins-1.4.13 was installed and configured.
2.unzipped and untarred the NRPE 2.8
3.I gave a... (0 Replies)
Discussion started by: Renjesh
0 Replies
8. Solaris
Hi guys,
I have a linux box with nagios installed on it. I have configured some windows clients very easily and now i want to configure a unix client on it.
Steps done:
1) installed nagios-plugins-1.4.13
2) downloaded nrpe-2.12, but while giving "./configure" command, it is throwing an... (1 Reply)
Discussion started by: Renjesh
1 Replies
9. Solaris
Hi Guru's
On one of our servers we have every few seconds following error:
Apr 28 10:15:27 svr10010 nrpe: connect from reno.customs.govt.nz
Apr 28 10:15:29 svr10010 nrpe: connect from reno.customs.govt.nz
Here are the details from this box:
SunOS svr10010 5.10 Generic_125100-10 sun4v... (3 Replies)
Discussion started by: gnom
3 Replies
10. Solaris
Hi have a Solaris 9 box and I'm trying to install Nagios on it.
I've installed the GCC compiler as well as OpenSSL and OpenSSH.
When I run the # ./configure for the nrpe plugin it executes without any obvious errors. However, when I run the # make install afterwards if fails with the... (0 Replies)
Discussion started by: soliberus
0 Replies
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, +@netgroup (from which
only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, +@netgroup (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD
