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
On 12/05/2017 11:25 PM, Dietrich, Stefan wrote:
My main concern were the database migrations run by PuppetDB during the
upgrade, which seems not to be an issue (despite the ancient version).
Yes, there shouldn't be a problem there (though they may take some time
depending on your data).
--
On 12/05/2017 01:57 PM, Dietrich, Stefan wrote:
Hello,
in order to finish our Puppet 4.x migration (and than Puppet 5.x, yay),
PuppetDB has to be upgraded as well.
If I read the upgrade docs correctly, a direct upgrade from PuppetDB 2.3.x is
not supported [1].
So in order to do this, an upg
Hi Bryan,
This is a bug -- right now fact_contents doesn't support ordering on value,
but the docs as you say, as well as this ticket:
https://tickets.puppetlabs.com/browse/PDB-1649 suggest that's a regression.
I've created https://tickets.puppetlabs.com/browse/PDB-3687 to track the
fix. In the
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
ce to operate.
Wyatt
Em quinta-feira, 20 de julho de 2017 15:13:38 UTC-3, Wyatt Alt escreveu:
That's the behavior I'd expect -- I believe the issue is you're
just not
hitting an endpoint. If you're trying to verify that the service
is up
and running
That's the behavior I'd expect -- I believe the issue is you're just not
hitting an endpoint. If you're trying to verify that the service is up
and running, the way we typically do that is with
curl http://localhost:8080/pdb/meta/v1/version
which should return a blob with a version number.
Wy
The userlist is most likely your your issue. This seems analogous to
FACT-1345 and PDB-2631 for context -- we usually see this with the os,
mountpoints, and partitions facts. What's generating the userlist and
what are the numbers it's valued with? Do you have code that generates
the fact? Ther
Peter,
You said no work is going to postgresql but how did you determine that? Are
you able to see if PuppetDB (java) or postgres is consuming the CPU? How is
disk activity?
Slow command processing is often correlated with long database queries --
it would be useful to turn on slow query logging
On 04/22/2017 11:54 PM, Bill Sirinek wrote:
A side effect of this change is that my PuppetDB command queue depth
went from just over 100 to 0, and has stayed there for a couple hours
now, maybe occasionally poking up to 2-3 briefly. At least I think it
was related to this change. :)
You're pr
On 04/22/2017 10:35 AM, Bill Sirinek wrote:
2017-04-22 13:30:25.912 EDT
[db:pe-puppetdb,sess:58fb8caf.8cbb,pid:36027,vtid:29/23277,tid:396758]
STATEMENT: INSERT INTO resource_events ( new_value,
corrective_change, property, file, report_id, old_value,
containing_class, certname_id, line,
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
Hey Anfield,
prune_upto was retired before 2016.2, along with the console database
itself (the data is in PuppetDB now). The way to control report deletion is
via the node_ttl, node_purge_ttl, and report_ttl PuppetDB configuration
settings, which are documented here:
https://docs.puppet.com/pup
Hi,
This seems like a bug to me, but I can't reproduce it on postgres 9.4 +
centos 7.3 and the combination of PDB 4.3 and postgres 9.4 is widely
used/tested.
Can you give a bit more detail about your environment? I'd like to know
your OS and version and the method you used to install postgres.
On 01/16/2017 07:05 PM, alohaaa...@gmail.com wrote:
Hello,
I just added postgresql 9.6 to my puppet server and receive this error.
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: [400 ] Unsupported query parameter 'command'
I also looked at the debug info and insta
On 12/12/2016 10:09 AM, Harish Kothuri wrote:
I see that following errors are popping up from puppetdb. There are quite a
few of these and also would like to know for which machines it is coming
from
2016-12-12 10:08:16,040 ERROR [c.p.p.command]
[afe425be-8413-49a8-8086-79ebaa00927a]
[store repor
Roetker, Jeremy Barlow, Karel Březina, Ken Barber, Kylo Ginsberg,
Molly Waggett, Rob Browning, Ryan Senior, Wyatt Alt, and Tiffany Longworth
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiv
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
PuppetDB 4.2.2 - August 25, 2016
PuppetDB 4.2.2 Downloads
Available in native package format as part of Puppet Collection 1 (PC1).
More information on the PC1 repositories is available here:
http://bit.ly/1HQJDNb
Binary tarball: http://downloads.puppetlabs.com/puppetdb/
Hey Bret, sorry for the gap in communication. Try making these changes:
* to the [master] section,
storeconfigs=true
storeconfigs_backend=puppetdb
reports=puppetdb
* to the [agent] section for each node, change "reports=puppetdb" to
"report=true".
I think that should straighten it out.
Wyatt
PuppetDB 4.2.1 - August 16, 2016
PuppetDB 4.2.1 Downloads
Available in native package format as part of Puppet Collection 1 (PC1).
More information on the PC1 repositories is available here:
http://bit.ly/1HQJDNb
Binary tarball: http://downloads.puppetlabs.com/puppetdb/
On 8/17/16 6:26 AM, Bret Wortman wrote:
On Wednesday, August 17, 2016 at 9:19:34 AM UTC-4, Bret Wortman wrote:
I'll confess that I know next to nothing about Postgres databases,
so I'm going to ask before I royally mess anything up: what's the
best way to relocate my database from
Can you post a gist of your master's full puppet.conf?
--
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+unsubscr...@googlegroups.com.
To view this di
I'd check the timestamps in the output of
curl -X GET http://localhost:8080/pdb/query/v4/nodes/fs1603.our.net
(with a real certname if that one is fake). These will tell you when the
last report/facts/catalog for the node were stored.
Nothing about the log output you've posted indicates an issue
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
On 07/10/2016 01:32 PM, R.I.Pienaar wrote:
hey,
Been playing with the PQL language and it's quite nice, have 2 questions.
I want to do a regex case insensitive match, docs mention you can do whatever
Postgres supports but I can't figure out how to do case insensitive matches
with PQL?
Postg
Virat,
Please describe what is going wrong with puppetdb. If there is an error
in the puppetdb log, share it in a gist.
Wyatt
On 06/30/2016 02:45 PM, Virat wrote:
Hello All,
I have configured opensource puppet master 4.5.2 & puppetdb 4.1.2.
Then started connecting master and db servers as
On 06/29/2016 10:30 PM, John Naggets wrote:
Hi Wyatt,
Any ideas where I can find PuppetDB v2.x? In the APT repository of
PuppetLabs the oldest I can find is version 3.2.
Those are in the non-PC1 repos at apt.puppetlabs.com, but is no 2.3.x
package for Jessie there. The wheezy ones appear to
John,
You'll want a PuppetDB version in the 2.x series -- 3+ requires Puppet 4.
On the offchance that you're just getting started, note that you can
install the latest puppetserver and puppet-agent packages from the same
PC1 repo, and that the latest PuppetDB will work with those.
Wyatt
On
On 06/12/2016 11:29 AM, Wyatt Alt wrote:
This is the configuration file for the puppetdb terminus, and puppet
server uses it to find puppetdb. Without the file, the hostname
"puppetdb" is assumed, hence the error you see. You need to configure
it like this:
https://docs.
On 06/11/2016 07:35 PM, Zeke Dehnert wrote:
There was a puppetdb.conf file in the /etc/puppetlabs/puppet
directory, but I moved it out, restarted puppet server and I’m still
getting errors:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Failed to execute
'/pdb/
e know if one of those does it.
Wyatt
On Fri, Jun 3, 2016 at 10:37 AM, Mike Sharpton wrote:
> 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.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
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
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
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
Hey Angel,
This sounds like a bug to me but I haven't had time to reproduce it. Would
you mind filing a ticket at tickets.puppet.com?
Wyatt
On Wed, May 4, 2016 at 1:37 AM, Angel L. Mateo wrote:
> Hello,
>
> I'm having a problem with puppetdb. I have deploy a new
> puppetserver (runni
Mike,
If you have no issue dropping and recreating the full database, that's
totally a workaround here (you know your requirements better than I, so
please don't take this as an endorsement of the approach :-) ).
To do this just stop PuppetDB, drop the puppetdb database, and recreate
the dat
Hey Mike, give this a shot (in a psql session):
begin;
delete from facts where fact_path_id in (select id from fact_paths where
name=any('{"disks", "partitions", "mountpoints"}'));
delete from fact_paths where id not in (select fact_path_id from facts);
delete from fact_values where id not in (
On 04/19/2016 10:39 AM, Mike Sharpton wrote:
Again,*_thank you_* very much. If I could buy you a beer, I would.
The machines in question are a mix of RHEL5/6/7.
Hah, you're very welcome. Thanks for confirming the OS; that means this
isn't just a Solaris issue like that facter ticket suggest
Hey Mike,
The unsatisfying answer is that PuppetDB handles giant facts
(particularly array-valued facts) pretty badly right now, and facter's
disks, partitions, and mountpoints facts can all get pretty huge in
cases such as SANs and similar. Can you try and see if the bulk of those
fact paths
Hey jamese,
This is exactly what the fact-names endpoint does. It's documented here:
https://docs.puppet.com/puppetdb/4.0/api/query/v4/fact-names.html
does that suit your needs?
Wyatt
On Sun, Apr 10, 2016 at 11:08 PM, jamese wrote:
> Hi,
>
> I'm looking for a way to retrieve a list of fact na
On 03/14/2016 06:34 AM, Akos Hencz wrote:
Hello,
We have a few nodes that fail to submit facts to PuppetDB, and the
replace facts commands end up in the DLO. The exception is:
clojure.lang.ExceptionInfo: Input to insert-facts-pv-pairs! does not
match schema.
I suspect it is a problem with one
On 02/17/2016 07:48 AM, Trevor Vaughan wrote:
I took a look at the API and it seems like I might have to use
'replace_facts' but I'd need to fetch the last fact set, update it,
and then resubmit it with the updated information which isn't ideal
but would be doable.
This is your best bet u
amounts of binary data. More information on the specifics of the release
can be found in the official release notes:
https://docs.puppetlabs.com/puppetdb/3.2/release_notes.html
Contributors
---
Andrew Roetker, Ken Barber, Rob Browning, Rob Nelson, Russell Mull, Ryan
Senior, and Wyatt Alt
On 11/19/2015 10:46 PM, Dirk Heinrichs wrote:
Am 19.11.2015 um 23:59 schrieb Wyatt Alt:
do you have a shareable manifest that will reproduce the issue?
Unfortunately not. It installs our inhouse SW... What about a simple
manifest which exec's a script that just prints 1 or 2 thousand
On 11/19/15 6:25 AM, Dirk Heinrichs wrote:
Hi,
using Puppet4 together with a PostgreSQL-backed PuppetDB to store
reports. We have some exec resources that don't show up in the reports
stored in PuppetDB (but in the "puppet agent" output as well as
last_run_report.yaml).
These particular exe
On 10/20/15 1:34 PM, Daniel Urist wrote:
Is there any update on when puppetdb will be available for Debian 8
(jessie)? Puppetserver is now available according to the announcement
for v.2.1.2.
On Wed, Oct 14, 2015 at 4:34 PM, Wyatt Alt <mailto:wy...@puppetlabs.com>> wrote:
://docs.puppetlabs.com/puppetdb/2.3/release_notes.html
Contributors
Ken Barber, Ryan Senior, Wyatt Alt
--
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
You're encountering PDB-170 (https://tickets.puppetlabs.com/browse/PDB-170.)
It's a known bug, and last time I looked at it wasn't clear whether the
issue was Puppet or PDB, but I just tried it on Puppet 4.2.2/PuppetDB
3.1.0 and I can't reproduce:
https://gist.github.com/wkalt/83d8d8170d9f20a
Hey Dan,
I see the bottom of a java stacktrace in your log snippet there -- could
you get the full stacktrace from journalctl and stick it in a gist?
Wyatt
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and st
PuppetDB 3.x and PuppetDB 2.x both work with Puppet 4. PuppetDB 3.x does
not work with Puppet 3.
Wyatt
On Fri, Oct 2, 2015 at 7:39 AM, Lori Cho wrote:
> I was reading release notes. PuppetDB 3.x ou works with Puppet 4?
>
--
You received this message because you are subscribed to the Google Gr
On 9/30/15 8:05 PM, Lori Cho wrote:
How come the ticket is still open if fixed?? I came across that when googling
earlier but with no responses to the ticket it was unclear what to make of it.
It was fixed incidentally in unrelated work. I've closed the ticket --
thanks for pointing that out.
On 9/30/15 3:33 PM, Wyatt Alt wrote:
On 9/30/15 2:25 PM, Lori Cho wrote:
We are using puppetdb 2.3.4 with postgres.
When looking at the dashboard, the following only shows '?',
"Collection Queries", "Enqueuing", "DLO Compression", "DLO Size o
On 9/30/15 2:25 PM, Lori Cho wrote:
We are using puppetdb 2.3.4 with postgres.
When looking at the dashboard, the following only shows '?',
"Collection Queries", "Enqueuing", "DLO Compression", "DLO Size on
Disk", "Discarded Messages".
Can someone advise as to why this might be?
--
You rec
rowse/PDB-2003> we can continue the
discussion there, and if you're on IRC I'm available in #puppet on
freenode as wkalt, mostly during work hours on US pacific time.
Thanks,
Wyatt
On Monday, September 28, 2015 at 6:45:49 PM UTC+1, Wyatt Alt wrote:
On 09/28/2015 10:39 AM, Wyatt
On 09/28/2015 10:39 AM, Wyatt Alt wrote:
On 09/28/2015 05:40 AM, Matt Jarvis wrote:
We seem to have hit a bit of an issue with puppetdb garbage
collection. Initial symptoms were exceptions in the puppetdb logs :
Retrying after attempt 6, due to: org.postgresql.util.PSQLException:
This
On 09/28/2015 05:40 AM, Matt Jarvis wrote:
We seem to have hit a bit of an issue with puppetdb garbage
collection. Initial symptoms were exceptions in the puppetdb logs :
Retrying after attempt 6, due to: org.postgresql.util.PSQLException:
This connection has been closed.
And on the postgre
On 8/24/15 12:59 PM, Christopher Wood wrote:
(Although I may dump/restore the data via puppetdb since that's the actual api
to the data, we do not log in via PostgreSQL.)
Others can speak to the rest of the plan, but just to clarify in case
I'm understanding you right: the PuppetDB import/expo
Jessie support in PuppetDB is blocked on support in Puppet Server. As
Martin has said, there is no established delivery date for that yet, but
it's currently supported in the nightly repos (for puppetserver, not PDB)
and my understanding is that it will be coming to PC1 in the next
puppetserver
PuppetDB 2.3.7 August 13, 2015
PuppetDB 2.3.7 Downloads
Available in native package format in the release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
For information on how to enable the Puppet Labs repos, see:
http://docs.puppetlabs.com/g
Fabrice,
Correct. The differences are listed here:
http://docs.puppetlabs.com/puppetdb/3.0/api/query/v4/upgrading-from-v3.html
. Anything missing from that list is a docs bug that we'll be glad to fix.
Wyatt
--
You received this message because you are subscribed to the Google Groups "Puppet
Contributors
Andrew Roetker, Ken Barber, Nick Fagerlund, Rob Browning, Russell Mull,
Wyatt
Alt
--
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
, Jorie Tappa, Ken Barber, Brian LaMetterey, Lars
Windolf, Mathieu Parent, Matthaus Owens, Melissa Stone, Nick Fagerlund, Rob
Braden, Rob Browning, Roger Ignazio, Russell Mull, Ryan Senior, Wayne
Warren, Wyatt Alt
--
You received this message because you are subscribed to the Google Groups
"P
Hey Benjamin,
This is a config validation error. You have a "webapps" setting somewhere
in your config directory. That's not a setting PuppetDB will use, and PDB
will fail to start if it's present. Remove that setting and things should
work fine.
Wyatt
On Thursday, July 9, 2015 at 8:50:15 AM
Hey Jim,
Do you see anything in your puppetserver log you can correlate to this?
Also curious if your "Broke and no longer processing" comment is in
relation to this issue or preexisting.
One interesting, possibly unrelated thing to know is that the report
processors in "reports" attribute in you
John Duarte, Ken Barber, Melissa Stone, Rob Browning, Russell Mull, Wyatt
Alt
Changelog
-
John Duarte (2):
ef409a4 (PDB-1300) Get tests working with Puppet 4 AIO packaging
1c5859a (PDB-1300) Set conditional beaker options for AIO
Ken Barber (3):
766608a (PDB-1469
://docs.puppetlabs.com/puppetdb/2.3/release_notes.html
Contributors
Andrew Roetker, Deepak Giridharagopal, Ken Barber, Melissa Stone, Rob
Browning,
Wyatt Alt
Changelog
-
Andrew Roetker (3):
a8eede4 (PDB-1412) Update rspec dependency from 2.x to 3.x
71875d5 Revert "(PDB
PuppetDB 2.3.2 - April 1, 2015
PuppetDB 2.3.2 Downloads
Available in native package format in the release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
For information on how to enable the Puppet Labs repos, see:
http://docs.puppetlabs.com/guid
com/puppetdb/2.3/release_notes.html
Contributors
Andrew Roetker, Ben S, John Duarte, Ken Barber, Matthaus Owens, Nick
Fagerlund, Rob Browning, Russell Mull, Ryan Senior, Wyatt Alt
Changelog
-
Andrew Roetker (1):
79fab2f (PDB-1328) Add contributors to and edit releas
With the 3.0 major release of PuppetDB in the next few months, we will
be retiring the v2 and v3 PuppetDB query APIs and adopting v4 as the new
stable. At the same time, we will release the final batch of new
features for the v4 API, which means that v4 in 3.0 will be different
than the curren
Hey James,
The MQ depth is labeled "Command Queue depth" in the dashboard. I just
updated the docs to make that connection explicit, so your link should be
updated shortly.
That page isn't intended to document the dashboard specifically, so not all
the fields are described. We don't really docume
Hey Andreas,
Can you give some more information about how this cropped up?
- Have you recently upgraded PuppetDB, or changed any other part of your
Puppet/PuppetDB installation?
- Was PuppetDB running fine before this started occurring, or are you
still getting it set up?
- What version of P
Hey Ryan,
That makes sense, though I'd guess that new reports are being stored and
are available through the API, they just aren't reflected as "latest"
since that's determined by the end_time stamp. report-ttl will be
ineffective without resetting to the future, and then you'd be deleting
r
Hey Fabio,
Got a few questions:
Did you have PuppetDB running properly before you started seeing this
issue or are you still setting it up?
Does it persist after postgres and PuppetDB are restarted?
When you restart PDB and use it, does it immediately produce this error
or does it work for
Abhi,
Try this:
curl -X GET http://localhost:8080/v4/facts/ipaddress --data-urlencode
'query=["in","certname",["extract","certname",["select-nodes",["=",["fact","kernel"],"Linux"
Wyatt
On 12/11/14 12:14 PM, a...@littlewiki.in wrote:
Hello.
I want to get the ip-addresses of all Linux mac
To follow up on what others have said, the method described in the
command example
https://docs.puppetlabs.com/puppetdb/2.2/api/commands.html#examples-using-curl
will deactivate your node, which is different than what we call
"purging", whether or not you intended.
Deactivating a node will n
v 21, 2014 at 8:57 AM, Wyatt Alt wrote:
> Paul,
>
> Thanks for that. It looks like 22128 has not been cleaned up properly for
> some reason, and it's likely being skipped over in the gc process because
> the facts cleanup identifies values to delete from that column in the facts
situation/data needs.
Wyatt
On 11/20/14 12:29 AM, Paul Seymour wrote:
On Wednesday, 19 November 2014 17:56:23 UTC, Wyatt Alt wrote:
Hey Paul,
That's some kind of DB corruption. Shouldn't be happening. Do you
have
any sense of when this started or whether it
Hey Paul,
That's some kind of DB corruption. Shouldn't be happening. Do you have
any sense of when this started or whether it was tied to a recent
upgrade? Is there a stacktrace in your logs that you could gist? Does it
happen on every agent run or only occasionally? Is it always the same
pat
These errors are red herrings as far as PDB not running is concerned.
You can make them go away by changing the temp-usage and store-usage in
the command-processing section of your config file to limit ActiveMQ to
a space less than the size of your disk.
https://docs.puppetlabs.com/puppetdb/la
Hey Stacey,
This error can be generated by queries made during the PuppetDB startup
sequence and also if PuppetDB is upgraded but not restarted. Can your
report your PuppetDB version with
curl -G http://localhost:8080/v4/version
(for the appropriate hostname)
and if you've just upgraded, ens
Ginsberg, Russel Sim, Ryan Senior and
Wyatt Alt
Changelog
-
Justin Holguin (1):
24835c9 (DOCUMENT-18) Mention DLO cleanup in docs
Ken Barber (14):
d48be30 (PDB-707) Fix bonecp 57P01 handling
9b53a30 Allow beaker rake task to accept proper preserve-hosts options
3715db6
running this will be more efficient.
>
> On Friday, October 10, 2014 6:13:04 PM UTC-7, Wyatt Alt wrote:
>
>> Hey Jon,
>>
>> Thanks for the update and the ticket:
>> https://tickets.puppetlabs.com/browse/PDB-947
>>
>> We've been trying to reproduc
C-7, JonY wrote:
Running for 7 hours now. Has exported ~15-20% of the data.
I'm intrigued to see what I end up with.
On Tuesday, October 7, 2014 1:19:04 PM UTC-7, Wyatt Alt wrote:
Thanks Jony.
I've loaded up an embedded database to comparable capacity and
default.
>
>
>
>
> On Tuesday, October 7, 2014 9:00:17 AM UTC-7, Wyatt Alt wrote:
>>
>> Hey JonY,
>>
>> Sounds interesting. What version of PuppetDB are you using? Do you have
>> reports, facts, and catalogs, or only some of those? Can you paste your
Hey JonY,
Sounds interesting. What version of PuppetDB are you using? Do you have
reports, facts, and catalogs, or only some of those? Can you paste your
config.ini?
Also can you give the output of
ps aux |grep java
top -n1
free
in a gist maybe?
Wyatt
On Tue, Oct 7, 2014 at 8:30 AM, Jon
Hi Spriya,
That error will occur if you don't have puppetdb-terminus installed.
Have you installed the terminus as described here?
https://docs.puppetlabs.com/puppetdb/2.2/connect_puppet_master.html
Your routes.yaml file also needs three dashes at the top, not two.
If that doesn't help plea
Hi Guillaume,
Can you post the output of
rpm -qa | grep puppet
?
It looks as if your puppetdb-terminus version could be out of sync with
that of puppetdb.
Wyatt
On Wed, Sep 3, 2014 at 7:17 AM, Guillaume Blairon wrote:
> Hi,
>
> We're using puppetdb 2.1.0 and puppet 3.6.2 on CentOS. PuppetD
Hi Spriya,
Can you try accessing your database server directly at the host and port
specified in /etc/puppetdb/conf.d/jetty.ini and see if you get the same
error?
e.g curl http://localhost:8080/v4/version
Wyatt
On Fri, Aug 29, 2014 at 11:30 AM, Spriya
wrote:
> Hi,
>
> I installed puppet se
90 matches
Mail list logo
