Re: [Puppet Users] [PuppetDB] Error 500 'Failed to execute '/pdb/cmd/v1....'

Can you provide the code, you used with puppetdb module? > On 2. Nov 2022, at 08:18, Nir Fishler wrote: > > I tried to configure it using two different methods; > Installing PuppetDB via Puppet module > Installing from packages > neither one of the above had given a complete success. > > On Mon

Re: [Puppet Users] [PuppetDB] Error 500 'Failed to execute '/pdb/cmd/v1....'

I tried to configure it using two different methods; 1. Installing PuppetDB via Puppet module 2. Installing from packages neither one of the above had given a complete success. On Monday, October 31, 2022 at 12:14:31 PM UTC+2 Martin Alfke wrote: > How did you configure puppetdb and pup

Re: [Puppet Users] [PuppetDB] Error 500 'Failed to execute '/pdb/cmd/v1....'

How did you configure puppetdb and puppetserver? On Open Source we usually recommend the puppetlabs-puppetdb module. > On 31. Oct 2022, at 10:39, Nir Fishler wrote: > > Hey Martin, > > Thanks for your reply. > > There are three files underneath that directory: > puppetdb-access.log > puppetd

Re: [Puppet Users] [PuppetDB] Error 500 'Failed to execute '/pdb/cmd/v1....'

Hey Martin, Thanks for your reply. There are three files underneath that directory: - puppetdb-access.log - puppetdb.log - puppetdb-status.log but all seem to be empty - 0kb what does that mean? On Monday, October 10, 2022 at 11:03:05 AM UTC+3 Martin Alfke wrote: > Hi Nir, > > Pl

Re: [Puppet Users] PuppetDB - ERROR [p.p.config] No subname set in the "database" config`

Hi Martin, Following on from your previous reply, I have taken the steps that you have suggested. From here I have received two new errors. I have looked into these and tried finding a solution and working through fixing them. However, I have unfortunately had no success in doing so. I am wonderin

Re: [Puppet Users] PuppetDB - ERROR [p.p.config] No subname set in the "database" config`

Best option is to completely remove the puppetdb service: - stop puppetdb process - uninstall puppetdb Package - remove puppetdb conf dir /etc/puppetlabs/puppetdb Now remove the puppetdb settings from puppet.conf file: - storeconfigs = true - storeconfigs_backend = puppetdb - reports = puppetdb

Re: [Puppet Users] PuppetDB - ERROR [p.p.config] No subname set in the "database" config`

Hi Martin, I am trying to use puppetlabs-puppetdb. This is being installed via my control repository. Unfortunately I am unable to start the service and am running into the errors / issues that I have previously stated. Thank you, Kind regards, Callum McCrorie Junior Engineer/Project Management O

Re: [Puppet Users] PuppetDB - ERROR [p.p.config] No subname set in the "database" config`

Hi Callum, in general we use Puppet to also manage the Puppet Server. Usually we recommend using puppetlabs-puppetdb, which will take care on postgresql and puppetdb and the required settings and even restart puppetserver process. Instead of trying to manually solve an issue, you should automat

Re: [Puppet Users] PuppetDB - ERROR [p.p.config] No subname set in the "database" config`

Thank you Martin for your help with this. I have tried implementing what you suggested above and moving the database config to database.ini. Unfortunately there has been no change of outcome when trying to start puppetdb or when running puppet agent. There is also no new information / entries appea

Re: [Puppet Users] PuppetDB - ERROR [p.p.config] No subname set in the "database" config`

Subname needs the PostgreSQL connection. Not the PuppetDB URL Wrong: subname = //localhost:8081/puppetdb Right: subname = //localhost:5432/puppetdb In my config all the database config is not in config.ini but in database.ini # /etc/puppetlabs/puppetdb/conf/database.ini [database] # The databa

