On 27/11/13 14:55, Ken Barber wrote:
This all sounds pretty serious, but something isn't quite right here
with the information you have provided. This error:
>puppetdb.resnet.bris.ac.uk:8081: Connection refused - connect(2)
Its very rare that a bug in a running piece of code/framework whatever
will cause a connection refused (destination port unreachable) message
on its own, its usually because the port and IP you are connecting to
is wrong and your client never got to connect to your application.
Thus its the kernel that returns the error, not the application.
Sorry, my mistake. This is the message I am getting - the above message
was the result of some of my tinkering.
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Failed to submit 'replace facts' command for
radius-dev.nomadic-core.bris.ac.uk to PuppetDB at
puppetdb.resnet.bris.ac.uk:8081: SSL_connect returned=1 errno=0
state=SSLv3 read server key exchange B: EC lib
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
--
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 discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/52960C93.1000408%40bristol.ac.uk.
For more options, visit https://groups.google.com/groups/opt_out.
