similar to: nodes cannot retrieve catalog after installing puppet-dashbaord

I have a puppet master install which uses puppetdb. I also have puppet dashboard installed with the inventory service running. I want multiple puppet masters using a single puppetDB server. Puppetdb is installed on separate vm. How can I get the dashboard inventory to use the puppetdb server to get the inventory records? Where do I configure the dashboard inventory so it uses puppetdb? I

Hi, Has anyone had success getting the Inventory Service running in RHEL 6? My Puppet Nodes are getting the following error: > [root@puppetnode-01 ~]# puppetd --debug --verbose --no-daemonize > ... > err: Could not retrieve catalog from remote server: Error 400 on SERVER: > Could not autoload inventory_active_record: uninitialized constant > ActiveRecord > ...

>Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find terminus puppetsvr for indirection catalog I had a working puppet install (new) with 2 agents working well. I added puppet dashboard and the inventory part which is also working well. However, clients are talking to the server (putting info into dashboard inventory), but not pulling down the

Hello Puppet list, I am taking over the puppet configuration of a sysadmin who left, and am having troubles deploying puppet to a new node. We are using puppet v2.7.3 both on the client and the puppetmaster, on Ubuntu 10.10. The node asks for a certificate fine, and I signed it on the puppetmaster. For the following logs extract I ve replaced the FQDN of my node by puppet.example.com. When doing

I am getting the following error when executing puppet agent --test from the node to force it to get its node definition [root@localhost puppet]# puppet agent --test Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Failed to find puppetnode.localdomain via exec: Execution of ''/etc/puppet/snc_enc.py

Hi, I have noticed that when a typo is introduced or a module is plain broken, puppet will run using a cached catalog. This is logged as an error on the local client, however, it is not logged as an error on Puppet Dashboard. How can I change this behavior, so that using the cached catalog will result in a warning/error being displayed on Puppet Dashboard? Foreman does this. I''ve

I had a working puppet server and added the Dashboard. Then I got the inventory part of dashboard working. Now I''ve got what looks like one last error I can''t get past: > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find terminus mabospuppet01 for indirection catalog Any idea what this means or where I can get better error

Hi, Since this morning all nodes are showing as unresponsive. I have faced a similar error before and the problem was fixed restarting the dashboard-workers as there were many pending task in the puppet dashboard. I am using Puppet Enterprise 2.7.1 version. I have already checked/done: * Restarted the puppetmaster server * Check that puppet-dashboard-workers are working * Time is synced

Hello, Just kicking the tyres with PuppetDB (1.1.0) on a test setup with 100-odd nodes running only once an hour by default. Looking at the dashboard the catalog duplication is showing 0.0% which seems a little odd to me. Any way to track down why this is and how to correct it as presumably this is not desired behaviour. Cheers Paul -- You received this message because you are subscribed

Greetings, I have a tested, working setup of Puppet and Webrick. I can add nodes, classes, etc. Then I switched to Puppet/Passenger and get the error below. Puppet, Apache and Passenger are all up. I have installed using *YUM *repos and *GEMs*. So, I have the most updated packages they have. Puppet version: 2.7.19 Ruby version: 1.8.7 (2011-06-30 patchlevel 352 i386) Apache: 2.2.15 The error

Just installed the puppet master server in and the client just installed the puppet I managed to sign the certificates root@Puppetmaster:/etc/puppet# puppet cert --list --all + "puppetclient" (96:9A:C3:8D:B6:72:A4:5F:01:AA:40:A9:95:3E:FB:D2) + "puppetmaster" (12:92:DF:EB:72:E5:DF:99:D8:22:CA:5F:22:3A:1D:61) at the time I create the file site.pp in / etc / puppet / manifests

Hello all, I''m running puppet for the first ime. I''ve finished the install but I''m stuck at the certificate part. The puppet master (0.24.4-3) is running on Ubuntu Lenny and the puppet client (0.24.8-4.el5) is running on CentOS 5.3. After the install, from the client side, I''ve run: puppetd --server puppetmaster.domain.com --waitforcert 60 --test On the

Hello, I''m trying to get puppet-dashboard installed on a CentOS 6.3 machine running puppet v3.0.1. I''m following the puppet-dashboard documentation here: http://docs.puppetlabs.com/dashboard/manual/1.2/configuring.html In the documentation page linked above, it says: Puppet uses SSL certificates to control who can make requests to the puppet > master, so Dashboard has

I have followed many tutorials including the ones provided by puppetlabs and I keep seeing the same issues. I began by installing puppet on machine: puppet001, and puppet master on machine: puppetMaster. The hosts files were then configured so that both machines were reachable by the machine name. The puppet.conf files were then updated, and a cert was generated and sent from puppet001 to

So set up new node, ran on the client puppetd --server puppetmaster --waitforcert 60 --test on the puppetmaster itself I ran puppetca --list saw the hostname and then ran: puppetca --sign hostname.domain.com and on the puppet node itself I went back and ran puppetd -tv and get the following error: err: Could not retrieve catalog from remote server: certificate verify failed warning: Not

After upgrading my puppet master to 2.6.8 from 2.6.2, I intermittently get things like: puppet-master[29789]: (Scope(Class[Auth::Kerberos_ldap])) Could not look up qualified variable ''common::datacenter::ldap::ldapservers''; class common::datacenter::ldap has not been evaluated puppet-master[29789]: Failed to parse template auth/rhel5/ ldap.conf.erb: undefined method

Hi All, For some reason my puppet dashborad is not starting and new node requests are not displaying in dashboard. I am getting following error while restarting Puppet dashboard. root@PuppetMaster:/etc/puppetlabs/puppet/modules# /etc/init.d/pe-puppet-dashboard-workers start * Starting PE Puppet Dashboard Workers

Hi All, Puppet-dashboard appears to be having some trouble. Under inventory, it says: "Could not retrieve facts from inventory service: Permission denied - certs/dashboard.private_key.pem" When I run: curl -k -H "Accept: yaml" https://puppet:8140/production/facts/host.domain I get the expected dump of facts. Versions: puppet-dashboard is 1.1.0 (using passenger) puppet-master

Dear all, I want to have a view of lxc CPU usage in openstack Dashboard. According the Openstack official site , Openstack Ceilometer can poll libvirt daemon to obtain CPU usage of a virtual machine. I tried the command locally on the libvirtd host "virsh -c lxc:/// domjobinfo", I got an error "error: this function is not supported by the connection driver:

Almost 4-5% of the total number of nodes are not receiving catalog from the master on an hourly run. We have about 250 nodes. The nodes that are receiving this error are rather random. The hourly cron happens almost at the same time. Is there any configuration changes for Puppet that can be done to avoid this ? Puppet (err): Could not retrieve catalog from remote server: execution expired