Troubleshooting the Orchestration Engine
A newer version is available; see the version menu above for details.
Increasing the ulimit for the
The ulimit controls the number of processes and file handles that the
pe-activemq user can open/process. To increase the ulimit for the
pe-activemq user, edit
/etc/security/limits.conf so that it contains the following:
pe-activemq soft nproc 8192 pe-activemq hard nproc 8192 pe-activemq soft nofile 16384 pe-activemq hard nofile 16384
Accessing the ActiveMQ Console
In some cases, you may need to access the ActiveMQ console to troubleshoot orchestration messages, which are handled by the
pe-activemq service. To do this, you will need to enable the ActiveMQ console from within the PE console by editing the
enable_web_console parameter of the
puppet_enterprise::profile::amq::broker class. The ActiveMQ node can be reached from whichever node has the
To activate the ActiveMQ console:
On the Puppet master, navigate to
jetty.xmlso that the
"host"value of the
"connectors"property is set to
"0.0.0.0", as shown in the following example:
<property name="connectors"> <list> <bean id="Connector" class="org.eclipse.jetty.server.nio.SelectChannelConnector"> <property name="host" value="0.0.0.0"/> <property name="port" value="8161" /> </bean> </list> </property>
From the console, click Nodes > Classification.
PE ActiveMQ Brokergroup.
puppet_enterprise::profile::amq::brokerclass, set the
Click Add parameter, and then click the Commit change button.
You can reach the the ActiveMQ console from whichever node has the
puppet_enterprise::profile::amq::broker class on port 8161 with
Running a 3.x Master with 2.8.x Agents is not Supported
3.x versions of PE contain changes to the MCollective module that are not compatible with 2.8.x agents. When running a 3.x master with a 2.8.x agent, it is possible that Puppet will still continue to run and check into the console, but this means Puppet is running in a degraded state that is not supported.