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
h
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 t
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 that
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 wrote:
> Hi Ryan,
>
> The puppetdb process shouldn't be trying to manipulate the postgres process
> in any way--it should o
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
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 wrote:
> On 18 Decemb
On 18 December 2012 15:50, Ryan Bond 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 * instead
> of th
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 * instead
of the init script, puppetdb fires up with no problems.
An
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 th
On 20 July 2012 11:20, Chris Price 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 /var/log/puppetdb, can y
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 /et
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 hap
On 17 July 2012 10:19, Deepak Giridharagopal wrote:
> On Mon, Jul 16, 2012 at 5:13 PM, Peter Brown wrote:
>>
>> On 17 July 2012 03:15, Chris Price wrote:
>> > Also, would you mind sharing a bit more info about your setup? I
>> > presume:
>> >
>> > * You are installing from the puppetlabs apt re
On Mon, Jul 16, 2012 at 5:13 PM, Peter Brown wrote:
> On 17 July 2012 03:15, Chris Price 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
On 17 July 2012 03:15, Chris Price 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 myself to the ticket.
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 Sun, Jul 15, 2012 at 7:42 PM, Peter Brown 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 DEBUG but still not
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 it
19 matches
Mail list logo
