puppet master stopped loading facts since puppetdb installation

256 views
Skip to first unread message

cko

unread,
Dec 17, 2013, 11:56:55 AM12/17/13
to puppet...@googlegroups.com
hey,

so i just installed puppetdb on a dedicated server (with pgsql).

I noticed that the puppet master server doesn't load any facts.

root@puppetmaster:~$ puppet agent -t
Info: Retrieving plugin
Info: Caching catalog for puppetmaster.local.domain
Info: 'replace catalog' command for puppetmaster.local.domain submitted to PuppetDB with UUID 87de0ebc-1543-4b8a-8434-ca9220238fda
Info: Applying configuration version '1387297065'
Notice: Finished catalog run in 20.88 seconds

Is this intended? Or did i miss something while installing and connecting puppetDB?

Deepak Giridharagopal

unread,
Dec 17, 2013, 6:13:09 PM12/17/13
to puppet...@googlegroups.com
On Dec 17, 2013, at 9:56 AM, cko <der...@gmail.com> wrote:

hey,

so i just installed puppetdb on a dedicated server (with pgsql).

I noticed that the puppet master server doesn't load any facts.

What do you mean "doesn't load any facts"? What is the problem you're seeing?


root@puppetmaster:~$ puppet agent -t
Info: Retrieving plugin
Info: Caching catalog for puppetmaster.local.domain
Info: 'replace catalog' command for puppetmaster.local.domain submitted to PuppetDB with UUID 87de0ebc-1543-4b8a-8434-ca9220238fda
Info: Applying configuration version '1387297065'
Notice: Finished catalog run in 20.88 seconds

Is this intended? Or did i miss something while installing and connecting puppetDB?

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/18ad2d51-9259-4abb-97a4-5b28bd77eee0%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

cko

unread,
Dec 18, 2013, 2:27:54 AM12/18/13
to puppet...@googlegroups.com
Every node (except for the master) does something like this when i run "puppet agent -t":


root@node1:~$ puppet agent -t
Info: Retrieving plugin
Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/environment.rb
Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ssh_hostkey_localhost.rb
Info: Loading facts in /var/lib/puppet/lib/facter/fsecure_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables_persistent_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb

Info: Caching catalog for node1.local.domain
Info: Applying configuration version '1386350341'
Notice: Finished catalog run in 25.51 seconds
 
The puppet master however doesn't.

An example on how this affects the functionality:

I use a template that manages the /etc/motd file.
It contains the fact "kernelrelease". Meaning after i update the kernel on the master, this information is supposed to be updated. (I'm still talking about the master server, every other nodes works as expected!)
But since the master doesn't load facts on a run, the motd file doesn't get updated.

Erik Dalén

unread,
Dec 19, 2013, 7:41:13 AM12/19/13
to puppet...@googlegroups.com
Sounds like there could be something wrong with your routes.yaml file. Does it look like this example? http://docs.puppetlabs.com/puppetdb/latest/connect_puppet_master.html#edit-routesyaml



For more options, visit https://groups.google.com/groups/opt_out.



--
Erik Dalén

cko

unread,
Dec 19, 2013, 8:58:02 AM12/19/13
to puppet...@googlegroups.com
Yes, ist looks exactly like this.

cat /etc/puppet/routes.yaml
---
master:
  facts:
    terminus: puppetdb
    cache: yaml

cko

unread,
Mar 3, 2014, 4:35:35 PM3/3/14
to puppet...@googlegroups.com
I'm still having these issues. 

Here is some output that might help:


Any ideas?

Ryan Senior

unread,
Mar 4, 2014, 2:52:20 PM3/4/14
to Puppet Users
Can you post your puppet.conf? Should be in /etc/puppet, also the versions of puppet/puppetdb/facter packages?

If you want to drop into freenode #puppet IRC channel, we can troubleshoot this more in real time. I'm rsenior there.


--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

cko

unread,
Mar 4, 2014, 3:10:16 PM3/4/14
to puppet...@googlegroups.com
The /etc/puppet/puppet.conf looks like this:

[main]
   logdir = /var/log/puppet
   rundir = /var/run/puppet
   ssldir = $vardir/ssl
   pluginsync = true
   storeconfigs = true
   storeconfigs_backend = puppetdb

[live]
   modulepath = /etc/puppet//modules/live
   manifest = /etc/puppet/manifests/live/site.pp

[test]
   modulepath = /etc/puppet/modules/test
   manifest = /etc/puppet/manifests/test/site.pp

[dev]
   modulepath = /etc/puppet/modules/dev
   manifest = /etc/puppet/manifests/dev/site.pp

[sandbox]
   modulepath = /etc/puppet/modules/sandbox
   manifest = /etc/puppet/manifests/sandbox/site.pp

[agent]
   environment = live
   classfile = $vardir/classes.txt
   localconfig = $vardir/localconfig
   report = true
   runinterval = 1800
   archive_files = true

[master]
   reports = http, puppetdb
   certname = puppet.local.domain
   dns_alt_names = puppet,puppet.local.domain
   ssl_client_header = SSL_CLIENT_S_DN
   ssl_client_verify_header = SSL_CLIENT_VERIFY

puppetversion: 3.4.3
facterversion: 1.7.5
puppetdb: 1.6.2

Another Error i just noticed on my puppet master (maybe this is connected):

$ puppet resource package puppet
Error: Could not run: undefined method `prune_parameters' for nil:NilClass


(I'm cko in #puppet)

Ryan Senior

unread,
Mar 4, 2014, 5:40:22 PM3/4/14
to Puppet Users
I think the problem is the following two lines:

storeconfigs = true
storeconfigs_backend = puppetdb

Those need to be in the [master] section. When it's in [main], it applies both the agent and the master on that box. You only want that to apply to the master.

-Ryan


cko

unread,
Mar 5, 2014, 2:19:19 AM3/5/14
to puppet...@googlegroups.com
This was indeed the problem.

Thank you, Ryan!

Ryan Anderson

unread,
Mar 5, 2014, 6:38:40 AM3/5/14
to puppet...@googlegroups.com
I'm not knocking on the gentleman with this issue, but I would like to helpfully recommend installing puppetdb via Puppet Labs' free puppetdb module. It takes care of such things for you, just my $.02.
Reply all
Reply to author
Forward
0 new messages