Folks: I''ve started to play around with the comprehensive integrated module set from example42 (http://www.example42.com/). Following the instructions, I set up one node as a nagios server, with ''include nagios''. I set up another node to be monitored via nagios, with ''include nagios::target". I set $monitor=true for the base node, which is inherited by both the nagios server and the target node, and I set $monitor_type = ["nagios", "munin"], and I set $monitor_tool = "nagios". I find the target''s nagios resources exported to the storeconfigs database, eg: | 105 | /etc/nagios/auto.d/services/client.example.com-apache_process.cfg | File | 2 | 4 | 1 | 45 | 2011-02-28 20:43:14 | 2011-02-28 20:43:14 | However, though both systems are monitored by munin in this setup, the nagios server never seems to monitor the target node. /etc/nagios/auto.d/services/client.example.com-apache_process.cfg and friends do not get created on either system. Is anyone from example42 around to help point out where I''m being stupid here? Thanks -Pete -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Al @ Lab42
2011-Mar-01 13:43 UTC
[Puppet Users] Re: Nagios monitoring with example42 modules
Hi Pete, On Monday, February 28, 2011 9:47:36 PM UTC+1, pete ehlke wrote:> > Folks: > > I''ve started to play around with the comprehensive integrated module set > from example42 (http://www.example42.com/). > > Following the instructions, I set up one node as a nagios server, with > ''include nagios''. I set up another node to be monitored via nagios, with > ''include nagios::target". I set $monitor=true for the base node, which is > inherited by both the nagios server and the target node, and I set > $monitor_type = ["nagios", "munin"], and I set $monitor_tool = "nagios". I > find the target''s nagios resources exported to the storeconfigs database, > eg: > > | 105 | /etc/nagios/auto.d/services/client.example.com-apache_process.cfg > | File | 2 | 4 | 1 | 45 | > 2011-02-28 20:43:14 | 2011-02-28 20:43:14 | > > However, though both systems are monitored by munin in this setup, the > nagios server never seems to monitor the target > node. /etc/nagios/auto.d/services/client.example.com-apache_process.cfg and > friends do not get created on either system. > > Is anyone from example42 around to help point out where I''m being stupid > here? > >Yes. Your setup doesn''t seem to have something particularly wrong, but if you want to replicate a working layout try this: Set for all nodes: $monitor = "yes" $monitor_tool = [ "nagios" , "munin" ] And on you Nagios server: include nagios That should be enough. Consider that you do not need anymore to include nagios::target on the nodes to be monitored and that the variable $monitor_type is not used (eventually tell me where you''ve read about it... the could be a mistake in the documentation). One thing that could be the cause for your problem is the variable $nagios_grouplogic that is useful if you need different Nagios servers checking nodes according to custom grouping logic. If undefined your Nagios server should monitor all the nodes registered to the same puppetmaster. Please, let me know if this helps. Best regards, Al -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.