Decommission puppetdb

88 views
Skip to first unread message

David Thompson

unread,
Jan 8, 2014, 5:17:20 PM1/8/14
to puppet...@googlegroups.com
I'm trying to decommission puppetdb, but it's being very persistent.  I've removed the puppetdb-terminus rpm, and commented out the storeconfigs entries in puppet.conf, but the managed systems can't apply without puppetdb running on the server.  The error messages are:

Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: Error 400 on SERVER: Could not retrieve facts for medusa.keck.waisman.wisc.edu: Failed to find facts from PuppetDB at puppetdb:8081: Connection refused - connect(2)

...and...

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for medusa.keck.waisman.wisc.edu to PuppetDB at puppetdb:8081: Connection refused - connect(2)
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Anyone know the rest of the magic sauce to make a managed system *not* talk to puppetdb?

Deepak Giridharagopal

unread,
Jan 8, 2014, 5:28:05 PM1/8/14
to puppet...@googlegroups.com
On Wed, Jan 8, 2014 at 3:17 PM, David Thompson <dtho...@waisman.wisc.edu> wrote:
I'm trying to decommission puppetdb, but it's being very persistent.  I've removed the puppetdb-terminus rpm, and commented out the storeconfigs entries in puppet.conf, but the managed systems can't apply without puppetdb running on the server.

Do you still have a routes.yml file that references puppetdb?
 
  The error messages are:

Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: Error 400 on SERVER: Could not retrieve facts for medusa.keck.waisman.wisc.edu: Failed to find facts from PuppetDB at puppetdb:8081: Connection refused - connect(2)

...and...

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for medusa.keck.waisman.wisc.edu to PuppetDB at puppetdb:8081: Connection refused - connect(2)
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Anyone know the rest of the magic sauce to make a managed system *not* talk to puppetdb?

I'm not 100% sure what you mean by "managed system", but unless you're using it with "puppet apply" the only systems that talk to PuppetDB are your puppetmasters. Agents never talk to it directly.

deepak
 


--
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/5a7abd23-45ab-41b7-9022-7f5c3cf1360b%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Jose Luis Ledesma

unread,
Jan 8, 2014, 5:34:11 PM1/8/14
to puppet...@googlegroups.com
Remove also /etc/puppet/puppetdb.conf
Reply all
Reply to author
Forward
0 new messages