Ubuntu – Can’t access node from puppet dashboard

puppetpuppet-dashboardUbuntu

I am trying to setup puppet's dashboard to be monitor the status of my servers. With the below shown configurations, my clients (or nodes) only show up as Unreported and says Has not reported in "Last report".

However the node can communicate with the server and pull changes as it's supposed to, but nothing appears in the dash. I have followed these docs trying to set it up, but I have no idea of what I am doing wrong.

Have I missed anything obvious?

// Server /etc/puppet/puppet.conf
[master]
reports = store,http
reporturl = http://192.168.1.101:3000/reports/upload

// Client /etc/puppet/puppet.conf
[agent]
report = true

Best Answer

It was not clear to me that I had to also add workers to process my incoming reports. By doing this I've managed to get it all working:

env RAILS_ENV=production script/delayed_job -p dashboard -n 4 -m start

http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html

Related Solutions

Puppet-dashboard: Could not retrieve facts from inventory service

my config has the following...

path /facts
auth any
allow *

path /fact
auth any
allow *

path /facts_search
allow *

I think also I had to create an empty file called namespaceauth.conf like so;

touch /etc/puppet/namespaceauth.conf

Referencing groups/classes from Puppet dashboard in the site manifest

You are on the right track with the External Node Classifier. It is a bit difficult to wrap your head around, but one you get it working you will never look back and I cannot recommend doing it strongly enough. I went to the puppet IRC room when i had trouble and they helped me get mine working.

Applying different modules based on OS is fine. I run a 300+ node environment with BSD and RHEL and we do it. Instead of having the the OS be a node, we have it as own class because . So instead of "node OS inherits basenode", we do have the ENC pass back something like this:
```
node web-prod-007 {
  $node_environment="production"
  include web_server_class # this then inherits basenode
  include centos6::server # 
  include logging::rsyslog 
}
```
...etc

how you do it depends on how you want your inheritance to work, if you want to modify the things in basenode depending on operating system, then having OS inherit basenode is the right way to go.

TLDR, what you are doing is okay, and look into ENC's because they make life easier.

EDIT: 2. I dont use Dashboard so I dont know.

Best Answer

Related Solutions

Puppet-dashboard: Could not retrieve facts from inventory service

Referencing groups/classes from Puppet dashboard in the site manifest

Related Topic