Hi,
I am trying to install a puppet module on CentOS 6.5. It returns Connection
timed out error
root@oo5:~# puppet module install openshift/openshift_origin --debug
Debug: Runtime environment: puppet_version=3.7.5, run_mode=user,
ruby_version=1.8.7
Notice: Preparing to install into /etc/puppe
Hi!
I try to install modules in puppet, but it gives an error message
independent of the module I try to install:
myserver:~ # puppet module install rtyler/jenkins
Notice: Preparing to install into /etc/puppet/modules ...
Notice: Downloading from https://forgeapi.puppetlabs.com ...
Error: Coul
Assuming that you are running a typical puppet master configuration, if you
review the Puppet process flow here:
http://www.aosabook.org/images/puppet/TimingDiagram.png
You would see that the issue likely occurring during plugin stage. This seems
to be cause because it looks like it is not able
We are evaluate PE and I installed puppet-enterprise-2.8.1-el-6-x86_64
agent. When I run agent with
puppet agent --no-daemonize --debug --onetime
I am keeping get error:
err:
/Stage[main]/Pe_mcollective::Server::Plugins/File[/opt/puppet/libexec/mcollective/mcollective/security/sshkey.rb
The fix was lowering the MTU.
I ran ifconfig ppp0 mtu 1000 and puppet runs without any problem.
I didn't think this fixed it in my last post because I made some changes on
the puppet master. Once I fixed those changes I lowered the MTU and it
works!!
On Friday, October 26, 2012 11:05:40 AM
I was able to telnet port 8140 via the 3g connection.
I also tried to lower the MTU on the interface and I was still
unsuccessful. So I set it back
One thing I don't understand is that the error message has now changed to
err: Could not retrieve catalog from remote server: Connection reset by
Interesting setup. Sometimes providers block uncommon ports. Can you get to
8140 over your 3/4g? If not, try running on 443 (change puppet.conf or apache
ports).
If none of these work check the docs for timeout settings (can't remember of
hand).
Den
On 26/10/2012, at 3:55, Steve wrote:
> I
I have a puppetmaster on an Amazon EC2 instance of Ubuntu 12.04. All of the
puppet nodes I am running are also on ubuntu server 12.04. I can connect
any of the nodes on a wireless or LAN connection. When I switch my node to
a Verizon mobile 3g or 4g device I run "puppet agent -t" and I get the
