On 23/09/06, James McKenzie <[EMAIL PROTECTED]> wrote: > Thank you. Yes, I was hupping the process rather than going through a > shutdown/startup sequence. I've tried both.
And do you get the same "error on subcontainer" messages both times? > > What happens if you shut the agent down completely, make sure that > > the config file(s) contain the minimum settings that you want to use, > > and start the agent up again? > > > The monitor fires once and only once. Errr... that sounds (possibly) correct. The design of the DisMan Event MIB is that such monitors should only fire once for any given "event". The trigger is only re-armed again when the value being sampled drops below the threshold value (or whatever is appropriate for that particular point) *at the time the next sample is taken*. If the problem disappears and then comes back - all within a single sample time, then the agent won't spot this, and the trigger won't be re-armed. Can you please be a little more explicit about exactly what you are doing, what commands etc you are running, what monitored processes are/are not running at any time, what you see from the agent, and what the timings involved are. It might also be worth running the agent with the flag -Ddisman That should print a certain amount of (hopefully) useful internal information. Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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
