similar to: puppet node [clean, find, search] questions

Hello, Running into a problem when wanting to daemon-ize the agent. It doesnt seems to do anything: - cannot find any daemon process with (ps aux | grep puppet) - the config is not updated after editing some params on the master - /var/log/puppet stay empty... while, when logged as root, it is working without issue with $puppet agent --test. ##Conf Ubuntu 12.04 Puppet 2.7.11 ## Daemon is

Hello All, So I finally got around to start to cut over node definitions from standard flat files to external nodes (foreman), and getting error message: "Error 400 on SERVER: Could not find node ''nodename''; cannot compile" - So basically it can''t pick up the node from the external node config. When I test the fetching of the yaml file it seems to work

In my puppet client I have puppet.conf defined puppet server as mypuppet server = mypuppet.example.net Not sure why the puppet client puppet-test is still sending these noises to the syslog Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911 daemon.error] Could not find server : getaddrinfo: node name or service name not known Jun 10 13:36:23 puppet-test puppetd[10863]: [ID 702911

Hello Gang, I''m working on scaling my puppet solution, and I''m deploying multiple masters w/ passenger that are going sit behind a load balancer. If anyone is using these type of setup, would you share how you deal with the SSL certs? I''ve been following Bode''s Blog (http://bodepd.com/wordpress/?p=7), and it''s not working to good for me.

I''m having some trouble with getting an ENC to work alongside site.pp: Even with a ''default'' node definition, and an ENC that only returns 0, regardless of input, consistently results in a ''cannot find node'' error. I''m wondering what I''ve missed here. I''ve tried to reduce everything to a ''base case'': and

Hi, When I run puppet agent --test --environment 42A, I have the following warning : Warning: Local environment: "42A" doesn''t match server specified node environment "production", switching agent to "production". ... The puppet manifest for the environment "42A" isn''t applied. The puppet version is 3.3.1-1puppetlabs1 on agent and

Hi- I recently upgrade from 0.24 to 0.25. In my 0.24 config, I had LDAP working such that Puppet was matching nodes in my directory to determine what classes to apply. I upgraded to 0.25 and this stopped working. I do not even see attempts from the Puppetmaster to search the directory (i.e., no connections to the ldap server). I *did* update the puppetmasterd conf, adding the variable

When I use the latest puppet 0.25.1 I got the same problem. This is what I do: 0. Install the Ubuntu 8.04 server with ssh, ruby, rdoc, libopenssl- ruby and git-core (which gets removed after clone). 1. Install the latest puppet from git repositories on both machines using git clone «git clone git://github.com/reductivelabs/puppet» and «git clone git://github.com/reductivelabs/facter» 2. Install it

I''m trying to setup dashboard as a node classifier w/puppet 2.6.14. Not sure why this is not working... In puppet.conf on the master I have: node_terminus = exec external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http:// localhost /usr/share/puppet-dashboard/bin/external_node The agent''s return: err: Could not retrieve catalog from remote server: Error 400 on SERVER:

At long last, 0.24.0 has been released. Look for your friendly packagers to package it up in the near future, but in the meantime you can download it: http://reductivelabs.com/downloads/puppet/puppet-0.24.0.tgz I''ll be walking the different release sites (RubyForge et al) and posting it there, too. Look for a related announcement later today on changes in development practices

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my

All, I am sure this is just something I am doing wrong, but I am trying to implement a node classifier (shell script) to have my nodes inherit the proper classes. However, when I run it I am not getting any classes except those that are defined in default. Rather than going into detail showing all of my configurations right off the bat, I have a question: I just stood up a

Hello, I''m trying to use External Node classification and I have not idea what is my mistake. I getting the following error : err: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `downcase'' for ["hola", {"mens"=>"HOLA"}]:Array on node casa I have a very simple parameter class : class hola( $mens =

puppet maser conf: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl [master] classfile = $vardir/classes.txt localconfig = $vardir/localconfig user = root group = root fileserverconfig = /etc/puppet/fileserver.conf reportdir = /home/logs/puppet/reports masterhttplog = /home/logs/puppet/masterhttp.log masterlog =

I did a fresh install on Ubuntu 12.04 with apt packages from puppet labs. I have agents talking to my puppetmaster. Puppetmaster is running apache/passenger connected to puppetdb and puppet-dashboard is setup to use puppetdb but it is not able to see any reports submitted to puppetdb. When an agent connects to master I see : Info: ''replace facts'' command for hostname

Hi, I''m trying to puppet kick with class option. Pupper Master: puppetmaster.example.com Puppet Client1: host1.example.net Puppet Client2: host2.example.net But I get this error. --- [root@puppetmaster ~]# puppet kick --class test --debug test: host1.example.net.example.com, host2.example.net.example.com Triggering host1.example.net.example.com, host2.example.net.example.com Host

Hello, Is it possible to configure an ENC to provide class definition to a number of nodes at the same time where a few other nodes are controlled in the site.pp by node ''FQDN'' {blah} for the same puppetmaster ? I am wondering once parameters are set for the master to look for an ENC based definitions, will it conflict with the site.pp node definitions ? For example these

I''ve ran into a strange issue today while using my development environment I was receiving some errors about modules that shouldn''t have been used. After looking it looks like my agent (or master) isn''t respecting the environment I specify and is actually using the main (master) environment. This used to work and I haven''t had any changes beyond a upgrade ..

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

Hello, It seems that, for one reason or another, two thing happened: the postgres for puppetdb was dead, and the puppetmaster service was started, even though it''s run from apache. After a bit of cleanup, everything works now. Thanks for your suggestion, and sorry for the stupid issue. On Tue, Mar 26, 2013 at 11:43 AM, Keith Burdis <keith@burdis.org> wrote: > The agent only