[TrapFiles]
# A list of snmptt.conf files (this is NOT the snmptrapd.conf file). The COMPLETE path
# and filename. Ex: '/etc/snmp/snmptt.conf'
snmptt_conf_files = <<END
/etc/snmp/snmptt.conf
/usr/share/snmp/mibs/processed_mibs
/usr/share/snmp/mibs/
END
It seems that XI is not parsing the traps for entires in snmptt.log the associated trap service for the host shows : OK: no data received yet.
Is there anything obvious that could be causing this?
It could be that the service has the freshness option enabled which will clear the results after a set amount of time and display this message. Edit it in the CCM and check for this under the Check_Settings tab. The option could also be inherited from a template applied to the service.
/etc/snmp/snmptt.conf may not be configured correctly as well. Doublecheck this file to make sure that an EVENT in there matches what is seen in the snmptt.log.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
snmptt.service - SNMP Trap Translator (SNMPTT)
Loaded: loaded (/usr/lib/systemd/system/snmptt.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2018-02-23 15:15:13 GMT; 56min ago
Main PID: 41842 (snmptt)
CGroup: /system.slice/snmptt.service
├─41840 /usr/bin/perl /usr/sbin/snmptt --daemon
└─41842 /usr/bin/perl /usr/sbin/snmptt --daemon
Feb 23 15:15:13 NAGIOS systemd[1]: Starting SNMP Trap Translator (SNMPTT)...
Feb 23 15:15:13 NAGIOS snmptt-sys[41678]: SNMPTT v1.4beta2 started
Feb 23 15:15:13 NAGIOS snmptt-sys[41678]: Loading /etc/snmp/snmptt.conf
Feb 23 15:15:13 NAGIOS snmptt-sys[41678]: Finished loading 64 lines from /etc/snmp/snmptt.conf
Feb 23 15:15:13 NAGIOS snmptt-sys[41842]: Changing to UID: snmptt (995)
Feb 23 15:15:13 NAGIOS systemd[1]: snmptt.service: Supervising process 41842 which is not our child. We'll most likely not notice when it exits.
Feb 23 15:15:13 NAGIOS systemd[1]: Started SNMP Trap Translator (SNMPTT).
Feb 23 15:15:13 NAGIOS systemd[1]: snmptt.service: Supervising process 41842 which is not our child. We'll most likely not notice when it exits.
As @cdienger mentioned above, the issue is almost certainly with configuration, rather than with which services are running/not running.
If you are receiving traps on the system (if traps are showing up in snmptt.log), but they're not showing up in Nagios XI, we'll need to see the snmptt configuration file, at /etc/snmp/snmptt.conf
If you're not receiving traps, we'll need to see the status of the snmptrapd service, which is responsible for listening on port 162. You can check the status of this with either