similar to: Strange signing problem in AWS - stumped

Hi, I have created an agent node from a master node using below command. puppet node_aws create --image ami-cc5af9a5 --keyname icos-client --type ti.micro Now as i am trying to install puppet on it using below command puppet node install \ --install-script=puppet- enterprise \ --installer-payload=/usr/local/puppet/puppet-2.7.0.tar.gz \ --installer-answers=/usr/local/puppet/agent.txt \

Was... Bash$ puppet node create This "create" action no longer exists. Has it been depreciated? Is the only way to create a node through puppetmaser now? Thanks, D -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/g3lJoO-j_u4J. To post

Hi all, When i try to boot an ec2 instance using: *puppet node_aws bootstrap --server myserverOnAWS.com --image ami-61ad0108 --keyname test-malcom --login ubuntu --type m1.small --keyfile test-malcom.pem -g puppets --verbose --debug --puppetagent-certname test* I get this error: *notice: Signing certificate ...* *debug: certificate_status supports formats: b64_zlib_yaml pson raw yaml; using

Hi, I am trying to bootstrap a new agent from my master node as below. puppet node_aws bootstrap \ --region us-east-1 \ --image ami-cc5af9a5 \ --login root \ --keyfile /root/.ssh/private.pem \ --install-script=puppet-enterprise \ --installer-payload=/usr/local/puppet/puppet-2.7.0.tar.gz \ --installer-answers=/usr/local/puppet/agent.txt \ --keyname icos-client \ --type t1.micro Node is created

Hello: I''m trying to put a puppet master on an EC2 instance, and have it be accessible to agentes using either its EC2 DNS name (e.g., ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com) or a friendlier alias (e.g., puppet.example.com). My /etc/puppet/puppet.conf looks like: [master] certname=ec2-xxx-xxx-xxx-xxx.compute-1.amazonaws.com

Hi! I''ve been playing with puppet node_aws on my ec2 instances and there is a problem which I don''t know how to solve it. The problem is: when i run puppet node_aws bootstrap in order to create and install puppet in new instance, I see at the end of logs: debug: Command: sudo puppet agent --configprint certname err: fingerprint f4:19:2a:53:b9:43:26:73:2e:b6:b7:9c:18:c3:db:aa

Need help for uploading a public key for a new EC2 (AMI) user to tmp folder. Any help on this appreciated. Follow the steps http://aws.amazon.com/articles/1233 i.e not able to pass this step "Copy all the public key files that you generated to a temporary place on your instance:" Steps: 1. SSH into my EC2 instance and logged in as su 2. Created a user "geoman" and with a

Hi, I have created an agent node from a master node using below command. puppet node_aws create --image ami-cc5af9a5 --keyname icos-client --type ti.micro Now as i am trying to install puppet on it using below command puppet node install \ --install-script=puppet-enterprise \ --installer-payload=/usr/local/puppet/puppet-2.7.0.tar.gz \ --installer-answers=/usr/local/puppet/agent.txt \

OpenSSH 5.1p1 I can't grasp why, when connecting with 'ssh -Y' to this test host, I am not tickling the verbose() call below that I have added. I am logging as auth + verbose in sshd_config The X11 forward for the session works fine as tested with xterm. At any rate, I am looking for some guidance on where to log X11 forwards that are established, ideally with a username and remote

Hi, My puppet master version:- #puppet --version 2.7.19 (Puppet Enterprise 2.7.0) While bootstrapping a new instance with my puppet master on Ec2,I am getting this error #puppet node_aws bootstrap --type t1.micro --image ami-00934969 --keyname ec2 --login root --keyfile ~/.ssh/ec2.pem --mode agent notice: Creating new instance ... notice: Creating new instance ... Done notice: Creating

Hi, I'm having trouble connecting to my postgreSQL db on Heroku(Amazon) using RPostgreSQL. I've looked through GitHub for people doing the same thing. There are quite a few examples and all look similar to the below: drv <- dbDriver("PostgreSQL") con <- dbConnect( drv, dbname = "dadqn30er7ghpl", host =

On 04.06.2017 22:35, Larry Rosenman wrote: > On Fri, Jun 02, 2017 at 11:15:41AM -0500, Larry Rosenman wrote: >> I'm seeing lots of: > [snipped] >> Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM >> IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data

What's going on here? I see nothing about this in the ChangeLog, so I am confused. ================================================================== ~:cairo> pwd /afs/rcf/user/jblaine ~:cairo> cat bin/tester #!/bin/sh echo "TESTER program in $HOME/bin!" ~:cairo> ================================================================== OpenSSH 4.4p1 (previous version we were

We are happy to announce the first public release candidate of our Puppet Cloud Provisioner. This release is available for download at our Module Forge: http://forge.puppetlabs.com/puppetlabs/cloud_provisioner<http://downloads.puppetlabs.com/dashboard/> Extensive documentation can be found at: http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html Please report feedback via the

Hi Guys, I''m unable to load the module cloud provisioner, when I try to run node_aws it gives me the below errors: Error: Could not autoload puppet/face/node_aws/list_keynames: no such file to load -- guid Error: Could not parse application options: Could not autoload puppet/face/node_aws/list_keynames: no such file to load -- guid And when I see the help list I can see the below

I am trying to configure puppet with LDAP repository . I have set puppet schema and I have also added node definition at LDAP. Here is my configuration details . ############################################################## Puppet.conf node_terminus = ldap ldapserver = 10.250.11.127 ldapbase = ou=Hosts,dc=xyz,dc=com ldapassword = secret

Hi Thomas, Could you tell how can I change the protocol of corresponding port means 5060 is configured with tcp protocol I want to configured with udp. When I execute nmap -p5060 xx.xx.xx.xx I got below output [root at ip-172-31-32-117 cel]# nmap -p5060 xx.xx.xx.xx Starting Nmap 5.51 ( http://nmap.org ) at 2015-04-21 11:19 UTC Nmap scan report for

I'm seeing lots of: Jun 2 00:00:05 thebighonker exim[57437]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM IN) [52.40.16.7]:51339 I=[192.147.25.65]:465: 535 Incorrect authentication data (set_id=web) Jun 2 00:00:06 thebighonker exim[57439]: dovecot_login authenticator failed for ec2-52-40-16-7.us-west-2.compute.amazonaws.com (ADM IN)

hello list.. I am sharing a yum configuration in a class (centos.pp) between two nodes. But the yum configuration doesn''t apply at all to one node even tho it does to another identically configured node. ## packages are failing to install via yum on one ec2 aws instance and another identical ec2 instance works fine [root@kromep2 ~]# cat /etc/redhat-release CentOS release 5.5 (Final)

Hello... I wanted to be able to startup an EC2 instance with one command and have a fully functioning server without having to shell into each new instance and configure the bits to allow puppet to finish the configuration. Here are some notes I came up with for bootstrapping an ec2 instance with puppet using Ubuntu 10.04. I left out a lot of things about creating and running custom AIM