similar to: Strange problem with exported ressources

Hi, We''re using thin stored configs heavily to manage things like Munin and Nagios and we''re currently wondering what to do when nodes go away, or change considerably. If we get rid of a server then all it''s stored config is still present in the database, as well as it''s nagios and munin configurations. We created a script that iterates through the database

Hello all. Probably this question has already been posed in the context of another software, but I am unable to find it. I would like to implement a module which should manage munin-clients as well as the munin-server. Here is what I am thinking about implementing: - There are two classes: munin::client and munin::server - munin::clients'' configuration will be managed automatically.

Greetings, I''m trying to wrap my head around a solution to a problem I''m facing with an exported resources configuration I have. I''m using the following simple config to build a munin configuration: @@file { "/etc/munin/munin.conf.d/${::fqdn}.node": content => "[All Hosts;${::fqdn}] address ${ipaddress_eth0} use_node_name yes\n\n", tag

Hi all, I am new to puppet and also newcomer in this group. I heart good things about puppet and I decided to give it a try 2 weeks now. After reading various documentation, I began using the complete configuration collection of puppet modules (thanks to David). But I have a problem with the munin module. It works fine, except that it seems to not export virtual ressources. Let me give more detail

Hi, I was playing with the munin plugin in nsd4 beta4, and saw some strange errors. Directly after starting nsd on linux, I'm seeing: $ ps ax -o pid,ppid,user,args | grep nsd 1638 1 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf 1641 1638 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf 1647 1641 nsd /usr/sbin/nsd -c /etc/nsd/nsd.conf $ sudo munin-run nsd_munin_memory

G''day. I am wondering what the current best practice for building a single file out of distributed fragments is with puppet. Specifically, my problem: 1. Install munin-node on arbitrary machines. 2. Install ''munin.conf'' as a single file on one machine, containing a configuration stanza for every machine that munin-node is installed on. The current best practice

Hi All, What is the best way to remotely monitor/administer a group of xen domUs across a network? We''re planning to deploy a few H/W servers with paravirtualized domUs. What are the best alternatives? What works and What doesn''t? Share your experiences. Cheers Rajan _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Greeting Puppeteers, ( I sent this from the wrong address so it may be a duplicate post after moderation ) I recently discovered puppet from the debian administration site and thought I might install it after BASHING my head against cfengine the last 3 times I tried to install it. I installed puppetmaster on my primary server and dropped puppet on a couple of xen virtuals. It worked

Hey Guys, I am trying to wrap some loose ends up before we close tomorrow and have one last thing. I have been asked to monitor tunnel bandwidth for vpn clients over the holidays and whipped up a quick Munin plugin to do this. It works well but one problem is that when a client disconnects, the plugin stops submitting graph data for it, so the png's don't show the user anymore, kinda hard

Hi, This is totally off-topic (it''s an rpm/rpmbuild problem), but I want to get to a point where I''m installing and configuring munin-node with puppet. To do that, I need a clean, standardized way of installing munin-mode on CentOS (RHELish) boxes. I could install munin-node from source via puppet and probably make enough edits that all the files end up in reasonable locations

I''m trying to use a "case defined" statement to configure Munin to automatically create plugin links for packages that are defined by Puppet but the behaviour seems to be unpredictable. I have a similar setup for Samba which works, but the Postfix one doesn''t and I can''t see any difference between them. Can some explain to me how "case

The munin rpms from EPEL failed to install correctly on a particular machine. This is why # /usr/sbin/groupadd -r munin groupadd: Can't get unique system GID (no more available GIDs) # but I don't understand why this happens. Even after checking the man pages for groupadd and login.defs, I have been unable to determine what the settings for SYS_GID_MIN/SYS_GID_MAX on RHEL/CentOS are.

I wrote a Perl script to poll `tc` for traffic control statistics (just bytes presently) for leaf qdiscs. The information is fed to either RRDTool or Munin[2], depending on what parameter is passed to the script. If the option for a RRD database is used, graphs[3][4] are written to disk for each ten second polling interval. If invoked via Munin[2], it handles graphing and samples at five

Does any one know or whether have someone done custom reports in puppet. Which will show the status of the servers, disk, cpu, load, pkg list, configs/files edited via puppet, how often a config file is updated, etc.. -- Deepak _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users

Hello list. I''ve the following parent class: class munin::client { ... munin::client::plugin { "postfix_mailqueue": name => "postfix_mailqueue", enable => "false" } } And the following inherited class: class munin::client::plugins::postfix inherits munin::client { munin::client::plugin {

Hello all. I am using the munin module for a while now, I think that after the upgrade to puppet and puppetmaster 0.23.2 (or 0.23.1) it simply stopped working. Were there any changes to the realizing and exporting of resources? What could prevent this module from stopping to work. What happenes is that new hosts (munin::client nodes) do get stored in the database, but the munin::host does not

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi *! Has anybody a fix/workaround for this beahaviour? My Service[munin-node] is subscribed to the timestamp of a directory containing config-snippets like this: {{{ file{"/etc/munin/plugins": checksum => mtime, } service{munin-node: subscribe => File["/etc/munin/plugins"], # ... }}} When adding new snippets to the

Hi, I''m trying to add following iptables rules to shorewall: iptables -I INPUT -d 192.168.1.1 iptables -I OUTPUT -s 192.168.1.1 What should I put in my custom action or any ware else? I need these rules for munin accounting. iptables -L INPUT -v -n -x Chain INPUT (policy DROP 5 packets, 260 bytes) pkts bytes target prot opt in out source destination 7175

Hi all: I see a lot of the errors below in /var/log/messages on my firewall: Aug 1 00:47:44 munin kernel: [109008.257109] martian source 192.168.1.5 from 127.0.0.1, on dev eth1 Aug 1 00:48:44 munin kernel: [109068.257384] martian source 192.168.1.5 from 127.0.0.1, on dev eth1 Aug 1 00:49:44 munin kernel: [109128.257509] martian source 192.168.1.5 from 127.0.0.1, on dev eth1 Aug 1 00:50:44

Hey folks, I'm setting up some kickstart files for our standard configs, and need to install munin-node, which of course does not come from you folks, So I set up the Dag Wieers repository but in the repo file I set it to "disabled" so that it will never get used by mistake. Then when adding munin-node I do : yum --enablerepo=dag -y install munin-node But that pulls in a bunch