As I've gotten to the point of configuring server.cfg and client.cfg, based on the documentation in Pro Puppet (which also references use of RPMs), it seems we have some configuration issues -- perhaps about standards of where things need to be located.
The book refers to a non-existent directory, /usr/share/mcollective/ plugins. The RPMs create /etc/mcollective/plugin.d (empty). Thus, when you start the server, it fails with the following errors: E, [2011-06-28T16:16:19.419481 #25040] ERROR -- : pluginmanager.rb: 111:in `loadclass' Failed to load Mcollective::Facts::Yaml_facts: no such file to load -- mcollective/facts/yaml_facts.rb E, [2011-06-28T16:16:19.419708 #25040] ERROR -- : pluginmanager.rb: 111:in `loadclass' Failed to load Mcollective::Connector::Stomp: n o such file to load -- mcollective/connector/stomp.rb E, [2011-06-28T16:16:19.419891 #25040] ERROR -- : pluginmanager.rb: 111:in `loadclass' Failed to load Mcollective::Security::Psk: no s uch file to load -- mcollective/security/psk.rb E, [2011-06-28T16:16:19.420036 #25040] ERROR -- : pluginmanager.rb: 111:in `loadclass' Failed to load Mcollective::Registration::Agent list: no such file to load -- mcollective/registration/agentlist.rb I, [2011-06-28T16:16:19.420433 #25040] INFO -- : mcollectived:31 The Marionette Collective 1.2.0 started logging at info level I could be mistaken. What's missing? -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
