THIS KNOWLEDGE BASE HAS BEEN ARCHIVED AND IS NO LONGER BEING UPDATED
Please visit library.nagios.com/docs for the latest and most up-to-date documentation.
Home » Categories » Multiple Categories

Disabling Port 113 IDENT Requests

Problem Description

You are seeing port 113 return requests either from your Nagios XI server (when submitting NSCA passive results) to the originating host OR you are seeing port 113 return requests when checking NRPE services).

You will see this behaviour on your firewall logs as you will most likely not have a firewall rule for port 113.

 

 

Explanation

This is usually because you are running an NRPE check through XINETD with USERID included on the log_on_success or log_on_failure options in your remote hosts /etc/xinetd.d/nrpe file.

OR this could be because you are submitting passive results to the XI server through NSCA (which is running under XINETD) /etc/xinetd.d/nsca with the same options as above.

Further information can be found in the following link:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/4/html/Reference_Guide/s2-tcpwrappers-xinetd-alt.html#s3-tcpwrappers-xinetd-alt-log

Note that the USERID option requires an IDENT request to port 113 on the originating server to determine the USERID, that's why you're seeing it.

 

Resolution

Then remove the USERID option from the log_on_failure AND log_on_success to stop the IDENT from occurring. The file you need to change depends on:

  • NRPE on remote host
    • /etc/xinetd.d/nrpe
  • NSCA on Nagios XI server
    • /etc/xinetd.d/nsca

For example, either comment this line out or remove it completely:

# default: on
# description: NSCA (Nagios Service Check Acceptor)
service nsca
{
           flags = REUSE
           socket_type = stream        
           wait = no
           user = nagios
           group = nagios
           server = /usr/local/nagios/bin/nsca
           server_args = -c /usr/local/nagios/etc/nsca.cfg --inetd
           log_on_failure += USERID
           disable = no
           only_from = 127.0.0.1
}

 

After making the changes you need to restart the xinetd service using one of the commands below:

 

RHEL 7+ | CentOS 7+ | Oracle Linux 7+ | Debian | Ubuntu 16/18/20

systemctl restart xinetd.service

 

 

 

Final Thoughts

For any support related questions please visit the Nagios Support Forums at:

http://support.nagios.com/forum/



Special Offer For Knowledgebase Visitors! Get a huge discount on Nagios Log Server by clicking below.

Get 60% Off Nagios Log Server!

Did you know? Nagios provides complete monitoring of: Windows, Linux, UNIX, Servers, Websites, SNMP, DHCP, DNS, Email, Storage, Files, Apache, IIS, EC2, and more!

0 (0)
Article Rating (No Votes)
Rate this article
  • Icon PDFExport to PDF
  • Icon MS-WordExport to MS Word
Attachments Attachments
There are no attachments for this article.
Related Articles RSS Feed
Nagios XI - Common Upgrade Failures And Solutions
Viewed 15932 times since Thu, Jun 29, 2017
NSCA Server - Inbound TCP Traffic
Viewed 25669 times since Tue, Mar 24, 2015
Nagios XI - ERROR: unable to open include file: /etc/mrtg/conf.d/xxxxxxx.cfg
Viewed 9556 times since Wed, Jun 1, 2016
Nagios XI - Disabling Database UTF8 Connectivity
Viewed 6233 times since Thu, Mar 8, 2018
Nagios XI - Running Out Of Disk Space On The Nagios XI VM
Viewed 26295 times since Tue, Jan 27, 2015
Nagios XI - Profile Build Failed
Viewed 15029 times since Tue, Aug 2, 2016
Nagios XI - Configuration Applies, No Changes Take Place
Viewed 9713 times since Tue, Jan 27, 2015
Nagios XI - Event Data Is Stale
Viewed 6802 times since Wed, Jan 27, 2016
Nagios XI - Some BPI Checks Show "Unknown BPI Group Index" After Upgrade
Viewed 5158 times since Wed, Sep 18, 2019
Nagios XI - Login Screen Keeps Redirecting To Itself
Viewed 8237 times since Wed, Jan 27, 2016