thanks for your reply Jeffrey
You have enable "log_external_commands=1" in your nagios.cfg, correct? Yes
You're pulling in your new, extra config files at the end of your snmptt.ini file, like so:
You are right - Additional lines are added in snmptt.ini
Yes
Search found 4 matches
- Mon Jun 08, 2020 1:43 pm
- Forum: Open Source Nagios Projects
- Topic: Traps are written in snmptt.log but not in nagios.log
- Replies: 2
- Views: 1008
- Thu Jun 04, 2020 4:56 am
- Forum: Open Source Nagios Projects
- Topic: How to stop auto clearance of Trap from Status Page
- Replies: 1
- Views: 817
How to stop auto clearance of Trap from Status Page
Hello,
Whenever i receive OSPF Trap down - It is visible in Nagios alert history and Network Status page. but, when issue is auto resolved then Error is auto cleared from current Network status. How can be stop trap being auto cleared from the status page?
Nagios Core version : 4.4.5
Whenever i receive OSPF Trap down - It is visible in Nagios alert history and Network Status page. but, when issue is auto resolved then Error is auto cleared from current Network status. How can be stop trap being auto cleared from the status page?
Nagios Core version : 4.4.5
- Fri May 29, 2020 2:19 pm
- Forum: Open Source Nagios Projects
- Topic: Traps are written in snmptt.log but not in nagios.log
- Replies: 2
- Views: 1008
Traps are written in snmptt.log but not in nagios.log
I have migrated from Nagios core 3 to Nagios 4.4.5 copied all the files properly. every thing is working properly, Except for traps log not written in nagios.log Below is the scenario With newly complied MIB, conf file which automatically add new conf path in snmptt.ini, traps are generating properl...
- Thu May 28, 2020 2:28 am
- Forum: Open Source Nagios Projects
- Topic: Additional lines in nagios.log
- Replies: 0
- Views: 792
Additional lines in nagios.log
Using Nagios Core 4.4.5 and SNMPTT for Traps on RHEL 7 Nagios Log Output : SERVICE ALERT: XXX-EXXXX;TRAP;CRITICAL;HARD;1;down:OSPF router id 10.xxx.xxx.xxx , neighbor router id 10.xxx.xxx.xxx with peering address 10.xxx.xxx.xxx state changed to down [1590369227] PROCESS_SERVICE_CHECK_RESULT:10.xxx.x...