failed to submit 'replace facts' command for puppetmaster.domain.com to puppetDB

[Kamjar Gerami]

Hello,

I have a separate
1. master running apache+passenger,
2. puppetDB on a separate server running postgresql
3. dashboard on a separate server.

Total of 3 servers - Master, puppetdb. dashboard.

This is the error message I get when I run puppet agent from any of the servers.

## I have changed the hostnames in the output below ##

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for puppetmaster.domain.com to PuppetDB at puppetDB.domain.com:8081: [400 Bad Request] Missing required query parameter 'payload'
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

[server ~]# nc -v puppetdb.domain.com 8081
Connection to puppetdb.domain.com 8081 port [tcp/tproxy] succeeded!

From the messages file on the master (after I've run puppet agent -t --noop --debug) I see this :


May 21 10:55:23 <3.3> puppetmaster.domain.com puppet-agent[8158]: (/File[/var/lib/puppet/lib]) Failed to generate additional resources using 'eval_generate': Connection refused - connect(2)
May 21 10:55:23 <3.3> puppetmaster.domain.com puppet-agent[8158]: (/File[/var/lib/puppet/lib]) Could not evaluate: Could not retrieve file metadata for puppet://puppetdb.domain.com/plugins: Connection refused - connect(2)
May 21 10:55:23 <3.3> puppetmaster.domain.com puppet-agent[8158]: (/File[/var/lib/puppet/lib]) Wrapped exception:
May 21 10:55:23 <3.3> puppetmaster.domain.com puppet-agent[8158]: (/File[/var/lib/puppet/lib]) Connection refused - connect(2)
May 21 10:55:23 <3.3> puppetmaster.domain.com puppet-agent[8158]: Could not retrieve catalog from remote server: Connection refused - connect(2)
May 21 10:55:23 <3.5> puppetmaster.domain.com puppet-agent[8158]: Using cached catalog
May 21 10:55:23 <3.6> puppetmaster.domain.com puppet-agent[8158]: Applying configuration version '1399548635'
May 21 10:55:23 <3.5> puppetmaster.domain.com puppet-agent[8158]: Finished catalog run in 0.02 seconds
May 21 10:55:23 <3.3> puppetmaster.domain.com puppet-agent[8158]: Could not send report: Connection refused - connect(2)

the /var/lib/puppet/lib directory is empty on both the master and the puppetdb server.


Please let me know what configurational files you require to help me solve this issue.

Thank you.

[Ken Barber]

This is almost always because you've upgraded the terminus to 2.0.0,
but the PuppetDB instance has not been upgraded properly - this could
be because you haven't installed the package, or the process has not
restarted correctly.

If you believe you've installed the puppetdb 2.0.0 package correctly
... try restarting the process for PuppetDB, forcefully if you have to
and attempt to restart with 2.0.0.

ken.

> --
> 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/869f0625-b870-4f5f-bfb8-85560c244fa8%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Kamjar Gerami]

Thank you for the reply Ken,

This is what my PuppetDB is running :

rpm -qa | grep puppet

puppet-3.5.1-1.el6.noarch
puppetdb-1.6.3-1.el6.noarch
puppetdb-terminus-1.6.3-1.el6.noarch


This is what my master is running :

pm -qa | grep puppet
puppetlabs-release-6-10.noarch
puppet-server-3.5.1-1.el6.noarch
puppetdb-terminus-2.0.0-1.el6.noarch
puppet-3.5.1-1.el6.noarch

Thank you - I will try to upgrade and see if that resolves my issues.

[Kamjar Gerami]

I've upgraded and made a few changes to my config.ini and database.ini file to reflect the new logging path for logback.xml  etc...

More info can be found here in the release notes:

https://github.com/puppetlabs/puppetdb/blob/stable/documentation/release_notes.markdown


it works now! Thank you very much!