Issue #6741 has been updated by R.I. Pienaar. Status changed from Accepted to Closed
5f52e8f (3 files in 2 dirs): http://bit.ly/gWOaKi ---------------------------------------- Bug #6741: bad server.cfg and client.cfg in 1.1.3 https://projects.puppetlabs.com/issues/6741 Author: Matthew Cashdollar Status: Closed Priority: Normal Assignee: R.I. Pienaar Category: Packaging Target version: 1.1.4 Keywords: topic config Branch: Affected mCollective version: I am upgrading from 1.1.0 to 1.1.3. I noticed that the server.cfg/client.cfg is still in the old non-subcollective format... from the top of the file: <pre>topicprefix = /topic/mcollective libdir = /usr/libexec/mcollective logfile = /var/log/mcollective.log loglevel = info daemonize = 1</pre> According to the backwards compatibility section in the release notes for 1.1.3, this is still supposed to work. However, it gives me a bad topic name when I try to run it: <pre>D, [2011-03-16T18:22:06.210867 #17399] DEBUG -- : mcollectived:39 Starting in the background (true) D, [2011-03-16T18:22:06.219730 #17402] DEBUG -- : pluginmanager.rb:73:in `[]' Returning plugin global_stats with class MCollective::RunnerStats D, [2011-03-16T18:22:06.220359 #17402] DEBUG -- : pluginmanager.rb:73:in `[]' Returning plugin global_stats with class MCollective::RunnerStats D, [2011-03-16T18:22:06.220509 #17402] DEBUG -- : pluginmanager.rb:73:in `[]' Returning plugin security_plugin with class MCollective::Security::Psk D, [2011-03-16T18:22:06.220681 #17402] DEBUG -- : pluginmanager.rb:73:in `[]' Returning plugin connector_plugin with class MCollective::Connector::Stomp D, [2011-03-16T18:22:06.220853 #17402] DEBUG -- : stomp.rb:83:in `connect' Connecting to puppet.dev.orbitz.net:6163 D, [2011-03-16T18:22:06.258489 #17402] DEBUG -- : agents.rb:16:in `loadagents' Reloading all agents from disk D, [2011-03-16T18:22:06.258752 #17402] DEBUG -- : agents.rb:64:in `findagentfile' Found discovery at /usr/libexec/mcollective/mcollective/agent/discovery.rb D, [2011-03-16T18:22:06.258882 #17402] DEBUG -- : pluginmanager.rb:83:in `loadclass' Loading MCollective::Agent::Discovery from mcollective/agent/discovery.rb D, [2011-03-16T18:22:06.259410 #17402] DEBUG -- : pluginmanager.rb:36:in `<<' Registering plugin discovery_agent with class MCollective::Agent::Discovery D, [2011-03-16T18:22:06.260375 #17402] DEBUG -- : pluginmanager.rb:73:in `[]' Returning plugin connector_plugin with class MCollective::Connector::Stomp D, [2011-03-16T18:22:06.260486 #17402] DEBUG -- : stomp.rb:156:in `subscribe' Subscribing to /topic/mcollectivemcollective.discovery.command</pre> As you can see it has mcollective twice in the topic. To fix the problem, I just switched my configs to use the subcollective style of config, but I think it is confusing. It causes activemq security errors. The file in your git repo etc/server.cfg.dist still has the old style as well (I am using the RPMs). -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
