similar to: Puppet Agent Configure Error in EC2

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 \

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 \

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

Hi there, after using Foreman successful on our clusters for more than a year. I'd like to reinstall a 90 node cluster with Centos 7.4. It's now running on Centos 7.3 . I'm not able to just update to 7.4 because of zfsonlinux dependencies and well - some nodes died and had to bare metal install them. So I was able to install these nodes successfully by pxe-booting and using a

A quick overview of our setup: We have an EBS-backed puppet master instance with an Elastic IP, and a number of puppet agent AMI images in various regions. When these AMIs were created, they were authenticated with the puppet master using the following command: # puppet agent --certname=$(cat /etc/puppet/certname) --server puppet.ourdomain.net --waitforcert 30 --test ...and accepted on the

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

I''m getting these errors when running ''puppet agent --test'' after doing a new installation of an agent: err: /Stage[main]/Pe_mcollective::Plugins/File[/opt/puppet/libexec/mcollective/mcollective/security/sshkey.rb]/content: change from {md5}512f42272699eaa085c83d2cc67c27ea to {md5}8fa3e9125fd917948445e3d2621d40e5 failed: Could not back up

I''m using puppet 3.0 i install puppet by these two command: sudo rpm -i http://yum.puppetlabs.com/el/5/products/i386/puppetlabs-release-5-6.noarch.rpm sudo yum install puppet-server as http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-red-hat-enterprise-linux-and-derivatives and

Hello everyone, Just getting my first puppet master set up and I am having a problem that I just do not know how to get past. For some reason, my certificate store keeps getting corrupted. Basically what happens is that the server will issue itself a valid certificate (after removing the ''bad'' cert) and will run just fine. When I start puppetDB (I am pretty sure it happens

I have a very basic puppet install right now, running puppet master, with the dashboard and foreman on the same host, I have some legacy static nodes (nodes.pp) and now I am using puppet to provision nodes in EC2. I am running cloud provisioner .60rc1 and my question is what happens after a puppet node bootstrap? I''m running into some issues and maybe its just idiot user driving this

Hi, I have a puppetmaster - agent architecture. I have a module for the vsftpd configuracion in the agents. The configuration of the value ''max_per_ip'' in the agents may vary. This is a line of the manifest: $max_per_ip = hiera(''max_per_ip'',10) I want to specify different values for each agent using hiera. The problem is I am only able to specify the

Hi, I am using the cloud provisioner to bootstrap some ec2 nodes, and these clients are signed using a randomly generated certname, which is put in /etc/puppet.conf at the bootstrap time (eg certname = d7bcd693-73fd-495f-0876-ff91ea11111e). But my puppet code repo also manages the puppet.conf file, so the file will be overwritten on the client at the first puppet run. Nevertheless, i should not

Hi All, If we have couple modules in Master server ,we can specifically add some modules to our agent using this command. puppet agent --test --tags=<module-name> This command will run if the modules are already there in master, to master I am adding these modules using puppet enterprise console.Is there any command available to do it from agent machine? Regards, Jithin -- You

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, First of all, thank you for the work the contributors are doing with Dovecot ! Dovecot is doing a great job ! I am encountering a problem with a configuration and, despite my search on the web, I do not find any solution for this problem. Dovecot seems to stop accepting new connection. The users : - - can not save sent messages to

Hi all, I ran into the following problem: Until now, i used fqdn as certname (i.e. had no certname defined in puppet.conf, so defaults applied) and everything worked fine. However, I wanted to use tthe short hostname as certname, so I redeployed the puppet.conf file, re-generated the certificates and signed them, and removed the old certificates from the master. Now I have the following status:

Hi all I''m trying to set up a separate puppet master and client on EC2. I''ve used two instances of CentOS5.4 with nothing other than the base install and have installed puppet via the ruby gems. Puppet is at 2.6.4 on both machines. I''ve been following the guide to get a basic configuration working (http://docs.puppetlabs.com/guides/configuring.html) with a little tweak

Hello All, I wanted to create two two MySQL database with same user credential using Puppet-MySQL. How can I achieve this? Please find my script below. class mysql::vsdatabase { include mysql mysql::db { ''vidispine'': user => ''user'', password => ''user123'', host => ''db.<hostname>.com'', } } How can I add

I want to manage my puppet.conf files on every node, via a puppet module on the puppetmaster. However, in puppet.conf on each of my nodes, I also *must* specify the certname attribute. (This is because my company''s NIS domain doesn''t match it''s DNS domain and the fqdn comes out erroneous unless I enforce the DNS name with the certname attribute.) Does anyone know how

1. I get the following error when I run “puppet device’ err: Could not request certificate: Could not write /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem to privatekeydir: Permission denied - /var/opt/lib/pe-puppet/devices/certname/ssl/private_keys/certname.pem Any thought? Thanks, -- You received this message because you are subscribed to the Google Groups

If I run below command on puppet master. I am able to get output pasted here. But the same information, I am trying to capture via browser using http://puppetdb:8080/v2/facts/operatingsystem but not working [root@puppetmaster ~]curl -X GET http://puppetdb:8080/v2/facts/operatingsystem curl: (6) Couldn''t resolve host ''puppetdb'' [root@puppetmaster ~]# curl -X