[Puppet Users] PuppetDB - ERROR [p.p.config] No subname set in the "database" config`

Hello, I’m reaching out about an issue related to PuppetDB. I am hoping that someone will be able to assist myself and my coworker in solving this problem. When I take a look inside the puppetdb log file the error that I am seeing is `ERROR [p.p.config] No subname set in the "database" config`. Ro

Re: [Puppet Users] [PuppetDB] Error 500 'Failed to execute '/pdb/cmd/v1....'

Hi Nir, Please check the puppetdb log file for further error investigation. Usually this is located at /var/log/puppetlabs/puppetdb/puppetdb.log Hth, Martin > On 30. Sep 2022, at 10:30, Nir Fishler wrote: > > Hello, > > puppetserver version: 7.8.0 (CentOS 7) | hostname: puppet-staging-srv

[Puppet Users] PuppetDB with postgres

Hi just realised my puppetdb attached to pgsql is configured for latin1 is it okay to stop all puppet services and then export , recreate the database to utf8 and then restart I'm getting these in my log ERROR: character with byte sequence 0xe2 0x80 0x9c in encoding "UTF8" has no equivalent

[Puppet Users] puppetdb ssldir chown is breaking PuppetDB

It seems the puppet agent, when invoked by the service or manually, is resetting the permissions on the files in the puppetdb ssldir (/etc/puppetlabs/puppetdb/ssl/*.pem) from puppetdb:puppetdb to puppet:puppet AND the mode on the mode on the 'private.pem' file to 0640, which means the next tim

[Puppet Users] puppetdb failover - implement ca self signed

Hello everyone. for security reasons. we decided to get 2 puppetdb servers up and running. there will be a setup with *master* and *slave*. We thought of using our load balancer to perform this operation. So we need a *cname* with a valid self-generated certificate. ie: puppetdb.internet.net

[Puppet Users] puppetdb v7 test: no such file to load -- puppet/util/puppetdb

Whilst trying to test a new Puppet v7.0.0 master (which is OK) and PuppetDB, I get the following on PuppetDB: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Internal Server Error: org.jruby.exceptions.LoadError: (LoadError) no such file to load -- puppet/util/puppet

Re: [Puppet Users] PuppetDB and PostgreSQL 12 errors

On Fri, Sep 18, 2020 at 6:29 AM Bob Negri wrote: > So 4 hrs might not be big enough? (Looks like the person who did the > update did not check the documents.) Trying the new settings now. > Yea I don't think 4 hrs is long enough and would cause the behavior you're seeing. In that case when gc fi

Re: [Puppet Users] PuppetDB and PostgreSQL 12 errors

So 4 hrs might not be big enough? (Looks like the person who did the update did not check the documents.) Trying the new settings now. On Thursday, September 17, 2020 at 6:27:29 PM UTC-5 zachar...@puppet.com wrote: > On Thu, Sep 17, 2020 at 8:12 AM Bob Negri wrote: > >> We recently updated our

Re: [Puppet Users] PuppetDB and PostgreSQL 12 errors

On Thu, Sep 17, 2020 at 8:12 AM Bob Negri wrote: > We recently updated our PuppetDB servers to PuppetDB 6.12.0 and PostgreSQL > 12. > Started getting these errors: > > ERROR: relation "resource_events_20200917z" does not exist at character 13 > ERROR: relation "resource_events_20200917z" alread

[Puppet Users] PuppetDB and PostgreSQL 12 errors

We recently updated our PuppetDB servers to PuppetDB 6.12.0 and PostgreSQL 12. Started getting these errors: ERROR: relation "resource_events_20200917z" does not exist at character 13 ERROR: relation "resource_events_20200917z" already exists ERROR: deadlock detected ERROR: could not serializ

[Puppet Users] PuppetDB 6.12.0 and Postgresql 12: ERROR: relation "reports_20200916z" does not exist at character 13

Has anyone see errors like this one? We recently upgraded from Postgresql 9.6 to Postgresql 12 and from PuppetDB 6.7 (I think as I did not do it) to 6.12.0. 2020-09-16 19:24:15.997 UTC [35203] ERROR: relation "reports_20200916z" does not exist at character 13 2020-09-16 19:24:15.997 UTC [35203

Re: [Puppet Users] Puppetdb upgrade - perfomance dashboard blank (mostly)

Hi, This is the manifestation of a bug in PuppetDB (PDB-4855 ). We just merged a fix for that bug and it'll be fixed in the next release. On 8/20/20 1:08 PM, Dave Beedle wrote: After updating puppetdb from v6.7.3 to 6.11.3, the puppetdb dashboar

[Puppet Users] Puppetdb upgrade - perfomance dashboard blank (mostly)

After updating puppetdb from v6.7.3 to 6.11.3, the puppetdb dashboard connects and begins to show data but stops after showing the version number. The version number is correct. All else seems to work. In the log there is: 2020-08-20T20:04:49.049Z WARN [o.e.j.s.HttpChannel] /pdb/dashboard/dat

Re: [Puppet Users] PuppetDB is broken after Debian upgrade to Stretch

I'm unable to reproduce this, can you share the example CURL command you are using that results in this error? On Wed, Aug 19, 2020 at 9:23 AM Eugene Bolshakoff < mercurius.lang...@gmail.com> wrote: > > Hello, > > PuppetDB is partially broken after we upgrade Debian from Jessie to > Stretch. > Pu

[Puppet Users] Puppetdb is broken after update

We updated Debian Jessie to Stretch and Puppetdb from 5.2.9 to 5.2.18. PostgreSQL version remains 9.6 (with a small minor update). After update PuppetDB is partially broken. Puppet works fine with it, but if I try to use API, I get an error: HTTP ERROR 500 Problem accessing /pdb/query/v4/resourc

[Puppet Users] PuppetDB is broken after Debian upgrade to Stretch

Hello, PuppetDB is partially broken after we upgrade Debian from Jessie to Stretch. PuppetDB version has been upgraded from 5.2.9 to 5.2.18. We used "apt-get dist-upgrade" command, no manual setups. Puppet master works fine with Puppetdb. But, if I try to use API via CURL, I got: Problem acce

Re: [Puppet Users] Puppetdb and postgresql module: How to manage Postgresql but NOT manage Postgresql REPO using Hiera?

Hi Martin. I ended up with wrapping everything in my own profile classes and controlling it from there since I need to setup certs, auth, etc. anyway. Thanks. Den lördag 13 juni 2020 kl. 16:43:50 UTC+2 skrev Martin Alfke: > > > postgresql::globals::manage_package_repo: false > postgresql::glob

Re: [Puppet Users] Puppetdb and postgresql module: How to manage Postgresql but NOT manage Postgresql REPO using Hiera?

postgresql::globals::manage_package_repo: false postgresql::globals::version: '9.6', > On 12. Jun 2020, at 17:40, Devminded wrote: > > Hi. > > I am trying to disable the managing of the Postgresql repo using Hiera when > using the puppetlabs/postgresql module. I have tried every Hiera combin

[Puppet Users] Puppetdb and postgresql module: How to manage Postgresql but NOT manage Postgresql REPO using Hiera?

Hi. I am trying to *disable* the managing of the *Postgresql repo* using *Hiera* when using the puppetlabs/postgresql module. I have tried every Hiera combination I can think of (from reading the docs/code) but nothing works. - puppetdb::database::postgresql::manage_package_repo: false -

[Puppet Users] puppetdb "

I upgraded via the Puppet repos from puppetdb-6.9.1-1.el7.noarch (Installed 3/12) to puppetdb-6.10.0-1.el7.noarch today, and restarting puppetdb fails with this error: Your PuppetDB database contains a schema migration numbered 1, but this version of PuppetDB does not recognize that version. Sure

[Puppet Users] PuppetDB : unable to upgrade 6.5 to 6.9 => SSL errors

Hi, I'm struggling with a simple update of PuppetDB since a couple of days, without finding the problem. I have 4 PuppetServers running Puppetserver 6.9 (puppetserver-6.9.0-1.el7.noarch). One has the CA role, the 3 others are simple masters. I have one dedicated PuppetDB server running puppetd

Re: [Puppet Users] PuppetDB latest version has disabled APIv1 metrics

Actually attempting to add the mentioned config to file '/etc/puppetlabs/puppetserver/conf.d/metrics.conf' results in the puppetserver service being unable to start, and this is logged - clojure.lang.ExceptionInfo: Value does not match schema: {:metrics-webservice {:mbeans disallowed-key}} --

Re: [Puppet Users] PuppetDB latest version has disabled APIv1 metrics

Thanks for this info, I think it points in the right direction. Are you able to provide any example config or a link to how to action this? It's not immediately obvious. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this

Re: [Puppet Users] PuppetDB latest version has disabled APIv1 metrics

I believe a config value was added at: metrics.metrics-webservice.mbeans.enabled to match the jolokia one that controls v2. However the default for the mbeans / v1 endpoint is now `false`. Note that this is now the case for Puppet Server as well and can be re-enabled with the same config value in

[Puppet Users] PuppetDB latest version has disabled APIv1 metrics

The latest version of PuppetDB v6.9.1 has removed localhost access to the v1 API metrics. Ref https://puppet.com/security/cve/CVE-2020-7943/ https://puppet.com/docs/puppet/latest/release_notes_puppet.html#puppet-resolved-issues-x.12.0 Given it's only "disabled by default", this suggests there is

Re: [Puppet Users] PuppetDB Using Puppetlabs Postgresql Module on Linux

You need to set it in globals. This is what we do: class { 'postgresql::globals': version => $postgresql_version, datadir => "${postgres_top}/postgresql/data", } John On Wed, 18 Dec 2019 at 01:49, Peter Krawetzky wrote: > I was looking through

[Puppet Users] PuppetDB Using Puppetlabs Postgresql Module on Linux

I was looking through the documentation and couldn't find my answer. I want to use both the PuppetDB and Postgresql supported modules to install and manage both. I don't want to use the default database directory "/var/lib/postgresql/..." but want to specify my own. What do I use to point th

Re: [Puppet Users] puppetdb query return values

Hi Matt, You should be able to do that now that we've finished PDB-2634 , which is available in PuppetDB 6.7.0+. The { } are still required, so a query could look like resources[certname, parameters.address] { type = "Postgresql::Server::Pg_hba_r

[Puppet Users] puppetdb query return values

Greetings, I've looked through the puppetdb docs, in particular the PQL docs, to find out if I can extract a single parameter in the return value(s). I have as a PQL: resources[parameters] { type = "Postgresql::Server::Pg_hba_rule" and parameters.address ~ "."} I'd like to get the "address" par

Re: [Puppet Users] puppetdb 6x not deactivating from catalogs table

Thanks Zachary that doc is a great help. I'll lower the node-purge-ttl and see how it performs. On Friday, 4 October 2019 22:14:04 UTC+1, Zachary Kent wrote: > > Hi Andy, > > Are you seeing the deactivated nodes' catalogs turn up in query results > from PDB or only when you query the postgres ta

Re: [Puppet Users] puppetdb 6x not deactivating from catalogs table

Hi Andy, Are you seeing the deactivated nodes' catalogs turn up in query results from PDB or only when you query the postgres table directly? I'm wondering if you might be hitting some strangeness around the node-purge-ttl setti

[Puppet Users] puppetdb 6x not deactivating from catalogs table

hey there we have just migrated hundreds of hosts from 3.x to 6.x and although lots of work we are almost home and dry but have an issue with puppetdb which I hope can be solved. we are running puppetdb-6.3.4 but when removing an old node as follows: puppet node deactivate the information is

Re: [Puppet Users] PuppetDB 5.2: How to find list of certnames from puppetdb where serverrole is "umg" using API

Hello Austin, Thanks for your reply. The issue is I am trying to return certnames based on server_role which I dont think is a fact, correct me if I am wrong. And since puppet 5.2, we have nested key, values and not sure how do I reach that leaf. Please check the json snippet, if you haven't check

Re: [Puppet Users] PuppetDB 5.2: How to find list of certnames from puppetdb where serverrole is "umg" using API

Apologies in advance if I didn't interpret your query properly, but I believe you are looking to return the certnames of servers that have a specific fact with a specific value, the best endpoint for that would probably be inventory

[Puppet Users] PuppetDB 5.2: How to find list of certnames from puppetdb where serverrole is "umg" using API

PuppetDB version- 5.2 I want to retrieve list of servers with a specific role- tata_umg The json is in below format: [ { "certname":"", "environment":"", "name":"_clientname", "value":{ "clientabc":{ "_productname":{ "t

[Puppet Users] Puppetdb installed with puppetlabs/puppetdb migration 65 failing

Hi all! Added the puppetdb module, runs through and gets stuck on boot with the following error: 2019-06-26 14:20:21,638 INFO [p.p.s.migrate] Applying database migration version 65 2019-06-26 14:20:21,673 ERROR [p.p.s.migrate] Caught SQLException during migration ... 2019-06-26 14:20:21,67

[Puppet Users] PuppetDB failing to start up with bizarre complaint

Using the puppetlabs/puppetdb module to manage PuppetDB I'm seeing way to much red text and PuppetDB is not "refreshing" meaning restarting. It is failing with an error message java.lang.IllegalArgumentException: Specified bootstrap config file does not exist: '/etc/puppetlabs/puppetdb/bootstrap.c

Re: [Puppet Users] PuppetDB exported resources with hiera-eyaml

Thanks for the detailed answer Erik. I was not able to @ you in the github issue as I did not know your username however you seem to have found it alone. Best Jocelyn -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this gr

Re: [Puppet Users] PuppetDB exported resources with hiera-eyaml

On 2019-01-10 10:56, Jocelyn Thode wrote: Hey, I'm trying to use exported resources where one of the parameter of the resource is a variable from hiera. This variable is retrieved using automatic lookup and is encrypted in hiera using hiera-eyaml. However when the ressource is exported inste

[Puppet Users] PuppetDB exported resources with hiera-eyaml

Hey, I'm trying to use exported resources where one of the parameter of the resource is a variable from hiera. This variable is retrieved using automatic lookup and is encrypted in hiera using hiera-eyaml. However when the ressource is exported insted of the clear password being exported, I ge

[Puppet Users] puppetdb - WITH inactive_nodes AS (SELECT certname

Hi, We recently upgraded to puppetdb 4.4. There is query that takes a while to run, 3 or 4 minutes though we are unsure of why it is even running. The query below looks related to some kind of clean up or garbage collection however this particular puppetdb node has two relevant properties:

[Puppet Users] PuppetDB 4.4 API - Getting ALL events (changes and no-changes)

I need to programmatically present all events for a given node from the latest report for audits of server Security Controls we're managing with Puppet - pretty much the way events look in the PE Console when looking at a report - whether the event was a success or not, and whether or not a res

Re: [Puppet Users] PuppetDB: manually import reports

On Wednesday, April 25, 2018 at 6:22:39 AM UTC-5, Thomas Müller wrote: > > > >> >>> >>> Another usecase could be to have a async puppetdb connection from the >>> second datacenter. If the connection between the datacenters is not stable >>> enough to use a single puppetdb I would need to add

Re: [Puppet Users] PuppetDB: manually import reports

> > >> >> Another usecase could be to have a async puppetdb connection from the >> second datacenter. If the connection between the datacenters is not stable >> enough to use a single puppetdb I would need to add a puppetdb per DC.Then >> I also would want to sync data to the central puppet

Re: [Puppet Users] PuppetDB: manually import reports

On 4/19/18 4:46 AM, Thomas Müller wrote: HI I've got some prod puppetserver/puppetdb and some dev puppetserver/puppetdb. But to have the complete overview over all nodes with the prod puppetdb I'd like to import the reports from the dev puppetserver (stored by reports=store config) into the

Re: [Puppet Users] PuppetDB: manually import reports

On Thursday, April 19, 2018 at 2:30:11 PM UTC-5, Thomas Müller wrote: > > > > Am Donnerstag, 19. April 2018 19:18:34 UTC+2 schrieb Christopher Wood: >> >> To challenge an assumption, what are you gaining from having more than >> one puppet infrastructure (puppetservers+puppetdb)? >> >> Could yo

Re: [Puppet Users] PuppetDB: manually import reports

Am Donnerstag, 19. April 2018 19:18:34 UTC+2 schrieb Christopher Wood: > > To challenge an assumption, what are you gaining from having more than one > puppet infrastructure (puppetservers+puppetdb)? > > Could you perhaps handle your dev stuff with another environment or set of > puppetservers

Re: [Puppet Users] PuppetDB: manually import reports

To challenge an assumption, what are you gaining from having more than one puppet infrastructure (puppetservers+puppetdb)? Could you perhaps handle your dev stuff with another environment or set of puppetservers under the same CA with the same puppetdb? Is there any reason for a separate puppet

[Puppet Users] PuppetDB: manually import reports

HI I've got some prod puppetserver/puppetdb and some dev puppetserver/puppetdb. But to have the complete overview over all nodes with the prod puppetdb I'd like to import the reports from the dev puppetserver (stored by reports=store config) into the prod puppetdb. is there some hidden tool t

[Puppet Users] PuppetDB catalog-hash-conflict-debugging substitute

Once upon a time I successfully used catalog-hash-conflict-debugging to find an unsorted thing being different in every catalog and that was very helpful. Recently catalog duplication (in the PuppetDB dashboard) has dropped about 10% and the setting is gone from PuppetDB in 5.2.0. https://ticke

Re: [Puppet Users] PuppetDB Upgrade Question from 2.1.1-1 to 2.7.2-1

Hey Peter, PuppetDB never released a 2.7 series (highest 2.x went was 2.3.x), so it's tough to answer your question specifically. In general, the size of your data (for which number of nodes is a proxy) can definitely have a large effect on migration times, but it largely depends on the specif

[Puppet Users] PuppetDB Upgrade Question from 2.1.1-1 to 2.7.2-1

I'm doing a minor upgrade from 2.1.1-1 to 2.7.2-1 and was wondering if the size of the database makes a difference in how long the upgrade takes? It's currently managing approximately 3200+ nodes in production. Testing in our lab environment did not run long as we only manage about 500 nodes

Re: [Puppet Users] PuppetDB Curl Queries

Best to use PQL via 'puppet query' Examples: https://docs.puppet.com/puppetdb/5.0/api/query/examples-pql.html On Tue, Jul 11, 2017, at 17:48, Peter Krawetzky wrote: > Using CURL to query PuppetDB has got to be the most time consuming thing > I've ever done. It took me almost 3 hours one day to

[Puppet Users] PuppetDB Curl Queries

Using CURL to query PuppetDB has got to be the most time consuming thing I've ever done. It took me almost 3 hours one day to create a CURL query that I ended up creating in a SQL statement in 10 minutes once I figured out the database structure. Does anyone have: 1. A documented list of C

Re: [Puppet Users] PuppetDB low catalog-duplication rate Puppet DB 4.3.0

I had a broadly similar issue in that I had a low catalog duplication rate and I had to change some puppet manifests around to fix that. Back in 2015 I was doing this to get mcollective plugin sources for the file resource: source => regsubst(keys($plugins), '^', 'puppet:///modules/mco/plugins/

[Puppet Users] PuppetDB low catalog-duplication rate Puppet DB 4.3.0

Hey all, I am hoping there is someone else in the same boat as I am. We are running Puppet 4.2.2, along with PuppetDB 4.3.0. I am seeing low duplication rate which I think is contributing to our queuing problems in PuppetDB. The queue will fluctuate from 0-100 queued, to up to 2000. We have

[Puppet Users] PuppetDB - High CPU Large number of KahaDB files and very little work going to postgresql

Last Sunday we hit a wall on our 3.0.2 puppetdb server. The cpu spiked and the KahaDB logs started to grow eventually almost filling a filesystem. I stopped the service, removed the mq directory per a troubleshooting guide, and restarted. After several minutes the same symptoms began again an

[Puppet Users] PuppetDB / hiera and Sensitive() questions

Hello, - Puppet: node: 3.7.2-4 / puppet server: 2.7.2-1puppetlabs1 / puppetdb: 4.4.0-1puppetlabs1 - Distribution: Debian Jessie - Module version: latest I have some questions about the Sensitive() function: I've *rewritten* my config to something like this: class profile::grafan

[Puppet Users] puppetDB in EC2 , need help to configure apache reverse proxy

*Hello Team , I am new to puppetdb I run puppet db in a EC2 instance and it is running and listening in port 8080* lsof -i :8080 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java851 puppetdb 19u IPv6 18964 0t0 TCP localhost:webcache (LISTEN) *I installed apache o

RE: [Puppet Users] puppetdb 2.x disable some logging

Users] puppetdb 2.x disable some logging Hi, Anyone knows how to disable the logging of follwing entries in puppetdb 2.3.8 ? 2017-04-14 08:48:07,063 WARN  [c.p.p.h.event-counts] The event-counts endpoint is experimental  and may be altered or removed in the future. 2017-04-14 08:48:07,065 WARN

[Puppet Users] puppetdb 2.x disable some logging

Hi, Anyone knows how to disable the logging of follwing entries in puppetdb 2.3.8 ? 2017-04-14 08:48:07,063 WARN  [c.p.p.h.event-counts] The event-counts endpoint is experimental  and may be altered or removed in the future. 2017-04-14 08:48:07,065 WARN  [c.p.p.h.server] v4 query API is experi

Re: [Puppet Users] [PuppetDB] records not being expired from puppetdb?

Well that was daft of me, and you're exactly right. After applying this tuning older things are purged as expected. Thank you! On Wed, Feb 22, 2017 at 01:26:45PM -0800, Wyatt Alt wrote: > Hey Christopher, > > This is the default behavior of PuppetDB -- my guess is you can address it > by tuning

Re: [Puppet Users] [PuppetDB] records not being expired from puppetdb?

Hey Christopher, This is the default behavior of PuppetDB -- my guess is you can address it by tuning your node-ttl and node-purge-ttl parameters, which are described here: https://docs.puppet.com/puppetdb/latest/configure.html#node-ttl PuppetDB won't expire or delete node data unless those

[Puppet Users] [PuppetDB] records not being expired from puppetdb?

Our security department raised that point that some nodes present in puppetdb are not for current or recently decommissioned servers. Does anybody have a spare hint as to why these nodes haven't become expired over the last few months of not being servers, or where I can look for more informati

Re: [Puppet Users] puppetdb 4.3 on PG 9.4 fresh install fails to start with DB UTF8 encoding error

s...@la-z-boy.com writes: > java.sql.BatchUpdateException: Batch entry 1 CREATE AGGREGATE md5_agg > (BYTEA) > ( > sfunc = dual_md5, > stype = bytea, > initcond = '\x00' > ) was aborted. Call getNextException to see the cause. > > 2017-02-16 14:19:54,571 ERROR [p.p.s.mig

[Puppet Users] puppetdb 4.3 on PG 9.4 fresh install fails to start with DB UTF8 encoding error

Hi everyone, I'm trying to do my first ever install of PuppetDB. I'm installing PuppetDB 4.3 from RPM with Postgres 9.4. When I try to start PuppetDB I get the following errors (removed some of the non-important java debugging lines): 2017-02-16 14:19:54,539 INFO [p.p.s.migrate] Applying da

[Puppet Users] Puppetdb module | broken puppetdb

Hello, I have used puppetdb module (https://forge.puppet.com/puppetlabs/puppetdb), installation went clean no errors. (rhel 7.3).Installed puppetdb separately (not on the puppet server) *Puppetdb server* # lsof -i :8081 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java270

Re: [Puppet Users] puppetdb 4.x filling up /opt/puppetlabs/server/data/puppetdb/mq

It turns out this was an ID10T error. One of my puppet masters inadvertently got upgraded, including the puppetserver and puppetdb-termini RPMs. The problem went away when I reverted the puppet RPMs back to their previous release. From what I could tell, the newer puppetserver/puppetdb-termini

Re: [Puppet Users] puppetdb 4.x filling up /opt/puppetlabs/server/data/puppetdb/mq

Hey Ryan, At first glance this sounds like https://tickets.puppetlabs.com/browse/PDB-2390, but that was fixed in 4.0.0 so it shouldn't be the issue. The fact that you have 2 gigs under discarded means you are sending a significant number of commands that PuppetDB is unable to accept. There ar

[Puppet Users] puppetdb 4.x filling up /opt/puppetlabs/server/data/puppetdb/mq

I'm using puppetdb-4.0.0-1.el7 (open source) and over time the ActiveMQ part of it has been saving a bunch of logs under /opt/puppetlabs/server/data/puppetdb/mq, and there does not appear to be any built-in log rotation, at least in the version I am using. After using this puppetdb a couple mon

[Puppet Users] Puppetdb has not logged any new input in past 7 hours

My puppetdb instance is up and running but hasn't stored any updates of any kind in the past 7 hours, according to both Puppet Explorer and Puppetboard. The process is running and so is postgres. Puppet configs haven't changed in that time. /var/log/puppetlabs/puppetdb/puppetdb.log shows plenty

Re: [Puppet Users] puppetdb instllation form source

Hi Joaquin, If you're able to install with the module that's the best option by far, since it will handle all the configuration for you. If something is requiring you to install from source, the instructions are here: https://docs.puppet.com/puppetdb/4.1/install_from_source.html#step-2-optio

[Puppet Users] puppetdb instllation form source

Hi Guys Trying to install puppetdb form source. I downloaded it from git b but then what? If I modify the puppet.conf to enable puppetdb it will lok into file confdir/puppetdb.conf which doesn't exist under the git version. Doing the config.ini rename to that puppetdb.conf will need to add the

[Puppet Users] puppetdb general questions

Hey, all; I've come to the point where i need to install puppetdb in my opensource puppet server 4.5 implementation. Although the use of exported resources is on the scope, the two immediate use cases that I'm looking for are: - puppet node status - Use of a dashboard yet TBD I looked

Re: [Puppet Users] PuppetDB Query based on facts

I was messing around in psql to see if I could figure out the table structure and just query without the API wrapper, I couldn't before you replied. Price is right losing horn. On Friday, June 3, 2016 at 1:37:59 PM UTC-5, Mike Sharpton wrote: > > Doh! Quotes matter, didn't think of it. That a

Re: [Puppet Users] PuppetDB Query based on facts

Doh! Quotes matter, didn't think of it. That appears to work, I grepped and piped and have my list. Thanks very much again, you have saved me work twice now. Mike On Friday, June 3, 2016 at 12:43:17 PM UTC-5, Wyatt Alt wrote: > > Mike, > > Where I was going with that is you might get resul

Re: [Puppet Users] PuppetDB Query based on facts

Yep, the value of my fact is a string. I will keep googling around to see what I can find. Thanks, Mike On Friday, June 3, 2016 at 11:31:28 AM UTC-5, Wyatt Alt wrote: > > Hey Mike, > > I think operatingsystemmajrelease might be a string instead of an int, > based on https://tickets.puppetlab

Re: [Puppet Users] PuppetDB Query based on facts

Mike, Where I was going with that is you might get results with curl -X GET http://localhost:8080/pdb/query/v4/nodes -d 'query=["and", ["=", ["fact", "operatingsystemmajrelease"], "7"], ["=", ["fact", "facta"], "true"]]' or curl -X GET http://localhost:8080/pdb/query/v4/nodes -d 'query=["and",

Re: [Puppet Users] PuppetDB Query based on facts

Hey Mike, I think operatingsystemmajrelease might be a string instead of an int, based on https://tickets.puppetlabs.com/browse/FACT-962. You also might verify that facta is valued with a real boolean instead of a stringified bool (the reference to casing made me wonder.) Wyatt -- You recei

Re: [Puppet Users] PuppetDB Query based on facts

Wyatt, Thanks for your reply. I changed out my url and facta to my fact name, nothing is returned except this. [ ] To ensure it wasn't my fact that was messing this up, I tried another standard fact is_pe. The value should be uppercase "False" but this returns a 500 when run that post/GET.

Re: [Puppet Users] PuppetDB Query based on facts

Hey Mike, I'm thinking you want something like this: curl -X GET http://localhost:8080/pdb/query/v4/nodes -d 'query=["and", ["=", ["fact", "operatingsystemmajrelease"], 7], ["=", ["fact", "facta"], true]]' Wyatt On Fri, Jun 3, 2016 at 6:40 AM, Mike Sharpton wrote: > Hey all, > > I am trying

[Puppet Users] PuppetDB Query based on facts

Hey all, I am trying to do what should be a simple thing. I need to query PuppetDB to gather a list of machines based on arbitrary facta being equal to true and the operatingsystemmajrelease fact being 7. I have searched around and found a few examples, but can't get them to work properly. I

Re: [Puppet Users] PuppetDB resources are not available

Hi Wyatt, I now have a custom fact using powershell commands to get the installed software's for windows machines. *PS Command:-* Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | where{$_.DisplayName -and $_.displayname -notmatch 'Update'} | Select-Object Displa

Re: [Puppet Users] PuppetDB resources are not available

Harish, The reason for that is the resources returned by puppet resource come from the RAL, rather than PuppetDB. If you were to declare puppet resources with the content included in your paste, then they would show up in PuppetDB. PuppetDB will only include version information on package resourc

Re: [Puppet Users] PuppetDB resources are not available

Hi Wyatt, Thanks for your quick reply ! I do get some response for /v3/resources/Package , but it does not contain any information about software's installed on node and it's versions. My data of interest is similar to following ( I got this from node when i issue *"puppet resource package"*)

Re: [Puppet Users] PuppetDB resources are not available

Hey Harish, Your issue could be that trailing backslash. PuppetDB is likely interpretting it as a query for all resources with type "" (i.e empty string). You should be able to get all package resources with /v3/resources/Package, and you can restrict that to a given node with curl -X GET

Re: [Puppet Users] PuppetDB resources are not available

Hi Ken, Thanks for your reply. I got the resource and catalog endpoints working after changing the confdir ownership with " sudo chown -R puppet:puppet `sudo puppet config print confdir`". Now, i just need to get the resource list for all machines or for a specific machine. I can't seem to fi

Re: [Puppet Users] PuppetDB resources are not available

So at a high level The resources are populated from successful Puppet runs that submit their catalogs to PuppetDB. So step 1, run puppet agent -t or whatever, if you aren't seeing something like this in your puppetdb.log: 2016-05-18 14:12:28,855 INFO [command-proc-3055] [p.p.command] [898d1

[Puppet Users] PuppetDB resources are not available

Hi, I am trying to access resources from PuppetDB API as follows, API makes a successful call but empty response. *API call:* curl -X GET 'http://sdin-swt-ctf-01:8080/v3/resources/' *Ouput:* [ ] Is there anything that i need to enable to populate the same? Thanks -- You received this messa

[Puppet Users] puppetdb database size

Hello, I'm running puppetdb (2.3.8 for compatibility with puppet 3.8) for a time. I have observed that although I don't significantly increase the number of servers, the size used by its database is constantly growing, not a lot, but continuously. Is this normal? Or maybe a

  1   2   3   4   5   6   >