Problem with load balanced puppetdb

[Angel L. Mateo]

Hello,

I have a farm of two puppetdb servers (4.1.2-1) installed from PC1
puppetlabs repository. These two servers are ubuntu 14.04 and they are
behing a load balancer.

The problem I'm having is that some resources are not correctly updated
after a change in the client catalogs.

Looking for something wrong in the database I have found some entries
in catalog_resources table with incorret certname_id. That is, a
resource in a node catalog is in the database with the certname_id field
of another different node.

Could this be related some strange kind of issue with load balancing?

Any help?

--
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información
y las Comunicaciones Aplicadas (ATICA)
http://www.um.es/atica
Tfo: 868887590
Fax: 868888337

[Molly Waggett]

Hi Angel,

Could you provide more information about your setup? Specifically, how are you replicating data between your PuppetDBs?

Thanks!

--
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/577B8B55.7030305%40um.es.
For more options, visit https://groups.google.com/d/optout.

[Angel L. Mateo]

El 05/07/16 a las 20:00, Molly Waggett escribió:

> Hi Angel,
>
> Could you provide more information about your setup? Specifically, how
> are you replicating data between your PuppetDBs?
>

They both use the same database, so I don't replicate data. I don't
have HA postgresql server, it is server by just one.

Besides this, puppetdb configuration is done with puppetlabs/puppetdb
module (v5.1.2) which its default options.

[Angel L. Mateo]

Looking deeper... I have been using puppetdb 2.3.x until a few days.
The problem I found after upgrading to puppetdb 4.1.2 and I didn't
realize that tables for catalog entries have changed. In puppetdb 2.3.x
catalog_resources and catalogs tables where directly related with the id
of the catalog entry, but now they are related with the latest_catalog
table. Now all make sense.

El 06/07/16 a las 08:18, Angel L. Mateo escribió:

[Molly Waggett]

Angel,

Glad your issue seems to have been resolved. Let us know if you have any more questions.

--
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/577CB3C9.40907%40um.es.