Simon Tideswell writes:
> Do you have a rough idea of the timeframe for Postgres 10 support?
We don't yet, though I think it's possible it'll make it in before the 6.0
release in a couple of months.
Thanks
--
Rob Browning
--
You received this message because you are subscribed to the Google
*"Now that I know the process of building a JAR you will find a willING
tester in me."*
Arrggh, I hate it when I do that
Simon
On Wednesday, July 25, 2018 at 10:10:42 AM UTC+10, Simon Tideswell wrote:
>
> Hello Rob
>
> Do you have a rough idea of the timeframe for Postgres 10 support? Now
Hello Rob
Do you have a rough idea of the timeframe for Postgres 10 support? Now that
I know the process of building a JAR you will find a will tester in me.
Simon
On Wednesday, July 25, 2018 at 3:11:01 AM UTC+10, Rob Browning wrote:
>
> Simon Tideswell > writes:
>
> > Thanks for that. I can
Simon Tideswell writes:
> Thanks for that. I can now get PuppetDB to start following your
> instructions. I'm running on Ubuntu 18 which uses PostgreSQL 10 and this
> version of PostgreSQL doesn't like some aspects of the SQL being performed
> by the JAR.
Ahh, right, PuppetDB is not
Hello Rob
Thanks for that. I can now get PuppetDB to start following your
instructions. I'm running on Ubuntu 18 which uses PostgreSQL 10 and this
version of PostgreSQL doesn't like some aspects of the SQL being performed
by the JAR.
Excerpt from the log file ...
Simon Tideswell writes:
> Hello Rob
>
> Thanks for that information. *lein uberjar *worked. But it built a jar that
> does not contain every library necessary to run PuppetDB.
Oh, I missed this message before my last reply, and I think I may have
just gotten the invocation slightly wrong. How
Hello Rob
Thanks for that information. *lein uberjar *worked. But it built a jar that
does not contain every library necessary to run PuppetDB.
Some, truncated, output from lein ...
puppetserver test depdency unconfigured (ignoring)
-- blah blah blah ---
Warning: The Main-Class specified does
Hi Simon,
While this isn't directly related to your question, you might want to pile
onto this ticket to ensure that the community can build all of the package
artifacts.
https://tickets.puppetlabs.com/browse/LTH-156
Thanks,
Trevor
On Wed, Jun 13, 2018 at 8:01 PM Simon Tideswell
wrote:
>
Simon Tideswell writes:
> No, I'm not trying to do anything fancy. I just wanted to use PuppetDB on a
> Ubuntu 18 server so that I can access the data with PuppetBoard. I can see
> that Canonical provided a package for PuppetDB on U14. I actually used the
> same Package on a U16 server with
On Thu, Jun 21, 2018 at 06:49:01PM -0700, Simon Tideswell wrote:
>Hello Rob
>No, I'm not trying to do anything fancy. I just wanted to use PuppetDB on
>a Ubuntu 18 server so that I can access the data with PuppetBoard. I can
I've had a good experience using PuppetBoard via Docker per
Hello Rob
No, I'm not trying to do anything fancy. I just wanted to use PuppetDB on a
Ubuntu 18 server so that I can access the data with PuppetBoard. I can see
that Canonical provided a package for PuppetDB on U14. I actually used the
same Package on a U16 server with good results. But the
Simon Tideswell writes:
> The instructions here
> https://puppet.com/docs/puppetdb/5.2/install_from_source.html don't
> actually work! I'm doing this on Ubuntu 18 (Bionic). I've installed *lein*
> from the Ubuntu 18 packages rather than pulling it down from github (in
> case that is
See also
https://tickets.puppetlabs.com/projects/PDB/issues/PDB-3938?filter=allissues
.
Hello
The instructions here
https://puppet.com/docs/puppetdb/5.2/install_from_source.html don't
actually work! I'm doing this on Ubuntu 18 (Bionic). I've installed *lein*
from the Ubuntu 18 packages
I've installed puppetdb v4.4.0. I've opened the http dashboard to other
hosts for testing purposes and if I leave a Chrome tab open to it the tab
eventually changed to an "Aw, Snap" error page, reloading the page resolves
the problem. However if I leave a Firefox tab open to it this doesn't
Seems like to me the SSL loaded into PuppetDB (the port 8081 you
mention) is not valid.
A simple activity would be to use our provided tool to reload the
certificates again:
* Move /etc/puppetdb/ssl to ssl.bak to preserve the original
* Backup /etc/puppetdb/conf.d/jetty.ini to say jetty.ini.bak
When I run
openssl s_client -host puppet -port 8081 -CAfile
/etc/puppet/ssl/certs/puppet.fqdn
I get Verify return code: 21 (unable to verify the first certificate).
If I run the same command, but use port 8140 to connect to puppet, I get a
return code of 19 (which is correct).
I believe
I ran across this same problem after upgrading. Puppetdb would slowly run,
then die without a single log.
I don't remember what version of puppetdb I upgraded from, but I upgraded
to 1.0.5.
Check your /etc/puppetdb/conf.d It's likely empty.
On ubuntu I solved the problem (a little overkill)
Hi Chris,
When it runs as the pe-puppetdb user, it dies off with zero logging. I have
Debug enabled as well...
Thanks
Ryan
On Dec 19, 2012, at 11:01 AM, Chris Price ch...@puppetlabs.com wrote:
Hi Ryan,
The puppetdb process shouldn't be trying to manipulate the postgres process
in any
It seems that once I cut over to postgres the puppet user was no longer
able to launch puppetdb.
The easy fix was changing the user to root in /etc/default/puppetdb...but
I doubt this is something I'll want to leave in place.
On Tue, Dec 18, 2012 at 5:17 PM, Peter Brown rendhal...@gmail.com
Hi Ryan,
The puppetdb process shouldn't be trying to manipulate the postgres process
in any way--it should only be communicating with it via a socket, and the
authentication should be based on the postgres database user account rather
than the system user account. Are you seeing any errors in
On 18 December 2012 15:50, Ryan Bond drb...@gmail.com wrote:
Was this issue ever resolved? I've been experiencing the same symptoms,
ever since I switched over to postgresql.
Interestingly enough, when I run *java -jar
/usr/share/puppetdb/puppetdb.jar services -c /etc/puppetdb/conf.ini *
OK, yes, the most important bit from that log output is this:
SelectChannelConnector@localhost:8080
If you hit port 8080 with a browser and/or via telnet, it should be open.
Ideally there should also be some output about opening port 8081 for SSL
connections, but it's entirely possible that
Hello Pete,
Do you have a reliable way to reproduce the port issue that you mentioned?
We'd like to troubleshoot it further but haven't found any way to
reproduce it on our end yet.
If you're not getting log output in /var/log/puppetdb, can you please try
the following?:
1. Edit the file
On 20 July 2012 11:20, Chris Price ch...@puppetlabs.com wrote:
Hello Pete,
Do you have a reliable way to reproduce the port issue that you mentioned?
We'd like to troubleshoot it further but haven't found any way to reproduce
it on our end yet.
If you're not getting log output in
On Sun, Jul 15, 2012 at 7:42 PM, Peter Brown rendhal...@gmail.com wrote:
Hi everyone,
I got the new version installed and am now having a strange issue.
my puppetdb server seems to start but then dies after a few seconds
with no logging that i can find.
I tried setting the log level to
Also, would you mind sharing a bit more info about your setup? I presume:
* You are installing from the puppetlabs apt repos?
* Your upgrade was from puppetdb 0.9.1 to 0.9.2?
On Monday, July 16, 2012 9:36:40 AM UTC-7, Deepak Giridharagopal wrote:
On Sun, Jul 15, 2012 at 7:42 PM, Peter Brown
On 17 July 2012 03:15, Chris Price ch...@puppetlabs.com wrote:
Also, would you mind sharing a bit more info about your setup? I presume:
* You are installing from the puppetlabs apt repos?
yes
* Your upgrade was from puppetdb 0.9.1 to 0.9.2?
and yes.
thanks again Deepak.
I shall add
On Mon, Jul 16, 2012 at 5:13 PM, Peter Brown rendhal...@gmail.com wrote:
On 17 July 2012 03:15, Chris Price ch...@puppetlabs.com wrote:
Also, would you mind sharing a bit more info about your setup? I
presume:
* You are installing from the puppetlabs apt repos?
yes
* Your upgrade
On 17 July 2012 10:19, Deepak Giridharagopal dee...@puppetlabs.com wrote:
On Mon, Jul 16, 2012 at 5:13 PM, Peter Brown rendhal...@gmail.com wrote:
On 17 July 2012 03:15, Chris Price ch...@puppetlabs.com wrote:
Also, would you mind sharing a bit more info about your setup? I
presume:
*
I have gotten around the current problem by installing puppetdb on one
of me CentOS 6 nodes and it appears to be working as expected.
I even got it talking to my postgres database on my master node and
that seems to be working as well.
Now I can apply some new catalogs i need to roll out.
I am
Hi everyone,
I got the new version installed and am now having a strange issue.
my puppetdb server seems to start but then dies after a few seconds
with no logging that i can find.
I tried setting the log level to DEBUG but still nothing.
I tried running by hand and discovered it couldn't read
31 matches
Mail list logo
