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!

1 (4)
Article Rating (4 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
NSCA Server - Debug Logging
Viewed 14499 times since Mon, Mar 23, 2015
Nagios XI - Installing Latest SourceGuardian Loaders
Viewed 10988 times since Mon, Jun 18, 2018
NRPE - Turn Off XINETD Logging On Success
Viewed 15514 times since Tue, Mar 7, 2017
Nagios XI - Empty Screen for Wizard, Component, Dashlet
Viewed 10471 times since Wed, Jan 27, 2016
Nagios XI - Display All Scheduled Reports
Viewed 7178 times since Wed, Oct 12, 2016
NRPE - Packet Size Explained
Viewed 35698 times since Thu, Jun 30, 2016
NRPE - Return Code Of 126 Is Out Of Bounds - Plugin May Not Be Executable
Viewed 10258 times since Fri, Jul 14, 2017
Nagios XI - SQL Error [nagiosxi] : ERROR: syntax error
Viewed 10821 times since Sun, Sep 10, 2017
Nagios XI - ICMP and Ping Checks Stopped Graphing
Viewed 17493 times since Mon, Jan 25, 2016
Nagios XI - Apply Configuration Fails - Backend login to the Core Configuration failed
Viewed 29136 times since Tue, Aug 2, 2016