Unfortunately, for me all this does is make the puppet-master host go 100%
busy between the dashboard and mysqld.
I am running Dashboard version 1.2.23 with puppet-server version 3.2.4 and
mysql version 5.1.69 on RHEL 6.4
I get the same result running John's cli rake command.
Any ideas?
Than
I have 39 RHEL nodes running the puppet agent and intermitently from 1 to 3
nodes will go unresponsive and require intervention to become active again.
I collected the following for one such instance from this morning:
Hung Puppet agent information:
[root@anmvwms3 ~]# rpm -qa | grep puppet
pupp
rd?
>
>
> On Mon, Dec 10, 2012 at 12:08 PM, MasterPO
> > wrote:
>
>> I don't know what is causing this, but the HOME page for the Puppet
>> Dashboard has a table of nodes offset to the extreme right of the display.
>> Am I missing some configuration parame
I am running RHEL 6 64bit using the puppetlabs yum repositories.
I have it configured to run the Puppet Console against port 3000 and The
Foreman against port 3030 using passenger.
When I installed the upgrade to puppetmaster 3.0, both the Puppet Cosole
stopped working and rails/passenger broke
