[Puppet Users] puppet agent -t throwing error
Hi everyone, I am trying to run "puppet agent -t" on an agent and it is throwing following error *root@puppet-client:/etc/puppet/manifests# sudo puppet agent -t* *Info: Retrieving pluginfacts* *Info: Retrieving plugin* *Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find default node or by name with 'puppet-client.com, puppet-client' on node puppet-client.com* *Warning: Not using cache on failed catalog* *Error: Could not retrieve catalog; skipping run* Please note that puppet-client.com (dns entry in /etc/hosts : 127.0.0.1 puppet-client.com) is the agent that I am using. Can someone please help? -- 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/4b2b7069-573e-41d3-a8cb-95356a270f72%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Hiera Questions: Virtual User Resources and Hiera
This issue is still unresolved as of 3.1.0
# hiera -h resources -c /etc/puppet/hiera.yaml
{webapplication2={Consumer=undef},
webapplication={Consumer={2a=nil, 1a={offset=3},
3a=undef}, indexer=nil}}
hieranil.pp
$fullhash = hiera_hash(resources)
create_resources(noundefparams,$fullhash)
define noundefparams($Consumer=abc, $indexer=def){
if $Consumer { notify {$Consumer:} }
}
_
]# puppet apply hieranil.pp
Error: Received incomplete information - no value provided for parameter
indexer at /tmp/experiment/hieranil.pp:15 on node puppet-master
Wrapped exception:
Received incomplete information - no value provided for parameter indexer
Error: Received incomplete information - no value provided for parameter
indexer at /tmp/experiment/hieranil.pp:15 on node puppet-master
On Thursday, May 24, 2012 3:15:58 AM UTC+5:30, Jeff McCune wrote:
On Tue, May 22, 2012 at 8:50 AM, Jeff McCune
je...@puppetlabs.comjavascript:
wrote:
On Tuesday, May 22, 2012, Dan White wrote:
I found an answer to this particular issue. Thanks for the reminder so
I can share the answer:
I found the hiera/yaml way to indicate an empty array !
So, to use my earlier example:
users:
beast:
username : beast
uid :
ingroups :
- ''
info : Let's see if this works
Then, with a hiera call, I get :
{beast={ingroups=[], uid=, username=beast,
info=Let's see if this works}
This is actually a non-empty array hat had one element, the empt string.
OK, I had a look today. Much of the behavior of hashes and arrays whose
elements are not defined has been resolved in Puppet 3.0.0rc. If you could
try that out it would help us make sure your problem has actually been
solved in Puppet.
As to how to specify an empty array as the value of a hash key using Hiera
and Puppet, this is the way:
---
username: beast
uid:
ingroups: []
info: Let's see if this works
Notice it's just an empty set of square braces, no empty string.
This clearly seems like a bug in puppet and how it is handling Hash
values. I'll take a look more as soon as I get into the office.
It is a bug, luckily we've fixed it in Puppet 3.0.x. Please give the
release candidates a try.
-Jeff
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] RHEL 6 and ActiveRecord issues
Could you post those notes? -removing all gems and installing active-record 3.0.11 did not fix the problem On Saturday, May 5, 2012 10:32:10 PM UTC+5:30, iceberg wrote: What I found was that you need to gem uninstall ALL of the active* gems, then reinstall and specify 3.0.xx version. Just replacing ActiveRecord won't fix the problem. I have more notes in my wiki at work, if that doesn't do it I'll grab them for you Monday. On Friday, May 4, 2012 8:52:53 AM UTC-7, Jeff Chapin wrote: Is anyone successfully running a puppet master with stored configs on RHEL 6? If so, would they be able to share version information or setup documentation? Thanks, Jeff On Tue, May 1, 2012 at 1:57 PM, Jeff Chapin jeff@uni.edujavascript: wrote: All, I am trying to install puppet master version 2.7.13 on Red Hat Enterprise Linux 6, and utilize stored configs. I followed the guide here: http://projects.puppetlabs.com/projects/1/wiki/Using_Stored_Configuration When I run puppet --noop on one of the clients, I get the following error: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload active_record: uninitialized constant ActiveRecord warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Googling this error has a smattering of hits, including one that recommends using the 3.0.11 version of the Active Record gem, but I get the same error. I have installed both the 3.2.3 and 3.0.11 versions of the ActiveRecord gem (3.0.11 was recomended here: https://groups.google.com/group/puppet-users/browse_thread/thread/55f29e9454ad5675 ) This error occurs regardless of the DB backend I tie to. I have tried both the postgres and mysql documentation. # ruby --version ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] # puppet --version 2.7.13 # puppetmasterd --version 2.7.13 I have searched the puppetlabs issue tracker and found a possibly related issue:Debian Squeeze package puppetmaster: Could not autoload active_record: uninitialized constant ActiveRecord(http:// projects.puppetlabs.com/issues/14080). This indicates that I may be missing a related package or gem -- but I don't even know where to start tracking down the missing package. On IRC it has been suggested that I install rubygem-activerecord, but this does not appear to be in the EPEL repo -- Haus on IRC found a 2.3.8 version of this package that I installed to test, but I get the same error. I managed to get a different error briefly, when I was running multiple versions of activerecord, activeresource and activesupport -- installed through a mix of gem and yum. Deleting the non-yum versions returned me to the existing error, so I am chalking that up as a fluke at this time. Any help would be appreciated. Jeff -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet...@googlegroups.comjavascript: . To unsubscribe from this group, send email to puppet-users...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- Jeff Chapin, Assistant Systems/Applications Administrator ITS-IS, University of Northern Iowa Phone: 319-273-3162 Email: jeff@uni.edu javascript: -- 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/-/t8CECMAvwqMJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
