[Puppet Users] Hi!!!
http://tagolpc.com.ua/cxsu/xzbqbmsqinss.ssbgtsvz -- 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.
[Puppet Users] Re: mcollective setup question
I've been having the same issue with my new MCollective setup and a quick
look in the client.rb file reveals this function on the line 99 area:
raise(MsgDoesNotMatchRequestID, Message reqid #{requestid} does not match
our reqid #{reply.requestid}) unless reply.requestid == requestid
rescue SecurityValidationFailed = e
Log.warn(Ignoring a message that did not pass security validations)
and looking in the logs you can find the request ID for the mco command:
base.rb:178:in `create_request' Encoding a request for agent 'discovery' in
collective mcollective with request id 2f1214f66d1f5741bb79daa26ed6316e
client.rb:51:in `sendreq' Sending request 2f1214f66d1f5741bb79daa26ed6316e
to the discovery agent with ttl 60 in collective mcollective
So it would seem that the client is expecting the reponse from the server
to have the same requestid as the one it sent, but for some reason they are
different. If the server is using SSL to generate/verify these request id's
it may point to a cert or pki mismatch issue but so far I haven't been able
to sport anything wrong with either. Ruvy isn't my strong suit so it will
probably need a ruby dev or one of the puppet team to explain how these ids
are generated and verified.
--
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] Hi!!!
Ugh. Sorry, everybody. Obviously, I hope you haven't clicked on this link since it wasn't me who sent it. I'm doing the usual stuff -- new strong password, refreshed app tokens, single-use passwords in other apps, etc. ... On Sun, Jun 2, 2013 at 5:53 AM, steve . leftath...@gmail.com wrote: http://tagolpc.com.ua/cxsu/xzbqbmsqinss.ssbgtsvz -- 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. -- 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] Packages for Ubuntu 13.04 Raring
I shipped this with installing the precise packages. For now it seems to work with Version 3.2.x. -- 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.
[Puppet Users] AWS Node Create with Puppet Cloud Provisioning : Listing Key Names
Hi folks. hopefully this is a easy newbie question you may be able to answer. I'm trying to deploy a AWS EC2 node using puppet node_aws create ... but am getting stuck at puppet node_*aws list_*keynames. Unfortunately it doesn't return anything. I created/downloaded/ssh-add'ed the key pair and created a security group which I hope is allowing inbound SSH/port from my source IP, but no luck. To note, I do get a AWS EC2 instance listing from pupet node_aws list Any ideas? Thanks in advance! $ puppet node*aws create --type t1.micro --image ami-ad36fbc4 --keyname pp_* kp err: Unrecognized key name: pp*kp (Suggestion: use the puppet node*aws list*keynames action to find a list of valid key names for your account.) err: Try 'puppet help node*aws create' for usage $ puppet node*aws list*keynames $ -- 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.
[Puppet Users] AWS Node Create with Puppet Cloud Provisioning :
hi folks. hopefully this is a easy newbie question you may be able to answer. i'm trying to setup a AWS node and am getting stuck at puppet node_aws list_keynames. Unfortunately it doesn't return anything. I created/downloaded/ssh-add'ed the key pair and created a Security Group that hopefully allows my source IP across SSH/22 for inbound connections, but no luck. I do however get a list of my defined AWS EC2 instances from puppet node_aws list Any ideas? $ puppet node_aws create --type t1.micro --image ami-ad36fbc4 --keyname pp_kp err: Unrecognized key name: pp_kp (Suggestion: use the puppet node_aws list_keynames action to find a list of valid key names for your account.) err: Try 'puppet help node_aws create' for usage -- 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.
[Puppet Users] puppet master --compile
Hi, I'm looking into using puppet master --compile to set up some tests. However it's unclean how I can use this: - do I *need* to run this on the master? - what are the exit statuses that I need to catch? - why does it update /var/lib/puppet/yaml/node/nodename.yaml after such a run? Thanks, Rudy -- 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.
[Puppet Users] Re: AWS Node Create with Puppet Cloud Provisioning : Listing Key Names
Eureka !!! Though I created my key pairs, it didn't sink in that I created it in the Amazon Oregon region. Be default puppet node_aws create (or list_keynames) defaults to the east coast Virginia region. Once I specified the region to reference my predefined key pair within the respective node_aws commands, I was able to launch my AMI instance. =) $ puppet node_aws create --keyname pp_kp --region=us-west-2 --type t1.micro --image ami-77be2f47 notice: Creating new instance ... notice: Creating new instance ... Done notice: Creating tags for instance ... notice: Creating tags for instance ... Done notice: Launching server i-24285d11 ... ### notice: Server i-24285d11 is now launched On Sunday, June 2, 2013 1:50:33 PM UTC-7, frsc...@gmail.com wrote: Hi folks. hopefully this is a easy newbie question you may be able to answer. I'm trying to deploy a AWS EC2 node using puppet node_aws create ... but am getting stuck at puppet node_*aws list_*keynames. Unfortunately it doesn't return anything. I created/downloaded/ssh-add'ed the key pair and created a security group which I hope is allowing inbound SSH/port from my source IP, but no luck. To note, I do get a AWS EC2 instance listing from pupet node_aws list Any ideas? Thanks in advance! $ puppet node*aws create --type t1.micro --image ami-ad36fbc4 --keyname pp_*kp err: Unrecognized key name: pp*kp (Suggestion: use the puppet node*aws list*keynames action to find a list of valid key names for your account.) err: Try 'puppet help node*aws create' for usage $ puppet node*aws list*keynames $ -- 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.
[Puppet Users] Unknown function validate_bool when trying puppet labs apache class
New to puppet. I am trying to use the Apache class from puppet labs found here: https://github.com/puppetlabs/puppetlabs-apache When it runs agent --test on my test environment I get: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Unknown function validate_bool at /etc/puppet/modules/apache/manifests/init.pp:43 on node slave Running on Ubuntu 12.04 with puppet 2.7.11-1ubuntu2.2 installed from the default Ubuntu repository . Looking in the files from the class I see calls to the function validate_bool, but don't see it defined. If there some base/pre-requisite class that I needed? Don't see any mention in the readme file. Also, these classes from puppetlabs github, is there a way to tell what version they would work with? -- 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] Unknown function validate_bool when trying puppet labs apache class
If you take a look in Modulefile in the root of the module you can see the other dependencies. You're going to need 'stdlib' and probably 'concat' as well. You can install them with either 'puppet module install puppetlabs-stdlib' type commands or just grab them from git also. On Sun, Jun 2, 2013 at 6:34 PM, Francisco Reyes franci...@natserv.netwrote: New to puppet. I am trying to use the Apache class from puppet labs found here: https://github.com/puppetlabs/puppetlabs-apache When it runs agent --test on my test environment I get: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Unknown function validate_bool at /etc/puppet/modules/apache/manifests/init.pp:43 on node slave Running on Ubuntu 12.04 with puppet 2.7.11-1ubuntu2.2 installed from the default Ubuntu repository . Looking in the files from the class I see calls to the function validate_bool, but don't see it defined. If there some base/pre-requisite class that I needed? Don't see any mention in the readme file. Also, these classes from puppetlabs github, is there a way to tell what version they would work with? -- 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. -- 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] Unknown function validate_bool when trying puppet labs apache class
On Sunday, June 2, 2013 6:48:41 PM UTC-4, Ashley Penney wrote: If you take a look in Modulefile in the root of the module you can see the other dependencies. Thanks. That will help in future installs. You're going to need 'stdlib' That one fixed it. and probably 'concat' as well. That one I could not install (not found by concat or puppetlabs-concat, but it seems was not needed so not an issue. You can install them with either 'puppet module install puppetlabs-stdlib' Is there a way to list all the available modules? Or basically anything in the git repository should be able to be installed that way? Thanks much for the help. Although there is quite a lot of content and concepts to go over, so far looking very manageable. My only other previous experience with a configuration management system was trying to learn Cfengine. Found that much harder to learn and eventually gave up on it. -- 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.
[Puppet Users] puppet module install vs github
Just learnt about the function puppet module install today (thanks Ashley). Which is more up to date github or what one gets from module install? I expected they would be the same, but doing md5 comparison of the manifest files shows they are different. The one file I was most surprised was the README file. The one in github has much more info. So I guess even if installing from module install, may still be good to go to github for the documentation. Did I miss some additional info/docs in the files pulled from module install? Not seeing anything besides the readme that looks like documentation. Another big different in the README was that the git version does not list dependencies. That is one piece of information I think should be present in both. -- 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] puppet module install vs github
On 3 June 2013 11:38, Francisco Reyes franci...@natserv.net wrote: Just learnt about the function puppet module install today (thanks Ashley). Which is more up to date github or what one gets from module install? the puppet module install command installs modules from puppet forge. a lot of people use github for the code for those modules but it is a manual process to upload to puppet forge. It is usually a point in time release which will usually be the same as a tag on github. if you clone a module from github you are getting the HEAD of the source tree and not a tag unless you check out that tag. So there will probably be differences in what you get from github and what you get from puppet forge. I tend to use puppet forge as a way to publish official releases of modules and github for keeping track of my development. So as a general rule use puppet forge unless you need those unreleased changes or want to help with development of a module. I expected they would be the same, but doing md5 comparison of the manifest files shows they are different. It will vary wildly for each module. See above. The one file I was most surprised was the README file. The one in github has much more info. So I guess even if installing from module install, may still be good to go to github for the documentation. Did I miss some additional info/docs in the files pulled from module install? Not seeing anything besides the readme that looks like documentation. Another big different in the README was that the git version does not list dependencies. That is one piece of information I think should be present in both. Again dependencies are only relevant for modules installed for puppet forge -- 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. -- 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.
[Puppet Users] Re: I have some trouble with starting puppet-dashboard service :(
when i try to start service,but i can't see any error log =( [root@ers-devesx06-vm235 share]# cd puppet-dashboard/ [root@ers-devesx06-vm235 puppet-dashboard]# ls app certs dbext log Rakefile spec tmp VERSION bin config examples lib public scriptspool vendor [root@ers-devesx06-vm235 puppet-dashboard]# cd log [root@ers-devesx06-vm235 log]# ls development.log development.log-20130601 production.log production.log-20130531 [root@ers-devesx06-vm235 log]# cat production.log [root@ers-devesx06-vm235 log]# /etc/init.d/puppet-dashboard start Starting Puppet Dashboard: = Booting WEBrick = Rails 2.3.17 application starting on http://0.0.0.0:3000 [FAILED] spencer hong於 2013年5月30日星期四UTC+8上午10時50分01秒寫道： Hi all: good day! when i want to start puppet-dashboard,i got this message below [root@ers-devesx06-vm235 puppet-dashboard]# /etc/init.d/puppet-dashboard start Starting Puppet Dashboard: config.gem: Unpacked gem rspec-1.3.2 in vendor/gems h as no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification file. Ru n 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no specificatio n file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rack-1.1.6 in vendor/gems has no specification file. Ru n 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification file. R un 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no specification f ile. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no specifi cation file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification file. Ru n 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem json_pure-1.7.7 in vendor/gems has no specification fil e. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification file. Ru n 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no specification file . Run 'rake gems:refresh_specs' to fix this. = Booting WEBrick = Rails 2.3.17 application starting on http://0.0.0.0:3000 [FAILED] [root@ers-devesx06-vm235 puppet-dashboard]# service mysqld start Starting mysqld: [ OK ] [root@ers-devesx06-vm235 puppet-dashboard]# /etc/init.d/puppet-dashboard start Starting Puppet Dashboard: config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specificati on file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification file. Run 'rake gems:refr esh_specs' to fix this. config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rack-1.1.6 in vendor/gems has no specification file. Run 'rake gems:refr esh_specs' to fix this. config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification file. Run 'rake gems:ref
[Puppet Users] Re: I have some trouble with starting puppet-dashboard service :(
Here is the log~ [root@ers-devesx06-vm235 puppet-dashboard]# ./script/server -e production = Booting WEBrick = Rails 2.3.17 application starting on http://0.0.0.0:3000 Database isn't the current migration version: expected , got 0 You must either run 'rake db:migrate' or set environmental variable NO_MIGRATION_CHECK spencer hong於 2013年5月30日星期四UTC+8上午10時50分01秒寫道： Hi all: good day! when i want to start puppet-dashboard,i got this message below [root@ers-devesx06-vm235 puppet-dashboard]# /etc/init.d/puppet-dashboard start Starting Puppet Dashboard: config.gem: Unpacked gem rspec-1.3.2 in vendor/gems h as no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification file. Ru n 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no specificatio n file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rack-1.1.6 in vendor/gems has no specification file. Ru n 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification file. R un 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no specification f ile. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no specifi cation file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem sass-3.1.2 in vendor/gems has no specification file. Ru n 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem json_pure-1.7.7 in vendor/gems has no specification fil e. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem haml-3.1.2 in vendor/gems has no specification file. Ru n 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem factory_girl-1.3.3 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem daemons-1.0.10 in vendor/gems has no specification file . Run 'rake gems:refresh_specs' to fix this. = Booting WEBrick = Rails 2.3.17 application starting on http://0.0.0.0:3000 [FAILED] [root@ers-devesx06-vm235 puppet-dashboard]# service mysqld start Starting mysqld: [ OK ] [root@ers-devesx06-vm235 puppet-dashboard]# /etc/init.d/puppet-dashboard start Starting Puppet Dashboard: config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specificati on file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no specification file. Run 'rake gems:refr esh_specs' to fix this. config.gem: Unpacked gem will_paginate-2.3.15 in vendor/gems has no specification file. Run 'rake gems:refresh_specs' to fix this. config.gem: Unpacked gem rack-1.1.6 in vendor/gems has no specification file. Run 'rake gems:refr esh_specs' to fix this. config.gem: Unpacked gem mocha-0.9.7 in vendor/gems has no specification file. Run 'rake gems:ref resh_specs' to fix this. config.gem: Unpacked gem rspec-rails-1.3.4 in vendor/gems has no specification file. Run 'rake ge ms:refresh_specs' to fix this. config.gem: Unpacked gem thoughtbot-shoulda-2.10.2 in vendor/gems has no specification file. Run
