For the next one hitting this - in my case this was related to a old
version of the puppetdb module (v2.0.0) which queried a URL that was no
longer existent.
Updating the module cleared the error right up.
The module was previousely not update because of a dependency lockup
through puppetlabs/
Did you figure this out Sans?
My only next logical step would be to have you show me a full git
repository with a working copy of the code/vagrantfile/etc. that is
actually breaking.
ken.
On Wed, Jun 18, 2014 at 7:17 AM, Sans wrote:
> Thanks Rakesh!
> But, as you probably can guess, that didn't
> Did you ever fix this. I am having the same problem.
>
> It is an issue with SSL. Chrome gives this error: "Error code:
> ERR_SSL_PROTOCOL_ERROR".
> Curl gives this error "curl: (35) Unknown SSL protocol error in connection"
>
> If I figure more out, I will post the fix.
These two errors are un
On Thursday, June 19, 2014 12:17:41 AM UTC+10, Sans wrote:
>
> Thanks Rakesh!
> But, as you probably can guess, that didn't change a thing; still getting
> the same error. I'm not sure if PuppetDB look in the DNS record (as opposed
> to hosts file), in that case it never gonna work. Best!!
>
Thanks Rakesh!
But, as you probably can guess, that didn't change a thing; still getting
the same error. I'm not sure if PuppetDB look in the DNS record (as opposed
to hosts file), in that case it never gonna work. Best!!
--
You received this message because you are subscribed to the Google Gr
Santanu,. can you please try and update your jetti.ini as follows
[jetty]
host = 0.0.0.0
port = 8080
*ssl-host = 0.0.0.0*
ssl-port = 8081
ssl-key = /etc/puppetdb/ssl/private.pem
ssl-cert = /etc/puppetdb/ssl/public.pem
ssl-ca-cert = /etc/puppetdb/ssl/ca.pem
Restart puppetdb and verify...
On Wed,
The puppetdb log is attached in the previous post.
And, here is the curl output:
root@puppet:~# curl
> 'http://puppet.internal:8080/v2/metrics/mbean/java.lang:type=Memory'
> {
> "ObjectPendingFinalizationCount" : 0,
> "HeapMemoryUsage" : {
> "committed" : 86220800,
> "init" : 805248
> It's very strange: Until I run puppetdb ssl-setup -f, I get
>>
>> Error: Unable to connect to puppetdb server (puppet.internal:8081): [404]
>> Not Found
>
> but after that, I get
>
>
>> Notice: Unable to connect to puppetdb server (puppet.internal:8081):
>> #
>
>
>
> Since, I increased the timeou
This is just after building a new server:
2014-06-17 23:20:05,246 INFO [p.t.s.w.jetty9-core] Removing buggy security
> provider SunPKCS11-NSS version 1.7
> 2014-06-17 23:20:06,036 INFO [p.t.s.w.jetty9-service] Initializing web
> server.
> 2014-06-17 23:20:06,132 INFO [p.t.s.w.jetty9-service]
It's very strange: Until I run puppetdb ssl-setup -f, I get
*Error: Unable to connect to puppetdb server (puppet.internal:8081): [404]
> Not Found*
>
but after that, I get
Notice: Unable to connect to puppetdb server (puppet.internal:8081):
> #
>
Since, I increased the timeout to 60, it chan
> Right now I'm creating only one VM, co-locating PuppetMaster and PuppetDB to
> make it simple - destroying and rebuilding. But it always fails - during the
> provisioning/building and also even after if I login to the machine and run
> puppet apply. Telnet works fine:
>
>> root@puppet:~# telnet p
hi Ken,
Right now I'm creating only one VM, co-locating PuppetMaster and PuppetDB
to make it simple - destroying and rebuilding. But it always fails - during
the provisioning/building and also even after if I login to the machine and
run puppet apply. Telnet works fine:
root@puppet:~# telnet p
Oh ... and lets see the output of:
iptables -vnL
Perhaps there is a firewall here? Its worth double checking.
On Tue, Jun 17, 2014 at 11:06 AM, Ken Barber wrote:
> At first glance this all seems correct. Hrm.
>
> Can you do the telnet test?
>
> telnet puppet.internal 8081
>
> Also, are you dest
At first glance this all seems correct. Hrm.
Can you do the telnet test?
telnet puppet.internal 8081
Also, are you destroying and rebuilding these VM's each time and then
its failing? Or are you doing all of this _after_ the vm's are
launched. Its quite possible there is a race condition/orderin
Hi Ken,
Thanks for the heads up!
First of all, it's a VBox VM, provisioned by Vigrant. PuppetMaster and
PuppetDB are on the same machine.
I did go through those basic checks before posting, which appeared fine:
root@puppet:~# telnet puppet.internal 8081
> Trying 127.0.1.1...
> Connected to pupp
> Just started using PuppetDB (using the Puppetlabs' module) and getting
> issues with connection. First it was giving me server Not Found:
>
>> Error: Unable to connect to puppetdb server (puppet.internal:8081): [404]
>> Not Found
>> Notice: Failed to connect to puppetdb; sleeping 2 seconds before
Hi there,
Just started using PuppetDB (using the Puppetlabs' module) and getting
issues with connection. First it was giving me server Not Found:
Error: Unable to connect to puppetdb server (puppet.internal:8081): [404]
> Not Found
> Notice: Failed to connect to puppetdb; sleeping 2 seconds bef
17 matches
Mail list logo
