RE: nsNotifyRestart traps
Krishna Vivek Vitta <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
Hello Bill Thank you for inputs. Isn’t snmpd.log rotated on receiving the HUP signal ? How can we check “logrotate” is running on server ? It’s a free bsd box and would output of any command provide hint the reason of HUP signal How can we log timestamp in snmpd.log ? Thank you Krishna Vivek From: Bill Fenner <[email protected]> Sent: 27 August 2019 21:04 To: Krishna Vivek Vitta <[email protected]> Cc: [email protected] Subject: Re: nsNotifyRestart traps On Tue, Aug 27, 2019 at 2:54 AM Krishna Vivek Vitta <[email protected]<mailto:[email protected]>> wrote: Hello experts, We have a management server running snmpd where it is sending nsNotifyRestart traps. The frequency is once per day during same time. May I know on what occasions this trap is raised and I don’t get to see any logs in management server restarting agent(snmpd), though we see following in snmpd.log. I went to https://lmgtfy.com/?q=nsNotifyRestart and the first search result was http://net-snmp.sourceforge.net/wiki/index.php/FAQ:Agent_15 which says: The Net-SNMP agent ... generates an enterprise-specific trap 'nsNotifyRestart' ... on receiving a HUP signal - typically after being re-configured. One interesting thing to note is that "logrotate" is pretty likely to send a HUP to a daemon whose logs it's configured to rotate. Does your trap happen to coincide with when "logrotate" runs on your server? Bill _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users