我刚刚在Ubuntu 10.04 LTS上使用puppet-enterprise-2.0-ubuntu-10.04-amd64.tar.gz（从http://puppetlabs.com/misc/pe-files/下载）安装PE，现在也一样机器正在运行主控，控制台和代理angular色。
我似乎有一个MCollective服务器的问题，即使它似乎开始罚款，不会打开端口61613，因为它应该。
守护从头开始
$ sudo /etc/init.d/pe-mcollective start * Starting mcollective daemon [ OK ] 显示是PS
$ ps aux | grep mcol | grep -v grep root 25636 0.0 0.5 64680 12056 ? S 07:21 0:00 /opt/puppet/bin/ruby /opt/puppet/sbin/mcollectived --pid /var/run/pe-mcollective.pid
Pid文件包含正确的值
$ sudo cat /var/run/pe-mcollective.pid 25636
但是我没有看到任何进程侦听端口61613
$ sudo netstat -lntp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 2395/mysqld tcp 0 0 127.0.0.1:11211 0.0.0.0:* LISTEN 25542/memcached tcp 0 0 0.0.0.0:8140 0.0.0.0:* LISTEN 25620/pe-httpd tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 10096/apache2 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2345/sshd tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2822/master tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 25620/pe-httpd
当我查看日志时，我在集体服务器和客户端日志中看到错误
$ sudo tail -f /var/log/pe-*/* ==> /var/log/pe-puppet-dashboard/mcollective_client.log <== I, [2011-12-20T07:26:22.731870 #30944] INFO -- : stomp.rb:79:in `on_connectfail' Connction to stomp://[email protected]:61613 failed on attempt 1646 ==> /var/log/pe-mcollective/mcollective.log <== I, [2011-12-20T07:26:24.852641 #25636] INFO -- : stomp.rb:79:in `on_connectfail' Connction to stomp://[email protected]:61613 failed on attempt 20
当我检查mcollective ruby脚本/ opt / puppet / sbin / mcollectived时，我可以看到它引用了configuration文件/etc/puppetlabs/mcollective/server.cfg，它具有以下configuration指令：
plugin.stomp.pool.size = 1 plugin.stomp.pool.host1 = puppetmaster.example.org plugin.stomp.pool.port1 = 61613 plugin.stomp.pool.user1 = mcollective plugin.stomp.pool.password1 = *************** plugin.stomp.pool.ssl1 = true plugin.stomp.base64 = true
我可以解决plugin.stomp.pool.host1 ，如果我更改plugin.stomp.pool.port1到61614我看到它反映在上面提到的mcollective.log错误。 我设置loglevel =debugging，但它不给我更多的提示。 我手动运行了脚本（/ opt / puppet / bin / ruby / opt / puppet / sbin / mcollectived），但是它也不给我任何线索。
问：如何进一步解决此问题？
这个问题是与Java密钥库：
pe-activemq起步良好
$ sudo /etc/init.d/pe-activemq start * pe-activemq started
但是通过看PS我注意到activemq试图启动，但几乎立即失败。 我修改了启动脚本来做一些debugging：
start() { echo -n "Starting $APP_NAME... " getpid if [ "X$pid" = "X" ] then # original command # COMMAND_LINE="$CMDNICE $WRAPPER_CMD $WRAPPER_CONF wrapper.syslog.ident=$APP_NAME wrapper.pidfile=$PIDFILE wrapper.daemonize=TRUE $ANCHORPROP $IGNOREPROP $LOCKPROP" # custom command with deamonize=FALSE COMMAND_LINE="$CMDNICE $WRAPPER_CMD $WRAPPER_CONF wrapper.syslog.ident=$APP_NAME wrapper.pidfile=$PIDFILE wrapper.daemonize=FALSE $ANCHORPROP $IGNOREPROP $LOCKPROP" echo "executing [$COMMAND_LINE]"
启动pe-activemq给出了以下错误
jvm 1 | ERROR | Failed to start ActiveMQ JMS Message Broker. Reason: java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: stomp+ssl://0.0.0.0:61613 due to: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.DefaultSSLContextImpl)
这看起来像是一个密钥库的问题。 /opt/puppet/activemq/conf/activemq-wrapper.confconfiguration文件为您提供了以下详细信息：
set.default.ACTIVEMQ_BASE=/opt/puppet/activemq wrapper.working.dir=/var/log/pe-activemq [...] # Enable SSL of the Stomp Connection (Note, this provides encryption only as per #10596) wrapper.java.additional.7=-Djavax.net.ssl.keyStorePassword=puppet wrapper.java.additional.8=-Djavax.net.ssl.keyStore=%ACTIVEMQ_BASE%/conf/broker.ks # The trust store need not be present. wrapper.java.additional.9=-Djavax.net.ssl.trustStorePassword=puppet wrapper.java.additional.10=-Djavax.net.ssl.trustStore=%ACTIVEMQ_BASE%/conf/broker.ts
FYI / opt / puppet / activemq / conf是/ etc / puppetlabs / activemq的符号链接在该目录中，broket.ts文件存在，但broker.ks文件丢失
基于这个页面（ http://activemq.apache.org/how-do-i-use-ssl.html ），我做了以下
$ cd /etc/puppetlabs/activemq $ sudo keytool -genkey -alias broker -keyalg RSA -keystore broker.ks => provided puppet password everywhere
然后activemq开始罚款
jvm 1 | INFO | Using Persistence Adapter: KahaDBPersistenceAdapter[/opt/puppet/activemq/data/kahadb] jvm 1 | INFO | KahaDB is version 3 jvm 1 | INFO | Recovering from the journal ... jvm 1 | INFO | Recovery replayed 1 operations from the journal in 0.022 seconds. jvm 1 | INFO | ActiveMQ 5.5.0 JMS Message Broker (localhost) is starting jvm 1 | INFO | For help or more information please see: http://activemq.apache.org/ jvm 1 | INFO | Installing StaticsBroker jvm 1 | INFO | Starting StatisticsBroker jvm 1 | INFO | Listening for connections at: tcp://myserver:61616 jvm 1 | INFO | Connector openwire Started jvm 1 | INFO | Listening for connections at: stomp+ssl://myserver:61613 jvm 1 | INFO | Connector stomp+ssl Started jvm 1 | INFO | ActiveMQ JMS Message Broker (localhost, ID:myserver-44300-1324455724257-0:1) started jvm 1 | INFO | jetty-7.1.6.v20100715 jvm 1 | INFO | ActiveMQ WebConsole initialized. jvm 1 | INFO | Initializing Spring FrameworkServlet 'dispatcher' jvm 1 | INFO | ActiveMQ Console at http://0.0.0.0:8161/admin jvm 1 | INFO | WebApp@2109578614 at http://0.0.0.0:8161/camel jvm 1 | INFO | WebApp@2109578614 at http://0.0.0.0:8161/demo jvm 1 | INFO | WebApp@2109578614 at http://0.0.0.0:8161/fileserver jvm 1 | INFO | Started [email protected]:8161
问题解决了
守护进程不听，守护进程连接到中间件节点，在你的情况puppetmaster.example.com:61613应该有ActiveMQ运行，
如果您需要更多帮助，请将问题提交到群组邮件列表http://groups.google.com/group/mcollective-users