[Puppet Users] New Puppet Setup
Team, I am trying to setup new Puppet master server on Centos 5.4. I am getting the below error which running yum install puppet-server puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems -- Missing Dependency: ruby-shadow is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems -- Missing Dependency: ruby-augeas is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) Error: Missing Dependency: ruby-augeas is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) Error: Missing Dependency: ruby-shadow is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest I am using the below puppet respository [puppetlabs] name=Puppet Labs Packages baseurl=http://yum.puppetlabs.com/el/$releasever/products/$basearch/ enabled=1 gpgcheck=1 gpgkey=http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs Also my Current ruby version is as below ruby 1.8.5 (2006-08-25) [i386-linux] Thanks, Munna -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] New Puppet Setup
Hi Munna, You can find those packages in the EPEL repository. See http://fedoraproject.org/wiki/EPEL. Den On 25/06/2012, at 17:34, Munna S 19.mu...@gmail.com wrote: Team, I am trying to setup new Puppet master server on Centos 5.4. I am getting the below error which running yum install puppet-server puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems -- Missing Dependency: ruby-shadow is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems -- Missing Dependency: ruby-augeas is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) Error: Missing Dependency: ruby-augeas is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) Error: Missing Dependency: ruby-shadow is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest I am using the below puppet respository [puppetlabs] name=Puppet Labs Packages baseurl=http://yum.puppetlabs.com/el/$releasever/products/$basearch/ enabled=1 gpgcheck=1 gpgkey=http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs Also my Current ruby version is as below ruby 1.8.5 (2006-08-25) [i386-linux] Thanks, Munna -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] New Puppet Setup
Hello Den, I just used below puppetlabs repo and i was able to install puppet server along with the dependency. rpm -ivh http://yum.puppetlabs.com/el/5/products/i386/puppetlabs-release-5-1.noarch.rpm Thanks for quick help Thanks, Munna On Mon, Jun 25, 2012 at 1:08 PM, Denmat tu2bg...@gmail.com wrote: Hi Munna, You can find those packages in the EPEL repository. See http://fedoraproject.org/wiki/EPEL. Den On 25/06/2012, at 17:34, Munna S 19.mu...@gmail.com wrote: Team, I am trying to setup new Puppet master server on Centos 5.4. I am getting the below error which running yum install puppet-server puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems -- Missing Dependency: ruby-shadow is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) puppet-2.7.17-1.el5.noarch from puppetlabs has depsolving problems -- Missing Dependency: ruby-augeas is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) Error: Missing Dependency: ruby-augeas is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) Error: Missing Dependency: ruby-shadow is needed by package puppet-2.7.17-1.el5.noarch (puppetlabs) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest I am using the below puppet respository [puppetlabs] name=Puppet Labs Packages baseurl=http://yum.puppetlabs.com/el/$releasever/products/$basearch/ enabled=1 gpgcheck=1 gpgkey=http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs Also my Current ruby version is as below ruby 1.8.5 (2006-08-25) [i386-linux] Thanks, Munna -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
[Puppet Users] puppet freezes on FUTEX_WAKE_PRIVATE
Hi, i just want to ask whether somebody else has this problem of mine and
if it can be solved.
Many of my ( 30+ ) puppet installation freeze up after some time. The
process is waiting for some private futex, but it stays like that forever.
This is what strace looks like when the problem occures:
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406739, {1340611695,
739433265}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 741431552}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406741, {1340611695,
751431552}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 753429831}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406743, {1340611695,
763429831}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 765427460}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406745, {1340611695,
775427460}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 777424282}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406747, {1340611695,
787424282}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 789423203}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406749, {1340611695,
799423203}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 801422477}) = 0
[pid 29173] futex(0x3d35ce7ab0, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 29173] futex(0x3d35ce7a84,
FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406751, {1340611695,
811422477}, ) = -1 ETIMEDOUT (Connection timed out)
[pid 29173] clock_gettime(CLOCK_REALTIME, {1340611695, 813420142}) = 0
This happens on RHEL6 with puppet from RF (puppet-2.7.9-1.el6.rf,
ruby-1.8.7.352-7.el6_2.x86_64) and also with some mandriva I happen to have
(puppet-2.7.13-1mdv2010.2, ruby-1.8.7.p249-4.2mdv2010.2)
--
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/-/VnnAQDuVe68J.
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.
[Puppet Users] Error 400 on SERVER: invalid value for Integer
Hello gurus, I'm getting this error every once in a while. Not agent specific, and the next run all goes well. I saw this mentioned in another thread, but without an answer. Could not retrieve catalog from remote server: Error 400 on SERVER: invalid value for Integer: eNqNVlmTqkoSfp9fwfTDPIzTUiCrEfcBFUFxYRFRXzpKKJR9KRbx1w/Sfc70\nOTfiztUQqzKTqswvv/rg/f2d+GdZXzsyu4bIraZ6neeomk53mYem0yV0K/wP\ngkCPPChhFWTplKABRb8D7p1mCQpMWWrK8GOaYZgJIEaAngLQx6cwQVPCdSsR\nUOO89Dw09hA1xvm4yTzoZykau1nSBzYwrhGeEv2QICJUpiieElad7q3BkqIq\ngTjqN2XZ8Y8fGFx1GhQ1CrwpITDclRUgGsxZjl6Jpjfc4QolJYoRxH0u/wo8\nACjijR1T4G2I9Asv/Vs5EoQbByitGlTiAYFhLZqgx/yY+5Fmm5XRB6IAADeW\nYvu/j0mfWZ8w6Hfk6a+km6CsatiX+OyXHywB/vhpfPNhjNFndihtpkSf1WdQ\nDj2vRBj/siQLvqH2s9B/D4V+R+8jzsAH/YkheH0HZ94vlmPiHfnD9MUBHFTI\nC8opQWZ5RVo6CfMcky/POzUWxvx7Ppkw7ziHpftecQwZB9fBS75u/BhGfdyw\n3B2WXgtLlPQ06ivDdco0v5byV2B9VZblbjYlFvIw8bIEBumAyV906sWH8Jph\nPMyqIEEvpKfEVrYOn7TJX8YPD3Z9/W/vFMO+fbffs7ocHBOG++JJkFao9KH7\nounbAOV/fk397Rewfy/rz8z9gU2AYY/MC83PhsDq3kNf45K89oVOhxF+DYfr\nb+h99ZSi+aGn1Dcq/OSpglJUBu4HRfeMoPpafzArKLM06Rn9P4bdM1x9P7S/\n0Pq3vb74MwjFz70G2tHfoPxCl3gh/YnQp87gLiE+XgG4gknedyZLiXWdEp9y\nwnC9nLx0BIBBaIYbMb6XGEaomxJS/5lNdk84pzqXlofpqu2vhiyVmbpNzdyZ\nCM8uhMKz3PA3S1kLN/FmXa5nUVzwzsoqQgELpyi7zXR/XzFGyZG+jMmboLSh\ngpuDtK25hyk9o/3Bz/zyEh1VJj/VdKBTVrwqdHXSSvbGpMGekwPBBvtdNerI\ny8lRtMmOcrtShZJALmXHUdLRYeLui1rcB5Uht55GlUoQLiekvIB8RR7Z55pG\n9/vEao7QedjhVW1DR3FHFT23bo6/DWpxt3juW/1i7CRXaNHlMpoIWUiRnW4e\nov0Sgr3pjupK1c7P7YKnQz5SN+a+jVfk7v7c2aF8e3i+dWo3bbU6VMfFKOqr\nFy8Gd96hSDWPxRK4+JYr3Vqu77W8qHFUkfmucZWcC/zOYFzjjz8+1bJ/EqDy\nZ7upMft10n8T3F69sxiWAf5GyASG/4eTnwLrorL6m4r8otK3ZHpx+sEU789M\nidzJtp/JM2m9PuWm6+3Wd6yDzWTdTQTTlXQOxyvDUNL1nZM7QwJKvVYV6rnf\nb6otY6mmoc/XgL9PpMpNg9kzKk+jTFsrK2Pp2nw118qcdcRQ58H8dD6V3KMu\n9ofUdoAlJMWFW5bRiYwY90m6vLnddYYBnGV68H23Jq2lpNacaFPxgT5p8czI\n2rytDYdUTCgdTg/XKx8d2Jz37Ly71dHyftYSbRcKjLQxpV4u6dlmdUqNPF24\nJ7pszSVvzA7tYWSnM1u3W+Q7QiMrTCLZ+R4mhi3IvLJUDJPEdyu5nxD5EDIl\njkbtJuM3aHvLzvqs9vUww+FV9jYkFWdZ0dXiXCa1eT6fCFiOENBmRX+wOPCA\nnDRphBfUR2lr3Ss4q2l9VwWKFjl20e1JhjKr8vJqhSTPG/pa4WXsmU18U+n2\nqOkjcFy5lC0KFt7tDlATbazZF7fR186JU8kquZBhuFOYVdFYkZX5Ktm5XH8O\nebV4tqG2n6mpPdpKiSSqszPd5lgKKmV9V66XWo3mKTzevUo0bb5GYq4tG3OR\nejeHpMsT9vVU8Cer7mK3c926PY98mVOitOK4Qvc4M10WvjMTCtO2d9VcMJa6\nnEaiT5UPDswOtweo81nDkgZcO63pX9MNI/EMn0ebjX9I/MXCW4ioGxWx3shM\nWwaGpJxv2sVTeT6kae7OAlt0Z8mCllg/ii4KsHmluEHgek9VfSrU43y8JxHS\nPGkfkEAtVZ32lRnXPGSwKoLHDhabE+0np+fAa2kh01e2UhJnuZQv25HLgM5y\nxNkWqJblHuq2LV1Pi4WQU3wnSWKwfgYHkMk3jTx3QbPaWbxSLQTkj0LL1aX1\npUCj482/PAKv2RdCuEmpVujKtaQxakjmlXGyS3KxDqg66x6rZbOCkhmhLUc6\nfKEJDypml5v5hGzKU3gnyWLNyjOVa582dbouI3EBkkB+qEr8aOXjedY9RrAp\nQFQWfEJCBOVqw1U29JDyCJ6NJ627rS93RyrOVzpvr7bxYkfq0OlVt01hoEaz\nKL9crvostmIRQ/Z+ZbnVpl07tbe6oxON7V68l2JZa5cgFQEjGDHshJm2uTT7\nQB45KxzeTgJuVvR+5TALKQvPddXwRWv+UL6vNwOM3Cz1Pl8aaIadsCzz9l/J\n7379\n Any ideas how I can prevent it? To me 400 implies that the client is responsible for the error, not the puppetmaster. Thanks, -- 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/-/kVQqa5_A0GsJ. 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.
Re: [Puppet Users] Re: Calling custom functions from functions, parameter weirdness
Hi,
Ruby DSL and templates (via e.g. inline_template) would have the same
problem, unless this was handled properly on the function's side.
KW
On Friday, 22 June 2012 18:53:55 UTC+1, ad wrote:
Josh,
I appreciate the help. Using function_foo(['bar']) rather than
function_foo('bar') works as expected. I'm sure this will also solve the
same issue I was having calling a custom function from a Ruby DSL defined
type.
Cheers,
Adam
On Friday, June 22, 2012 12:01:24 PM UTC-5, Josh Cooper wrote:
On Fri, Jun 22, 2012 at 9:13 AM, ad adam.denn...@gmail.com wrote:
I just tested this on CentOS/Puppet 2.7.12 with the same result.
- Adam
On Friday, June 22, 2012 10:20:52 AM UTC-5, ad wrote:
This is on Windows running 2.7.16. I haven't tested on Linux or other
versions. I'm still relatively new to Puppet and haven't used custom
functions before, so wanted to run this by the list before filing a bug.
When calling custom functions from functions, arguments are being
converted to decimal arrays. That is, passing the argument 'bar' from a
custom function to another function results in
arg[0]: 98
arg[1]: 97
arg[2]: 114
Here's a full example in case I'm doing something wrong here.
Function 1:
module Puppet::Parser::Functions
newfunction(:foo) do |args|
puts 'args[0]:' + args[0].to_s
puts 'args.size:' + args.size.to_s
end
end
Function 2:
module Puppet::Parser::Functions
newfunction(:foo2) do |args|
Puppet::Parser::Functions.**autoloader.loadall
function_foo('from_function')
Since you are calling foo with a single argument, I believe the args in
function foo is a string, not an array. If you instead say
`function_foo(['from_function'])`, it should do what function foo expects.
end
end
A manifest:
foo('from_manifest')
foo2()
Puppet Agent run Result:
args[0]:from_manifest
args.size:1
args[0]:102
args.size:13
13 is the string length of 'from_function', and 102 is the decimal
representation of 'f'.
- Adam
--
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/-/-eqfuh4NRI0J.
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.
--
Josh Cooper
Developer, Puppet Labs
--
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/-/UAzUIA3jQWkJ.
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.
[Puppet Users] Re: OT: Monitoring solutions
Hi, Have a look at https://github.com/monitoringsucks/ KW On Sunday, 24 June 2012 21:45:50 UTC+1, k...@mocker.org wrote: All, I'm curious what monitoring solutions everyone is using and recommend, some of the ones I've been looking at recently: Nagios: Old stand-by, used quite a bit but doesn't provide a cohesive solution (have to have add-ons for graphing, etc..) Zabbix: Currently using, decent but seems to be a bit resource intenstive Zenoss: Never used, no opinion yet Icinga: Never used, Nagios fork that I have no opinion on yet Shinkin: Never used, no opinion yet Centreon: Never used, no opinion yet There are (lots) more out there, recommendations from someone who has used the product would be great to hear. Obviously integration into puppet would be a great feature to have. :) Thanks, Kyle Sexton -- 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/-/coe-pqnA37YJ. 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.
AW: [Puppet Users] OT: Monitoring solutions
We got a totally integrated solution made up with Puppet, Icinga and stored resources. When integrating a new host into Puppet, one just has to wait until it gets monitored in Icinga - no more work to do. Some details are found here: http://www.bernd-adamowicz.de/tag/monitoring/ Bernd -Ursprüngliche Nachricht- Von: puppet-users@googlegroups.com [mailto:puppet- us...@googlegroups.com] Im Auftrag von Kyle Sexton Gesendet: Sonntag, 24. Juni 2012 22:46 An: puppet-users@googlegroups.com Betreff: [Puppet Users] OT: Monitoring solutions All, I'm curious what monitoring solutions everyone is using and recommend, some of the ones I've been looking at recently: Nagios: Old stand-by, used quite a bit but doesn't provide a cohesive solution (have to have add-ons for graphing, etc..) Zabbix: Currently using, decent but seems to be a bit resource intenstive Zenoss: Never used, no opinion yet Icinga: Never used, Nagios fork that I have no opinion on yet Shinkin: Never used, no opinion yet Centreon: Never used, no opinion yet There are (lots) more out there, recommendations from someone who has used the product would be great to hear. Obviously integration into puppet would be a great feature to have. :) Thanks, Kyle Sexton -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] OT: Monitoring solutions
On Sun, Jun 24, 2012 at 03:45:50PM -0500, Kyle Sexton wrote: All, I'm curious what monitoring solutions everyone is using and recommend, some of the ones I've been looking at recently: Nagios: Old stand-by, used quite a bit but doesn't provide a cohesive solution (have to have add-ons for graphing, etc..) Zabbix: Currently using, decent but seems to be a bit resource intenstive Zenoss: Never used, no opinion yet Icinga: Never used, Nagios fork that I have no opinion on yet Shinkin: Never used, no opinion yet Centreon: Never used, no opinion yet OpenNMS[1] is my personal favourite at the moment. It has a bit of a learning curve but works great once you get over it. In terms of configuration I manage OpenNMS config itself in puppet but when it comes to configuring nodes for monitoring I use the automated service discovery capabilities of OpenNMS. Once you 'teach' it about the services you're running and how to discover them it's just a case of triggering a service scan after a node is built. I do this via a REST call after the initial puppet run. OpenNMS will periodically re-scan my nodes and pick up any changes (or one can trigger a re-scan manually when/if needed). I tried many things before but OpenNMS works best for me so far. Cheers, Andrew. [1] http://www.opennms.org/ -- [ a...@zx23.net ] -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] system users class hogging whole cpu
Anyone please
On Thursday, 14 June 2012 18:07:32 UTC+5, Azfar Hashmi wrote:
Peter,
What should I change in nns config to change its behavior without breaking
any other function. BTW all are Debian 6 but on different clouds.
On Tue, Jun 12, 2012 at 8:40 PM, Azfar Hashmi azfarhas...@gmail.comwrote:
Hi,
Sorry I forgot to add the code, below is my class.
class std_debian_users {
#We create users
users::useraccount { user1:
ensure = present,
fullname = user,
password =
'$6$UCKmcpzC$.bgwFSgNNaauzWk7WUyO9dohTRRy5Li.Xd0KddJxICEECMESAbt1XThDc770V1hYiyGBdc5vekq5N4njQv6bZ1',
shell = '/bin/bash'
}
users::useraccount { user2:
ensure = present,
fullname = user2,
password =
'$6$qBa42BcV$oKXSwPgUKlvDTX71U5Of42wP9G8CgXUn/UYQei5bKiN5xXowtQaFr/n1wiwe/BTpykrFkaOngBPSrHen7rVmV1',
shell = '/bin/bash'
}
users::useraccount { user3:
ensure = present,
fullname = user3,
password =
'$6$atO.haGi$28ZSmzB/fcHm3wcqFWxjUcGvEha0Ea0h2RYHUwvqjjbxjIw881GJxgPScI.baoE38iEWwrAaZfUtgu5pCS9NJ/',
shell = '/bin/bash'
}
users::useraccount { user4:
ensure = present,
fullname = user4,
password =
'$6$RdmLIN/Q$g2PpxbYrmv4sBRHIVn3k8xgc0ZbbaCux3RiBKqArM7A.RkGzuJajaD3cbZUYvHAz63iTEdA1y88SDtGz/h8nH/',
shell = '/bin/bash'
}
#users::useraccount { user5:
# ensure = present,
# fullname = user5,
# password =
'$6$998jabhr$yEDSXs4/cdZxAmRjj2H7XHIPngRYsBycGfhFyrcfSeaTnaFuUIcYkZu7bMThbN5Q9p5zlCmzu1PpZXpt3yqIe/',
# shell = '/bin/bash'
#}
users::useraccount { user6:
ensure = present,
fullname = user6,
password =
'$6$5O7svvCF$o6IyT0mTIhd8GeS/C4.Cp.UR4dXo.nwJwWzGVXtN6vGe8AvzF/y.XrbkFR2XLkFt87VauI9z.U6Qtm0pWmOdm/',
shell = '/bin/bash'
}
users::useraccount { user7:
ensure = present,
fullname = user7,
password =
'$6$PUi11dq7$DBjgWj461bZwNv4hKguwownEsU.wmwpuMbAidMGceVs/cr18rrVW.O8ZV2/dwiDLQsZGV38uPQvAfRvcNhaIA/',
shell = '/bin/bash'
}
#SSH Public Keys for users
file { '/home/user1/.ssh/authorized_keys2':
owner = user1,
group = user1,
mode = 0600,
require = Users::Useraccount['user1'],
source = puppet://
sw-zabbix.abc.com/files/standard_debian/home/user1/.ssh/authorized_keys2
,
}
file { '/home/user2/.ssh/authorized_keys2':
owner = user2,
group = user2,
mode = 0600,
require = Users::Useraccount['user2'],
source = puppet://
sw-zabbix.abc.com/files/standard_debian/home/user2/.ssh/authorized_keys2
,
}
file { '/home/user3/.ssh/authorized_keys2':
owner = user3,
group = user3,
mode = 0600,
require = Users::Useraccount['user3'],
source = puppet://
sw-zabbix.abc.com/files/standard_debian/home/user3/.ssh/authorized_keys2
,
}
file { '/home/user4/.ssh/authorized_keys2':
owner = user4,
group = user4,
mode = 0600,
require = Users::Useraccount['user4'],
source = puppet://
sw-zabbix.abc.com/files/standard_debian/home/user4/.ssh/authorized_keys2
,
}
file { '/home/user5/.ssh/authorized_keys2':
owner = user5,
group = user5,
mode = 0600,
require = Users::Useraccount['user5'],
source = puppet://
sw-zabbix.abc.com/files/standard_debian/home/user5/.ssh/authorized_keys2
,
}
file { '/home/user6/.ssh/authorized_keys2':
owner = user6,
group = user6,
mode = 0600,
require = Users::Useraccount['user6'],
source = puppet://
sw-zabbix.abc.com/files/standard_debian/home/user6/.ssh/authorized_keys2
,
}
#file { '/home/user7/.ssh/authorized_keys2':
#owner = user7,
#group = user7,
#mode = 0600,
#require = Users::Useraccount['user7'],
#source = puppet://
sw-zabbix.abc.com/files/standard_debian/home/user7/.ssh/authorized_keys2
,
#}
}
On Tue, Jun 12, 2012 at 11:20 AM, David Schmitt da...@dasz.at wrote:
On 2012-06-11 17:46, Azfar Hashmi wrote:
I have dozens of nodes but on one node the system users class is
taking 100% cpu. I have no issue on other systems. When I disable this
class the puppet client works fine. Tried reinstalling puppet from
scratch but no avail. Any idea why it always hanging at this class?
The NSS configuration on that node is different, causing an adduser call
to run through the complete user directory to find a free uid.
Also, what Peter said.
Best Regards, David
--
Re: [Puppet Users] Re: OT: Monitoring solutions
Hah, this is going to make my search worse! More monitoring solutions to look at. :-) Sent from my iPhone On Jun 25, 2012, at 7:30 AM, Krzysztof Wilczynski krzysztof.wilczyn...@linux.com wrote: Hi, Have a look at https://github.com/monitoringsucks/ KW On Sunday, 24 June 2012 21:45:50 UTC+1, k...@mocker.org wrote: All, I'm curious what monitoring solutions everyone is using and recommend, some of the ones I've been looking at recently: Nagios: Old stand-by, used quite a bit but doesn't provide a cohesive solution (have to have add-ons for graphing, etc..) Zabbix: Currently using, decent but seems to be a bit resource intenstive Zenoss: Never used, no opinion yet Icinga: Never used, Nagios fork that I have no opinion on yet Shinkin: Never used, no opinion yet Centreon: Never used, no opinion yet There are (lots) more out there, recommendations from someone who has used the product would be great to hear. Obviously integration into puppet would be a great feature to have. :) Thanks, Kyle Sexton -- 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/-/coe-pqnA37YJ. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: AW: [Puppet Users] OT: Monitoring solutions
Curious if Icinga has integrated graphing or if it's an add-on since it's based on Nagios. Overall you are pleased with the solution? Sent from my iPhone On Jun 25, 2012, at 7:45 AM, Bernd Adamowicz bernd.adamow...@esailors.de wrote: We got a totally integrated solution made up with Puppet, Icinga and stored resources. When integrating a new host into Puppet, one just has to wait until it gets monitored in Icinga - no more work to do. Some details are found here: http://www.bernd-adamowicz.de/tag/monitoring/ Bernd -Ursprüngliche Nachricht- Von: puppet-users@googlegroups.com [mailto:puppet- us...@googlegroups.com] Im Auftrag von Kyle Sexton Gesendet: Sonntag, 24. Juni 2012 22:46 An: puppet-users@googlegroups.com Betreff: [Puppet Users] OT: Monitoring solutions All, I'm curious what monitoring solutions everyone is using and recommend, some of the ones I've been looking at recently: Nagios: Old stand-by, used quite a bit but doesn't provide a cohesive solution (have to have add-ons for graphing, etc..) Zabbix: Currently using, decent but seems to be a bit resource intenstive Zenoss: Never used, no opinion yet Icinga: Never used, Nagios fork that I have no opinion on yet Shinkin: Never used, no opinion yet Centreon: Never used, no opinion yet There are (lots) more out there, recommendations from someone who has used the product would be great to hear. Obviously integration into puppet would be a great feature to have. :) Thanks, Kyle Sexton -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: AW: [Puppet Users] OT: Monitoring solutions
I use pnp4nagios with icinga, and use the graphite branch (some mods required). Otherwise the RRD setup works well too. On Mon, Jun 25, 2012 at 8:58 AM, Kyle Sexton k...@mocker.org wrote: Curious if Icinga has integrated graphing or if it's an add-on since it's based on Nagios. Overall you are pleased with the solution? Sent from my iPhone On Jun 25, 2012, at 7:45 AM, Bernd Adamowicz bernd.adamow...@esailors.de wrote: We got a totally integrated solution made up with Puppet, Icinga and stored resources. When integrating a new host into Puppet, one just has to wait until it gets monitored in Icinga - no more work to do. Some details are found here: http://www.bernd-adamowicz.de/tag/monitoring/ Bernd -Ursprüngliche Nachricht- Von: puppet-users@googlegroups.com [mailto:puppet- us...@googlegroups.com] Im Auftrag von Kyle Sexton Gesendet: Sonntag, 24. Juni 2012 22:46 An: puppet-users@googlegroups.com Betreff: [Puppet Users] OT: Monitoring solutions All, I'm curious what monitoring solutions everyone is using and recommend, some of the ones I've been looking at recently: Nagios: Old stand-by, used quite a bit but doesn't provide a cohesive solution (have to have add-ons for graphing, etc..) Zabbix: Currently using, decent but seems to be a bit resource intenstive Zenoss: Never used, no opinion yet Icinga: Never used, Nagios fork that I have no opinion on yet Shinkin: Never used, no opinion yet Centreon: Never used, no opinion yet There are (lots) more out there, recommendations from someone who has used the product would be great to hear. Obviously integration into puppet would be a great feature to have. :) Thanks, Kyle Sexton -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
[Puppet Users] Re: Is this possible with Hiera - Puppet Module Development and using Hiera
On Friday, June 22, 2012 6:02:33 PM UTC-5, Peter wrote: I believe by extending the hiera-puppet plugin for module developers to follow a similar convention as hiera for module users would make certain things easier for module developers. By providing the ability to signal the hiera-puppet plugin (using a module-hiera.yaml file (for lack of a better name)) a module developer could reduce complexity and use the DRY principle to setup sane defaults (either in a defaults.pp or in a defaults.yaml file) and than use layer on top specific settings for Operating systems or even Hardware Types (as examples). What I'm getting is that the central idea you propose is to give Hiera's Puppet plugin the ability to collect data not only from different namespaces, as it does now, but also from different classes in each namespace. I also get the impression that you are reserving use of the YAML backend to module users. I'm not prepared to discount your proposal, but I do think you are artificially limiting yourself if as a module developer you refuse to use the YAML backend. If you want more flexibility *today* then that's where you should look. John -- 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/-/9rtwA8ZgbQAJ. 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.
Re: AW: [Puppet Users] OT: Monitoring solutions
On 25.06.2012 14:45, Bernd Adamowicz wrote: We got a totally integrated solution made up with Puppet, Icinga and stored resources. When integrating a new host into Puppet, one just has to wait until it gets monitored in Icinga - no more work to do. Some details are found here: http://www.bernd-adamowicz.de/tag/monitoring/ I have a similar aproach, in theory it works great. However, i am up to 200 Hosts and 5000 Services right now - and puppet at the nagios host needs aprox 45 Minutes for a run to collect/check all the nagios_* stuff. Is this me or are other people experiencing similar results once you go beyond a certain number of objects? Regards Alex -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
[Puppet Users] Re: Extending Puppet using Rubygems
On Saturday, June 23, 2012 7:38:20 PM UTC-5, Kelsey Hightower wrote: There is a pending pull request that adds the ability for Puppet to load Faces, parser functions, and report processors installed via Rubygems. https://github.com/puppetlabs/puppet/pull/873 This means in addition to extending Puppet via pluginsync you would be able to simply do something like this: gem install puppetlabs-cloud-provisioner That would bring in all the gem dependancies and be ready for use without restarting Puppet. For more examples take a look at this ticket: http://projects.puppetlabs.com/issues/7788 I would really love to get some feedback around this, and if you like it, add your vote to the ticket. I will never use it, at least for any system that has a decent native package manager. As I have written before, it is a bad idea to give multiple agents (e.g. gem and yum) overlapping management responsibilities. If it doesn't interfere with anything else, though, nor take substantial effort to maintain then I won't vote against it. John -- 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/-/7O4phpnzUV0J. 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.
AW: AW: [Puppet Users] OT: Monitoring solutions
Yes, we are very satisfied with this solution. Icinga is based on Nagios (I think it's a fork.) and has graphical capabilities. Just check out their homepage to see some examples (https://www.icinga.org/). Bernd -Ursprüngliche Nachricht- Von: puppet-users@googlegroups.com [mailto:puppet- us...@googlegroups.com] Im Auftrag von Kyle Sexton Gesendet: Montag, 25. Juni 2012 14:58 An: puppet-users@googlegroups.com Cc: puppet-users@googlegroups.com Betreff: Re: AW: [Puppet Users] OT: Monitoring solutions Curious if Icinga has integrated graphing or if it's an add-on since it's based on Nagios. Overall you are pleased with the solution? Sent from my iPhone On Jun 25, 2012, at 7:45 AM, Bernd Adamowicz bernd.adamow...@esailors.de wrote: We got a totally integrated solution made up with Puppet, Icinga and stored resources. When integrating a new host into Puppet, one just has to wait until it gets monitored in Icinga - no more work to do. Some details are found here: http://www.bernd-adamowicz.de/tag/monitoring/ Bernd -Ursprüngliche Nachricht- Von: puppet-users@googlegroups.com [mailto:puppet- us...@googlegroups.com] Im Auftrag von Kyle Sexton Gesendet: Sonntag, 24. Juni 2012 22:46 An: puppet-users@googlegroups.com Betreff: [Puppet Users] OT: Monitoring solutions All, I'm curious what monitoring solutions everyone is using and recommend, some of the ones I've been looking at recently: Nagios: Old stand-by, used quite a bit but doesn't provide a cohesive solution (have to have add-ons for graphing, etc..) Zabbix: Currently using, decent but seems to be a bit resource intenstive Zenoss: Never used, no opinion yet Icinga: Never used, Nagios fork that I have no opinion on yet Shinkin: Never used, no opinion yet Centreon: Never used, no opinion yet There are (lots) more out there, recommendations from someone who has used the product would be great to hear. Obviously integration into puppet would be a great feature to have. :) Thanks, Kyle Sexton -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
[Puppet Users] Re: Extending Puppet using Rubygems
On Monday, June 25, 2012 9:19:01 AM UTC-4, jcbollinger wrote: On Saturday, June 23, 2012 7:38:20 PM UTC-5, Kelsey Hightower wrote: There is a pending pull request that adds the ability for Puppet to load Faces, parser functions, and report processors installed via Rubygems. https://github.com/puppetlabs/puppet/pull/873 This means in addition to extending Puppet via pluginsync you would be able to simply do something like this: gem install puppetlabs-cloud-provisioner That would bring in all the gem dependancies and be ready for use without restarting Puppet. For more examples take a look at this ticket: http://projects.puppetlabs.com/issues/7788 I would really love to get some feedback around this, and if you like it, add your vote to the ticket. I will never use it, at least for any system that has a decent native package manager. As I have written before, it is a bad idea to give multiple agents (e.g. gem and yum) overlapping management responsibilities. If it doesn't interfere with anything else, though, nor take substantial effort to maintain then I won't vote against it. John John you make a really good point. Rubygems support would be totally optional. One of my hopes is that once people are able to use rubygems for things like parser functions and report processors we start seeing more OS packages built from those gems. -- 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/-/OS_O3XoInLYJ. 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.
AW: AW: [Puppet Users] OT: Monitoring solutions
Yes, our Puppet master is running very long for collection the stored Nagios resources. We still can cope with this situation but it might get worse in the future which will then make us think about new hardware I guess. Bernd -Ursprüngliche Nachricht- Von: puppet-users@googlegroups.com [mailto:puppet- us...@googlegroups.com] Im Auftrag von Alexander Bien Gesendet: Montag, 25. Juni 2012 15:10 An: puppet-users@googlegroups.com Betreff: Re: AW: [Puppet Users] OT: Monitoring solutions On 25.06.2012 14:45, Bernd Adamowicz wrote: We got a totally integrated solution made up with Puppet, Icinga and stored resources. When integrating a new host into Puppet, one just has to wait until it gets monitored in Icinga - no more work to do. Some details are found here: http://www.bernd-adamowicz.de/tag/monitoring/ I have a similar aproach, in theory it works great. However, i am up to 200 Hosts and 5000 Services right now - and puppet at the nagios host needs aprox 45 Minutes for a run to collect/check all the nagios_* stuff. Is this me or are other people experiencing similar results once you go beyond a certain number of objects? Regards Alex -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
AW: AW: [Puppet Users] OT: Monitoring solutions
Yes, PNP4Nagios is another feature we are using, too. Simply using the performance data created by the Nagios checks is a very good way of having long term monitoring of all boxes. Bernd Von: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] Im Auftrag von Christopher Johnston Gesendet: Montag, 25. Juni 2012 15:00 An: puppet-users@googlegroups.com Betreff: Re: AW: [Puppet Users] OT: Monitoring solutions I use pnp4nagios with icinga, and use the graphite branch (some mods required). Otherwise the RRD setup works well too. On Mon, Jun 25, 2012 at 8:58 AM, Kyle Sexton k...@mocker.orgmailto:k...@mocker.org wrote: Curious if Icinga has integrated graphing or if it's an add-on since it's based on Nagios. Overall you are pleased with the solution? Sent from my iPhone On Jun 25, 2012, at 7:45 AM, Bernd Adamowicz bernd.adamow...@esailors.demailto:bernd.adamow...@esailors.de wrote: We got a totally integrated solution made up with Puppet, Icinga and stored resources. When integrating a new host into Puppet, one just has to wait until it gets monitored in Icinga - no more work to do. Some details are found here: http://www.bernd-adamowicz.de/tag/monitoring/ Bernd -Ursprüngliche Nachricht- Von: puppet-users@googlegroups.commailto:puppet-users@googlegroups.com [mailto:puppet-mailto:puppet- us...@googlegroups.commailto:us...@googlegroups.com] Im Auftrag von Kyle Sexton Gesendet: Sonntag, 24. Juni 2012 22:46 An: puppet-users@googlegroups.commailto:puppet-users@googlegroups.com Betreff: [Puppet Users] OT: Monitoring solutions All, I'm curious what monitoring solutions everyone is using and recommend, some of the ones I've been looking at recently: Nagios: Old stand-by, used quite a bit but doesn't provide a cohesive solution (have to have add-ons for graphing, etc..) Zabbix: Currently using, decent but seems to be a bit resource intenstive Zenoss: Never used, no opinion yet Icinga: Never used, Nagios fork that I have no opinion on yet Shinkin: Never used, no opinion yet Centreon: Never used, no opinion yet There are (lots) more out there, recommendations from someone who has used the product would be great to hear. Obviously integration into puppet would be a great feature to have. :) Thanks, Kyle Sexton -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.commailto:puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet- users+unsubscr...@googlegroups.commailto:users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.commailto:puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.commailto:puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.commailto:puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.commailto:puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.commailto:puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.commailto:puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
[Puppet Users] Re: Is this possible with Hiera - Puppet Module Development and using Hiera
On Friday, June 22, 2012 7:02:33 PM UTC-4, Peter wrote: Hi Joh, On Wednesday, 20 June 2012 03:18:46 UTC+10, jcbollinger wrote: I confess that I don't follow what you are suggesting. Hiera already supports module developers providing data, and module users overlaying their own on top, in the order of their choice. What more would your suggestion provide in that area? And why do module developers need to configure specific locations for (the root of) their data on the filesystem? That should be under the control of module users (== the administrators of the master). What am I missing? Thanks for taking the time to reply. Yes hiera provides support for module developers ... however I would argue that it is limited for example, the hiera-puppet plugin is *hard-coded* to only look for values in the module manifest directory for a file called data.pp. This does allow for a very low threshold for module developers to start implementing hiera in their modules (rename their existing params.pp files). I believe by extending the hiera-puppet plugin for module developers to follow a similar convention as hiera for module users would make certain things easier for module developers. By providing the ability to signal the hiera-puppet plugin (using a module-hiera.yaml file (for lack of a better name)) a module developer could reduce complexity and use the DRY principle to setup sane defaults (either in a defaults.pp or in a defaults.yaml file) and than use layer on top specific settings for Operating systems or even Hardware Types (as examples). Sorry I don't have time right now to provide something in depth but a brief example would be setting up ISCSI, the module I currently have has a complex params.pp file for detecting particular setups. As a module developer I am interested in setting up a hierarchy such that from most specific to least specific: * Hardware_platform * Operating System * Defaults By defining this in the module-hiera.yaml file it makes it very easy for me to signal to the module user what settings override which. I am not suggesting taking any control from module users, and to be explicit user settings (if set) would override the module variable. Hopefully I have done a better job of explaining what I am thinking. Thanks, Peter. I like where this idea is going. You would like a backend, hiera-puppet for now, to be able to lookup default data from the current module directory during parse time. Let's open a ticket (feature request) for this and workout the details. -- 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/-/Ib1O42g43JYJ. 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.
[Puppet Users] Re: Installing hiera
On Friday, June 22, 2012 3:25:49 PM UTC-4, llo...@oreillyauto.com wrote:
My puppet master is behind a proxy and unable to connect to a gem repo, so
I used a different machine to fetch hiera and hiera-puppet gems, and the
hiera-puppet source tarball.
I then did a gem install on them, and I made sure that hiera was in the
path, and extracted the hiera-puppet sources into my modulepath.
I ran puppet agent on the master (as suggested by a comment on
http://puppetlabs.com/blog/first-look-installing-and-using-hiera/ ) and I
also did a service puppetmaster restart.
I set up a basic hierarchy, with just a common layer for right now, and I
added some variables to it.
When I do a puppet run, I get the following error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
no such file to load -- hiera
Did I miss a step, or am I doing something wrong?
I am using puppet 2.7.14 on Lucid for my puppet master, and the agent in
question is running 2.7.16 on Precise.
My hiera.yaml is:
---
:hierarchy:
- common
:backends:
- yaml
:yaml:
:datadir: '/etc/puppet/environments/%{environment}/hieradata'
Did you ever get this working?
--
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/-/FbGipFztkZ0J.
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.
[Puppet Users] Using simulation capability against a specific node
I've just learned of the 'noop' flag on apply and it is really nice. Only, I can't figure out how to get it to do what I want and I wonder if I misunderstand how it's supposed to be used. I've got several different types of nodes in a cluster where each type gets some combination of the modules on puppetmaster applied to them. So, when I change a module, I was thinking 'puppet apply --noop' would allow me to see what that change would look like on a node of that type. Currently, it seems to compare to the current system - the puppetmaster in this case. So is there a way to do this same sort of simulation against a specific node? Or elsewhere I should be looking? Any pointers are greatly appreciated. Thanks, --tim -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
[Puppet Users] Re: Using simulation capability against a specific node
On Monday, June 25, 2012 9:39:13 AM UTC-4, williamstw wrote: I've just learned of the 'noop' flag on apply and it is really nice. Only, I can't figure out how to get it to do what I want and I wonder if I misunderstand how it's supposed to be used. I've got several different types of nodes in a cluster where each type gets some combination of the modules on puppetmaster applied to them. So, when I change a module, I was thinking 'puppet apply --noop' would allow me to see what that change would look like on a node of that type. Currently, it seems to compare to the current system - the puppetmaster in this case. So is there a way to do this same sort of simulation against a specific node? Or elsewhere I should be looking? Any pointers are greatly appreciated. Thanks, --tim I think what you want here is to run the follow command on the specific node: *puppet agent* --test --*noop* -- 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/-/qYTU-X6vx4AJ. 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.
Re: [Puppet Users] OT: Monitoring solutions
Hi, Original Message Subject: [Puppet Users] OT: Monitoring solutions From: Kyle Sexton k...@mocker.org To: puppet-users@googlegroups.com Date: 2012-06-24 22:45 Icinga: Never used, Nagios fork that I have no opinion on yet developing using it at work, in combination with pnp4nagios for graphing, plus checkmk for inventory and snmp checks. doing it the puppet way (like many users report that the nagios cookbooks still work) is one of my many todos left. so if you got any insights on that topic, feel free to enhance that page :) https://wiki.icinga.org/display/howtos/Puppet kind regards, Michael -- DI (FH) Michael Friedrich Vienna University Computer Center Universitaetsstrasse 7 A-1010 Vienna, Austria email: michael.friedr...@univie.ac.at phone: +43 1 4277 14359 mobile: +43 664 60277 14359 fax:+43 1 4277 14338 web:http://www.univie.ac.at/zid http://www.aco.net Lead Icinga Core Developer http://www.icinga.org -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] Hiera - can't convert Array into String error
On Thursday, June 14, 2012 1:51:45 AM UTC-4, Mike wrote:
Thanks,
It appears to be something internal to the hiera function, so I'll have to
go digging in there to find out what's going on.
Cheers
Are you in position to **test** the 1.0rc branches of hiera and
hiera-puppet?
On 14/06/2012, at 1:06 AM, Wolf Noble wrote:
I had some issues with using boolean logic with data being fed to me by
hiera. I went for a slightly hacky option of:
might help you, might be a BadIdea(™)
(untested)
class foo::params{
bool_to_be_tempname = hiera('some_TorF_key_as_a_string')
case bool_to_be_tempname {
[tT][rR][uU][eE]: {
bool_to_be = true
}
default: {
bool_to_be = false
}
}
}
On Jun 13, 2012, at 7:40 AM, Michael Knox wrote:
Hi,
I've been moving from extlookup to hiera, and it's generally gone
fairly smoothly, but I've run into a problem with one of our defines ...
I get this error:
err: Could not retrieve catalog from remote server: Error 400 on
SERVER: can't convert Array into String at ...
The define uses an exec to install Perl CPAN modules and sets log
output based on a hiera lookup.
exec{cpan_load_${title}:
cut …
logoutput = hiera('cpan_logoutput'),
}
If I remove that line, everything runs through fine.
The yaml for hiera:
---
cpan_logoutput: true
Any ideas on what could be triggering this error?
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
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.
This message may contain confidential or privileged information. If you
are not the intended recipient, please advise us immediately and delete
this message. See http://www.datapipe.com/legal/email_disclaimer/ for
further information on confidentiality and the risks of non-secure
electronic communication. If you cannot access these links, please notify
us by reply message and we will send the contents to you.
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
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.
--
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/-/2GdyZeaN6DoJ.
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.
Re: [Puppet Users] Using generate() to mine a shadow file hash
Hey Christopher,
Thanks for the reply. I will give this a try this morning. As for your
question about why we want to mine it, we want to change the root password
in out password manager software, have that change the root password on the
puppet master, and then have puppet distribute the hash everywhere. It
makes it easy to keep a single root for all the systems we want it to
manage.
Thanks!
Rob
On Friday, June 22, 2012 6:13:19 PM UTC-4, Christopher Wood wrote:
inline
On Fri, Jun 22, 2012 at 02:42:54PM -0700, Rob B. wrote:
Hey all,
My objective is to set the root password on the puppet master and
then
have root module mine the hash from the shadow file. It seems like it
should work, but I get the error Parameter password failed:
Passwords
cannot include ':' at. I am not sure where it is seeing the :.
Any ideas?
The manifest looks like this:
class root::linuxroot {
user { 'root':
ensure = 'present',
comment = 'root',
uid = '0',
gid = '0',
home = '/root',
password = generate(/pathtoscript/getlinuxhash.sh),
shell= '/bin/bash',
}
}
And the getlinuxhash.sh looks like this:
#!/bin/sh
HASHPASS=$(/bin/grep root /etc/shadow | /bin/awk -F : '{ print $2
}')
echo '$HASHPASS'
# facter | grep operatingsystem
operatingsystem = Debian
operatingsystemrelease = 6.0.5
# /bin/grep root /etc/shadow | /bin/awk -F : '{ print $2 }'
bash: /bin/awk: No such file or directory
You're probably fine with not using the full paths there, unless you are
either on a single system type and/or templating getlinuxhash.sh.
'$HASHPASS'
That is likely interpreted as:
' --- a string
$HASHPASS --- substituted
' --- a string
When I run your whole script without the full paths:
# cat /tmp/22
#!/bin/sh
HASHPASS=$(grep root /etc/shadow | awk -F : '{ print $2 }')
echo '$HASHPASS'
# bash /tmp/22
'$6$Fpa0v1.a$2WyfaKkiZS7ALdjtXbU9bASyGcFTxomYSalcryFp5QsKrNJSOmPsG4NNNOZRSZS4S3aRwMD3iza03ORDTxlaq0'
Since the password hash should start with $6$, it looks like you're
returning the quotes too, which is an incorrect password hash.
# cat /tmp/1.pp
file { '/tmp/cw1':
content = generate('/tmp/22')
}
# puppet apply /tmp/1.pp
notice: /Stage[main]//File[/tmp/cw1]/ensure: defined content as
'{md5}3f4302ca8a8c24301c265fdc5345f341'
# cat /tmp/cw1
'$6$Fpa0v1.a$2WyfaKkiZS7ALdjtXbU9BASyGcFTxomYSal4ryFp5AsKrNJSOmPsG4NNNOZRSZh4S3aRwMD3iza03ORDTelaq0'
Possibly try this for your generator? The -n is because I'm not certain if
puppet will keep the trailing newline as part of the hash.
#!/bin/sh
HASHPASS=$(grep root /etc/shadow | awk -F: '{print $2}')
echo -n $HASHPASS
Also, why mine the password rather than provision it from your puppet
manifests better hiera? That way you get more than one root password.
--
You received this message because you are subscribed to the Google
Groups
Puppet Users group.
To view this discussion on the web visit
[1]https://groups.google.com/d/msg/puppet-users/-/Q2wcMCPiKBUJ.
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.
References
Visible links
1. https://groups.google.com/d/msg/puppet-users/-/Q2wcMCPiKBUJ
--
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/-/c8T9SpVwjOcJ.
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.
Re: [Puppet Users] Using generate() to mine a shadow file hash
- Original Message - From: Rob B. rbenc...@gmail.com To: puppet-users@googlegroups.com Sent: Monday, June 25, 2012 2:52:51 PM Subject: Re: [Puppet Users] Using generate() to mine a shadow file hash Hey Christopher, Thanks for the reply. I will give this a try this morning. As for your question about why we want to mine it, we want to change the root password in out password manager software, have that change the root password on the puppet master, and then have puppet distribute the hash everywhere. It makes it easy to keep a single root for all the systems we want it to manage. quite sure this wont work, the puppet master does not run as root and so your generate wont have access to read shadow file. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] Using generate() to mine a shadow file hash
- Original Message - From: R.I.Pienaar r...@devco.net To: puppet-users@googlegroups.com Sent: Monday, June 25, 2012 2:53:45 PM Subject: Re: [Puppet Users] Using generate() to mine a shadow file hash - Original Message - From: Rob B. rbenc...@gmail.com To: puppet-users@googlegroups.com Sent: Monday, June 25, 2012 2:52:51 PM Subject: Re: [Puppet Users] Using generate() to mine a shadow file hash Hey Christopher, Thanks for the reply. I will give this a try this morning. As for your question about why we want to mine it, we want to change the root password in out password manager software, have that change the root password on the puppet master, and then have puppet distribute the hash everywhere. It makes it easy to keep a single root for all the systems we want it to manage. quite sure this wont work, the puppet master does not run as root and so your generate wont have access to read shadow file. you could use sudo of course, but it doesnt seem like a great idea :) -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] OT: Monitoring solutions
If you are thinking abou Nagios, Icinga, or Shinken, may I suggest you look at omdistro.org? They provide a single installable RPM/DEB (e.g. omd-0.54.rpm) which includes all three, plus 10 or so add-ins, all configured to work together, *plus* a nifty management tool that makes it super easy to set up multiple environments. We are using check_mk/multisite (included in OMD) which makes automatic configuration via Puppet a snap. Each node exports 2 or 3 file resources, which are then collected by the correct Nagios server, which in turn kicks off an inventory and rebuilding of the Nagios configuration. It is a thing of beauty. On Mon, Jun 25, 2012 at 6:39 AM, Michael Friedrich michael.friedr...@univie.ac.at wrote: Hi, Original Message Subject: [Puppet Users] OT: Monitoring solutions From: Kyle Sexton k...@mocker.org To: puppet-users@googlegroups.com Date: 2012-06-24 22:45 Icinga: Never used, Nagios fork that I have no opinion on yet developing using it at work, in combination with pnp4nagios for graphing, plus checkmk for inventory and snmp checks. doing it the puppet way (like many users report that the nagios cookbooks still work) is one of my many todos left. so if you got any insights on that topic, feel free to enhance that page :) https://wiki.icinga.org/**display/howtos/Puppethttps://wiki.icinga.org/display/howtos/Puppet kind regards, Michael -- DI (FH) Michael Friedrich Vienna University Computer Center Universitaetsstrasse 7 A-1010 Vienna, Austria email: michael.friedr...@univie.ac.at phone: +43 1 4277 14359 mobile: +43 664 60277 14359 fax:+43 1 4277 14338 web:http://www.univie.ac.at/zid http://www.aco.net Lead Icinga Core Developer http://www.icinga.org -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@** googlegroups.com puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/** group/puppet-users?hl=enhttp://groups.google.com/group/puppet-users?hl=en . -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] Using generate() to mine a shadow file hash
quite sure this wont work, the puppet master does not run as root and
so your generate wont have access to read shadow file.
you could use sudo of course, but it doesnt seem like a great idea :)
Sounds right enough. Though if you're being generous with the hash of
that one root password for each last of your boxen (this strikes me at
not the most secure of concepts), you can go all the way and make it a
custom fact that the agent *on* your puppet master (or any other node
you declare seed for the root password) presents to the puppet master
for redistribution.
Also, some wear leveling of your precios grep binary (either in
generate+sudo or a fact):
awk -F: '$1 == root { print $2 }' /etc/shadow
;-)
(Also, protection from various possible occurences of the string root
in your shadow file.)
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
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.
Re: [Puppet Users] Using generate() to mine a shadow file hash
I suppose I could use a cron to pull out the hash and put it into a file to be read by puppet. On Monday, June 25, 2012 9:54:49 AM UTC-4, R.I. Pienaar wrote: - Original Message - From: R.I.Pienaar r...@devco.net To: puppet-users@googlegroups.com Sent: Monday, June 25, 2012 2:53:45 PM Subject: Re: [Puppet Users] Using generate() to mine a shadow file hash - Original Message - From: Rob B. rbenc...@gmail.com To: puppet-users@googlegroups.com Sent: Monday, June 25, 2012 2:52:51 PM Subject: Re: [Puppet Users] Using generate() to mine a shadow file hash Hey Christopher, Thanks for the reply. I will give this a try this morning. As for your question about why we want to mine it, we want to change the root password in out password manager software, have that change the root password on the puppet master, and then have puppet distribute the hash everywhere. It makes it easy to keep a single root for all the systems we want it to manage. quite sure this wont work, the puppet master does not run as root and so your generate wont have access to read shadow file. you could use sudo of course, but it doesnt seem like a great idea :) -- 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/-/VjsMV8RwvTsJ. 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.
[Puppet Users] Re: Installing hiera
On Monday, June 25, 2012 8:37:30 AM UTC-5, Kelsey Hightower wrote: Did you ever get this working? No, I still do not have this working. Dan - When I did the irb thing, I got true for both requires. Also, I can do lookups successfully on CLI, just not from puppet. -- 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/-/e4Q2atOVbtcJ. 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.
[Puppet Users] Re: Installing hiera
On a related note, I saw a post where someone had a similar problem, but they fixed it by adding/creating some missing default file - but they did not elaborate. Any ideas on what that may be, so I can check it out? -- 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/-/eUxkzp8_4qIJ. 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.
Re: [Puppet Users] Re: Installing hiera
Hi, Have you the hiera Files in the puppet libdir e.g /var/lib/puppet/lib ? Regards Am 25.06.2012 um 17:15 schrieb llow...@oreillyauto.com llow...@oreillyauto.com: On a related note, I saw a post where someone had a similar problem, but they fixed it by adding/creating some missing default file - but they did not elaborate. Any ideas on what that may be, so I can check it out? -- 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/-/eUxkzp8_4qIJ. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] Re: Installing hiera
On Monday, June 25, 2012 10:21:20 AM UTC-5, Florian Koch wrote: Hi, Have you the hiera Files in the puppet libdir e.g /var/lib/puppet/lib ? No, I do not, actually. Which files need to go there? The stuff in /var/lib/gems/1.8/gems/hiera-0.3.0/lib/ ? -- 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/-/Vd1FW3XHlOoJ. 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.
[Puppet Users] Base directory with File
Hi all, I'd like to specify a base_directory and a list of directories (as variables that may be pulled via hiera later) that will be created under that base directory. base_dir = /home/base bars = [a, b, c] bars will be used to create the folders under base and also part of the information going into building a template so I don't want to store them as [$base_dir/a, $base_dir/b, $base_dir/c]. What's the best way to create the bar directories under the base_dir? I'd love to just give File the bars array and specify the base_dir as a property. Should I make a prepend function that would prepend base_dir to each bar and then pass that to File? I tried a definition but then to loop I have to generate a single loop-able structure to call the definition with that contains both bars and base_dir. I looked at create_resources but that seems like it'd force me to make more things variables than I wanted and duplicate more than I would like. Thanks, Mark -- 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/-/WFydQrjUbdQJ. 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.
Re: [Puppet Users] Re: Installing hiera
this is my /var/lib/puppet/lib [root@foreman-proxya01 lib]# tree . ├── hiera │ ├── backend │ │ └── puppet_backend.rb │ └── scope.rb └── puppet └── parser └── functions ├── foreman.rb ├── hiera_array.rb ├── hiera_hash.rb ├── hiera_include.rb └── hiera.rb On Mon, Jun 25, 2012 at 5:34 PM, llow...@oreillyauto.com llow...@oreillyauto.com wrote: On Monday, June 25, 2012 10:21:20 AM UTC-5, Florian Koch wrote: Hi, Have you the hiera Files in the puppet libdir e.g /var/lib/puppet/lib ? No, I do not, actually. Which files need to go there? The stuff in /var/lib/gems/1.8/gems/hiera-0.3.0/lib/ ? -- 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/-/Vd1FW3XHlOoJ. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] Re: Installing hiera
On Mon, Jun 25, 2012 at 10:30 AM, Florian Koch florian.koch1...@googlemail.com wrote: this is my /var/lib/puppet/lib [root@foreman-proxya01 lib]# tree . ├── hiera │ ├── backend │ │ └── puppet_backend.rb │ └── scope.rb └── puppet └── parser └── functions ├── foreman.rb ├── hiera_array.rb ├── hiera_hash.rb ├── hiera_include.rb └── hiera.rb This directory is typically managed by pluginsync, so in most cases do not directly copy files in this directory, but rather make sure you have the right modules on the puppet master. The modules that provide these functions are: http://www.github.com/puppetlabs/hiera-puppet, so make sure you have this module in the puppet master module path, and run puppet agent -t --pluginsync. Thanks, Nan -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
[Puppet Users] Re: Base directory with File
Actually, I think a definition will work.
define file_with_base($base_dir) {
file {$base_dir/$name:
...
}
}
file_with_base($bars:
base_dir = $base_dir
}
I didn't think about the $name coming from an array used when creating the
file_with_base definition. I was only thinking about the parameters
specified in the define, which probably comes from me continuing to think
of it like a function which is wrong.
Regards
Mark
On Monday, June 25, 2012 1:27:40 PM UTC-4, Mark Roggenkamp wrote:
Hi all,
I'd like to specify a base_directory and a list of directories (as
variables that may be pulled via hiera later) that will be created under
that base directory.
base_dir = /home/base
bars = [a, b, c]
bars will be used to create the folders under base and also part of the
information going into building a template so I don't want to store them as
[$base_dir/a, $base_dir/b, $base_dir/c].
What's the best way to create the bar directories under the base_dir? I'd
love to just give File the bars array and specify the base_dir as a
property. Should I make a prepend function that would prepend base_dir to
each bar and then pass that to File?
I tried a definition but then to loop I have to generate a single
loop-able structure to call the definition with that contains both bars and
base_dir. I looked at create_resources but that seems like it'd force me to
make more things variables than I wanted and duplicate more than I would
like.
Thanks,
Mark
--
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/-/cPwQ82qQ594J.
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.
[Puppet Users] facter 1.6.9 patches for aix/powervm detection
greetings folks. wanted to have aix detect if it was under powervm using
facter. came up with this hack for facter 1.6.9 which work for vscsi and
npiv enabled vm's under powervm (so far)...
havent checked the dev facter so something may be in a different branch
already for facter on this topic...
--
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/-/KCDrgcjUoy0J.
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.
--- util/virtual.rb.old 2012-06-07 11:54:11.0 -0400
+++ util/virtual.rb 2012-06-25 14:20:11.0 -0400
@@ -83,4 +83,10 @@
def self.zlinux?
zlinux
end
+
+ def self.powervm?
+#Facter::Util::Resolution.exec(/usr/bin/odmget -q name=`/usr/bin/getconf
BOOT_DEVICE` CuDv | /usr/bin/grep PdDvLn).chomp =~ /vdisk/
+# should work for vscsi and npiv vm's
+Facter::Util::Resolution.exec(/usr/bin/getconf BOOT_DEVICE |
/usr/bin/xargs -n 1 /usr/sbin/lsdev -F parent -l | /usr/bin/xargs -n 1
/usr/sbin/lsdev -F parent -l | /usr/bin/xargs -n 1 /usr/sbin/lsdev -l).chomp
=~ /Virtual/
+ end
end
--- virtual.rb.old 2012-06-25 14:23:42.0 -0400
+++ virtual.rb 2012-06-07 12:00:38.0 -0400
@@ -46,12 +46,16 @@
Facter.add(virtual) do
- confine :kernel = %w{Linux FreeBSD OpenBSD SunOS HP-UX GNU/kFreeBSD}
+ confine :kernel = %w{AIX Linux FreeBSD OpenBSD SunOS HP-UX GNU/kFreeBSD}
result = physical
setcode do
+if Facter.value(:kernel)==AIX and Facter::Util::Virtual.powervm?
+ result = powervm
+end
+
if Facter.value(:kernel) == SunOS and Facter::Util::Virtual.zone?
result = zone
end
[Puppet Users] Spaces in file paths for puppet windows
Hi all, I need to execute the following command, what will be the correct syntax in a windows exec resource? command = C:\Program Files (x86)\RSyslog\Agent\RSyslogConfigClient.exe C:/Program Files (x86)/RSyslog/Agent/customsyslog.xml /f Tanks, Paul. -- 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/-/NG14OmcrhMgJ. 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.
[Puppet Users] Re: Inventory Service on RHEL - uninitalized constant ActiveRecord
Update: I found the problem. My company's RHEL 6 template image had customized/hardened umask settings. When I reverted the umask settings to their default values, everything worked fine. It must have been some sort of permission issues.. -Michael On Monday, June 18, 2012 4:34:37 PM UTC-4, Michael Altfield wrote: Hi, Has anyone had success getting the Inventory Service running in RHEL 6? My Puppet Nodes are getting the following error: [root@puppetnode-01 ~]# puppetd --debug --verbose --no-daemonize ... err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload inventory_active_record: uninitialized constant ActiveRecord ... Here's the gems I have installed: [root@puppetmaster ~]# gem list *** LOCAL GEMS *** activemodel (3.0.11) activerecord (3.0.11) activesupport (3.0.11) arel (2.0.10) builder (2.1.2) daemon_controller (1.0.0) fastthread (1.0.7) i18n (0.5.0) passenger (3.0.13) rack (1.1.0) rake (0.9.2.2, 0.8.7) tzinfo (0.3.33) Any help will be much appreciated! -- 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/-/0LZ7wleESTQJ. 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.
[Puppet Users] Puppet commands require root access
Hi Everyone; Why does running puppet resource require root/sudo access? Is it supposed to be this way or do I have a permissions issue? I installed using the gzip files... Thanks! -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
[Puppet Users] subscribing to a remote mailbox
I think the answer is yes, but is it possible for Puppet to subscribe to an email folder on a remote server? My plan is to perform an action whenever the mailbox receives a new email message. -- 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/-/T_3zIM13sjkJ. 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.
[Puppet Users] Puppet Subscribe Metaparameter
Hello Everyone; I am just learning puppet and playing around. I was testing the 'subscribe' metaparameter and making changes to the live file on the node, specifically, making modifications the /etc/ssh/sshd_config. What I found out was that puppet does not detect changes to the live file, but, if I stage a new copy of the file (with modifications), add it as a source to the resource, then subscribe does restart the service. I just wanted to make sure that my understanding is correct... Also, if my goal is to ensure that the contents of the file are NOT being changed on the target host, how do you reccommend that I accomplish this? Thank you! -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
[Puppet Users] Fwd: possible changes to puppet config file
Hi everyone, We've been doing some work lately to harden the pluginsync functionality for Puppet 3.x. An issue was brought to my attention by Jeff McCune: In current versions of puppet, it's possible to configure things like your vardir and libdir in any section of the config file; potentially, this means that you can specify a different libdir for all three of [main, master, agent]. This causes problems with respect to pluginsync; when you run an agent, it will sync down plugins / modules / faces from the master into the *agent's* libdir. Then, when you try to run a face (even the help face), your libdir will be set to the main libdir, and thus it won't have the content that it needs from the previous agent run. The basic problem here is that all of our various client-side programs *must* share the same libdir. Thus, it seems that we need to restrict the ability to set these for individual client programs. We have a short-term and a long-term solution in mind to resolve this. In the short term, we will simply disallow libdir and related settings from appearing in any sections of puppet.conf other than main and master. (This will still allow the master to have a separate libdir from client-side programs.) The ticket and pull req for this are here: http://projects.puppetlabs.com/issues/15211 https://github.com/puppetlabs/puppet/pull/875 Slightly longer term, we are thinking of simply removing support for run-mode-specific configuration sections in the puppet.conf file. We would only allow three sections: main (possibly renamed to global or similar), master, and ca. (Obviously you could still specify environments in there as well, though we probably should move those to a separate config file in the future.) This is filed as a ticket here: http://projects.puppetlabs.com/issues/15212 Would love to hear any feedback that anyone has on this topic! Thanks Chris -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
[Puppet Users] Value assigned to config.time_zone not recognized
Hi, I'm trying to run Puppet on a RHEL 6 box using apache through passenger. I recently added the Inventory service, but I'm now getting the following error: Value assigned to config.time_zone not recognized.Run rake -D time for a list of tasks for finding appropriate time zone names. I'm not seeing any tell-tell logs from /var/log/httpd/* or /var/log/messages. Any ideas on where the root of this problem is? Thanks, Michael Altfield -- 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/-/JydA_6eKVAwJ. 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.
Re: [Puppet Users] Puppet commands require root access
use sudo command in exec, no problem, but you need to configure sudoers file. 2012/6/25 Worker Bee beeworke...@gmail.com Hi Everyone; Why does running puppet resource require root/sudo access? Is it supposed to be this way or do I have a permissions issue? I installed using the gzip files... Thanks! -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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. -- Douglas Brancaglion Security Analist -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] Puppet commands require root access
Of course giving someone 'sudo puppet' is the same as giving them full root
access. Just be aware of that.
On Monday, June 25, 2012, Douglas Brancaglion wrote:
use sudo command in exec, no problem, but you need to configure sudoers
file.
2012/6/25 Worker Bee beeworke...@gmail.com javascript:_e({}, 'cvml',
'beeworke...@gmail.com');
Hi Everyone;
Why does running puppet resource require root/sudo access? Is it
supposed to be this way or do I have a permissions issue?
I installed using the gzip files...
Thanks!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to
puppet-users@googlegroups.comjavascript:_e({}, 'cvml',
'puppet-users@googlegroups.com');
.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com javascript:_e({}, 'cvml',
'puppet-users%2bunsubscr...@googlegroups.com');.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
Douglas Brancaglion
Security Analist
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to
puppet-users@googlegroups.comjavascript:_e({}, 'cvml',
'puppet-users@googlegroups.com');
.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com javascript:_e({}, 'cvml',
'puppet-users%2bunsubscr...@googlegroups.com');.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
twitter: @procnetdev
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
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.
Re: [Puppet Users] Using generate() to mine a shadow file hash
This would be fairly easy from cron by running 'puppet resource user root some.pp'. It would be even better if your password manager could trigger the command to run only when the password has changed. On Monday, June 25, 2012 10:17:20 AM UTC-4, Rob B. wrote: I suppose I could use a cron to pull out the hash and put it into a file to be read by puppet. -- 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/-/i1EhG8PI6y4J. 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.
Re: [Puppet Users] Using generate() to mine a shadow file hash
Hey John, It doesnt give the password section. Thanks! Rob On Mon, Jun 25, 2012 at 9:16 PM, John Lyman jlym...@gmail.com wrote: This would be fairly easy from cron by running 'puppet resource user root some.pp'. It would be even better if your password manager could trigger the command to run only when the password has changed. On Monday, June 25, 2012 10:17:20 AM UTC-4, Rob B. wrote: I suppose I could use a cron to pull out the hash and put it into a file to be read by puppet. -- 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/-/i1EhG8PI6y4J. 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. 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.
Re: [Puppet Users] Hiera - can't convert Array into String error
On 25/06/2012, at 11:48 PM, Kelsey Hightower wrote:
On Thursday, June 14, 2012 1:51:45 AM UTC-4, Mike wrote:
Thanks,
It appears to be something internal to the hiera function, so I'll have to go
digging in there to find out what's going on.
Cheers
Are you in position to **test** the 1.0rc branches of hiera and hiera-puppet?
Just tried them, unfortunately I got exactly the same error….
err: Could not retrieve catalog from remote server: Error 400 on SERVER: can't
convert Array into String at
--trace on the client (using puppet agent) hasn't given me anything useful.
I can extract the data using on the server using hiera, so it would seem to be
something in the puppet functions. Hopefully I'll be able to spend some time
and look at the functions in a bit more detail soon.
On 14/06/2012, at 1:06 AM, Wolf Noble wrote:
I had some issues with using boolean logic with data being fed to me by
hiera. I went for a slightly hacky option of:
might help you, might be a BadIdea(™)
(untested)
class foo::params{
bool_to_be_tempname = hiera('some_TorF_key_as_a_string')
case bool_to_be_tempname {
[tT][rR][uU][eE]: {
bool_to_be = true
}
default: {
bool_to_be = false
}
}
}
On Jun 13, 2012, at 7:40 AM, Michael Knox wrote:
Hi,
I've been moving from extlookup to hiera, and it's generally gone fairly
smoothly, but I've run into a problem with one of our defines ...
I get this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
can't convert Array into String at ...
The define uses an exec to install Perl CPAN modules and sets log output
based on a hiera lookup.
exec{cpan_load_${title}:
cut …
logoutput = hiera('cpan_logoutput'),
}
If I remove that line, everything runs through fine.
The yaml for hiera:
---
cpan_logoutput: true
Any ideas on what could be triggering this error?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
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.
This message may contain confidential or privileged information. If you are
not the intended recipient, please advise us immediately and delete this
message. See http://www.datapipe.com/legal/email_disclaimer/ for further
information on confidentiality and the risks of non-secure electronic
communication. If you cannot access these links, please notify us by reply
message and we will send the contents to you.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
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.
--
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/-/2GdyZeaN6DoJ.
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.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
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.
