[Puppet Users] Puppet 2.6.1rc2 eats up a lot of memory
Hi there, This morning I noticed puppet agent, which was running in daemon mode every 5 minutes since August 24th, is using 1.4GB of memory on all hosts. I was not experiencing that kind of memory usage with Puppet 0.24. This is what 'top' reports: 23209 root 20 0 1511m 1.4g 2432 S0 17.9 337:26.04 puppet I know it is difficult to find out what's wrong just with an observation like this, but I'd be glad to provide more details. I'd prefer not to run puppet in cron. Thanks in advance, -- Jean-Baptiste Quenot -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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] Random errors in AIX-Zlinux clients
The errors appear once or two times, randomly, and if I execute the
client again it works properly. They are usually these kind of errors:
You will probably find life improved by deploying
another mode of operation for the puppetmaster daemon, and using a real
database (I use PostgreSQL) for storedconfigs.
You are right, I am using both of them... but I thougth that It could
scale to 20 clients... I will setup mysql+mongrel.
I will tell you if this solves the problem.
I just configured mysql for storeconfigs and Apache+mongrel. ns:
Bad luck, it is still failing with random errors, but more related to
the platform:
On a Suse ZLinux (s390x) installation (and a pair of times on AIX
servers) I get this error related to MySQL: MySQL server has gone
away. It is always with the same query, but with Linux x86 clients it
does not fail :?. I have 1 zLinux, 2 AIX and 5 Linux-x86 clients:
Thu Sep 02 07:49:06 +0200 2010 //zlinux.myhost.com/Puppet (err): Could
not retrieve catalog from remote server: Error 400 on SERVER:
Puppet::Parser::Compiler failed with error
ActiveRecord::StatementInvalid: Mysql::Error: MySQL server has gone
away: SELECT * FROM `hosts` WHERE (`hosts`.`name` =
'zlinux.myhost.com') LIMIT 1 on node zlinux.myhost.com
Thu Sep 02 07:49:06 +0200 2010 //zlinux.myhost.com/Puppet (err):
Cached catalog for zlinux.myhost.com failed: Could not parse YAML data
for catalog zlinux.myhost.com: allocator undefined for Proc Thu Sep 02
07:49:06 +0200 2010 //zlinux.myhost.com/Puppet (err): Could not
retrieve catalog; skipping run
And I still get these random errors on AIX. I think that it might be
caused by a bug in ruby, maybe related to pthreads library :?
Thu Sep 02 07:27:12 +0200 2010 //aix1.myhost.com/Puppet (err): Could
not retrieve catalog from remote server: method `include?' called on
terminated object (0x2002e848) Thu Sep 02 07:27:12 +0200 2010
//aix1.myhost.com/Puppet (err): Cached catalog for aix1.myhost.com
failed: Could not parse YAML data for catalog aix1.myhost.com:
allocator undefined for Proc Thu Sep 02 07:27:12 +0200 2010
//aix1.myhost.com/Puppet (err): Could not retrieve catalog; skipping
run
Thu Sep 02 08:18:16 +0200 2010
//aix2.myhost.com//Stage[main]/Cgx_unixserver::Ad_integration::Aix::Secldapclntd/File[/usr/lib/libibmldap.a]
(err): Could not evaluate: undefined method `inject' for
false:FalseClass
Thu Sep 02 04:57:11 +0200 2010 //aix1.myhost.com/Puppet (err): Could
not retrieve catalog from remote server: undefined method `reference'
for 0:Fixnum Thu Sep 02 04:57:11 +0200 2010 //aix1.myhost.com/Puppet
(err): Could not retrieve catalog; skipping run
Thu Sep 02 02:48:08 +0200 2010 //aix2.myhost.com/Puppet (err): Could
not retrieve catalog from remote server: Could not intern from pson:
expected ',' or ']' in array at '{exported:false,l'!
Thu Sep 02 02:48:08 +0200 2010 //aix2.myhost.com/Puppet (err): Cached
catalog for aix2.myhost.com failed: Could not parse YAML data for
catalog aix2.myhost.com: allocator undefined for Proc Thu Sep 02
02:48:08 +0200 2010 //aix2.myhost.com/Puppet (err): Could not retrieve
catalog; skipping run
Wed Sep 01 20:48:14 +0200 2010 //aix2.myhost.com/Puppet (err): Could
not retrieve catalog from remote server: Could not intern from pson:
Could not convert from pson: Could not find relationship target
Exec[reload-aliases]
Wed Sep 01 20:48:14 +0200 2010 //aix2.myhost.com/Puppet (err): Cached
catalog for aix2.myhost.com failed: Could not parse YAML data for
catalog aix2.myhost.com: allocator undefined for Proc Wed Sep 01
20:48:14 +0200 2010 //aix2.myhost.com/Puppet (err): Could not retrieve
catalog; skipping run
Wed Sep 01 18:27:13 +0200 2010 //aix1.myhost.com/Puppet (err): Could
not save yaml aix1.myhost.com: class or module required
Wed Sep 01 15:48:12 +0200 2010 //aix2.myhost.com/Puppet (err): Got an
uncaught exception of type NoMethodError: undefined method `[]' for
false:FalseClass
Wed Sep 01 15:18:12 +0200 2010 //aix2.myhost.com/Puppet (err): Got an
uncaught exception of type NoMethodError: undefined method `merge' for
false:FalseClass
Wed Sep 01 14:00:22 +0200 2010
//aix1.myhost.com//Stage[main]/Cgx_unixserver::Srv_tree/File[/srv]
(err): Failed to generate additional resources using 'eval_generate':
Invalid parameter 0(0) at
/cgx1/puppet/data/test/modules/stow/manifests/package.pp:61
--
Atentamente
Héctor Rivas
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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 FACTER in other ruby code
Hi all,
I'm trying to write a ruby script to setup MySQL replication base on
facts that we can distribute at runtime.
I have two facts(mysql_master and mysql_repl_dbs) that show up when I
run facter --puppet, however they do not appear to be imported in the
following script:
=
#!/usr/bin/ruby
#
# mysql-replication.rb
#
# This script uses facter to setup mysql replication based upon the
facts mysql_master and mysql_repl_dbs
#
# It is currently in beta
#
# 1) Require the relevant libraries
require 'rubygems'
require 'facter'
require 'mysql'
# 2) Get the relevant facts and echo them to the screen
puts Getting facts
begin
Facter.mysql_master
puts Facts received
rescue
Facter.loadfacts()
puts running rescue
end
mysql_master = Facter.value('mysql_master')
mysql_repl_dbs = Facter.value('mysql_master')
puts Master Server: #{mysql_master}\nDatabases: #{mysql_repl_dbs}
==
The output from the script is as follows:
Getting facts
running rescue
Master Server:
Databases:
where as facter --puppet mysql_master shows the correct hostname.
Am I missing a trick here?
Thanks,
Matt
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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 FACTER in other ruby code
- Matthew Macdonald-Wallace mattmacw...@gmail.com wrote: Hi all, I'm trying to write a ruby script to setup MySQL replication base on facts that we can distribute at runtime. I have two facts(mysql_master and mysql_repl_dbs) that show up when I run facter --puppet, however they do not appear to be imported in the following script: = #!/usr/bin/ruby # # mysql-replication.rb # # This script uses facter to setup mysql replication based upon the facts mysql_master and mysql_repl_dbs # # It is currently in beta # # 1) Require the relevant libraries require 'rubygems' require 'facter' require 'mysql' add around here: ENV['FACTERLIB'] = /var/lib/puppet/lib/facter:/var/lib/puppet/facts substitute with wherever your pluginsync is putting the facts -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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 FACTER in other ruby code
On 2 September 2010 13:52, R.I.Pienaar r...@devco.net wrote: add around here: ENV['FACTERLIB'] = /var/lib/puppet/lib/facter:/var/lib/puppet/facts substitute with wherever your pluginsync is putting the facts Works a treat. (as always!) Thanks for the heads-up. How do I get this into the puppet/facter documentation? Matt -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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 FACTER in other ruby code
- Matthew Macdonald-Wallace mattmacw...@gmail.com wrote: On 2 September 2010 13:52, R.I.Pienaar r...@devco.net wrote: add around here: ENV['FACTERLIB'] = /var/lib/puppet/lib/facter:/var/lib/puppet/facts substitute with wherever your pluginsync is putting the facts Works a treat. (as always!) Thanks for the heads-up. How do I get this into the puppet/facter documentation? not sure where would be appropriate, I just got that from the facter code - looked what it does for --puppet :) -- R.I.Pienaar -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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 file recursion requires two passes to converge
Hi,
So for awhile I have been seeing this issue but it hasn't been painful.
However, recently I have been deploying a new module that has made it much more
annoying.
file { cdh3_config:
recurse = true,
ignore = .svn,
checksum = md5,
notify = Exec[hadoop_alternatives],
require = Package[hadoop],
path = /etc/hadoop-$bespin_cdh3_version/conf.bespin,
source = puppet:///modules/cdh/cdh3/conf.bespin,
}
Then I have 2-3 different hadoop services that subscribe this resource.
So if you make a change in the directory it will correctly refresh the
services. However the next time puppet runs, it will notice there is a mtime
difference on the directory and this will also trigger a refresh.
notice: //cdh::cdh3/File[cdh3_config]/checksum: checksum changed '{mtime}Wed
Sep 01 21:28:46 -0400 2010' to '{mtime}Thu Sep 02 08:53:56 -0400 2010'
This is not good since this forces the services to restart again, which is
really annoying.
We run, puppet 0.25.4.
Thanks,
derek
Derek Yarnell
UNIX Systems Administrator
University of Maryland
Institute for Advanced Computer Studies
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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: nginx+passenger+puppet
Okay, I've researched this a bit more, and it turns out, that the application is not being spun up. Could this have to do with my config paths? I'll attach my puppet.conf at the bottom, but basically, I've installed a puppet-admin user on this system and that's where I edit all of my manifests. I've set up paths in puppet.conf to reflect this. The out takes from the nginx logs point at a missing file (404) $ tail /home/puppet-admin-puppet_config/app/log/access.log 2010/09/02 14:57:04 [error] 29557#0: *5 open() /home/puppet-admin/puppet_config/app/public/production/catalog/servercharlie.bestgroup failed (2: No such file or directory), client: 192.168.1.200, server: servercharlie.bestgroup, request: GET /production/catalog/servercharlie.bestgroup?facts=eNp9VVuTsjoWfZ9fwfgwdc50KeEiKlXz4BXb%252Bx3al64AUSOXYAIi%252FPoJ0O1n%250An%252B%252FMUKUFO8m%252BrLX2Tr1eF%252F5JEzsTiX1FTqyvkihCsa4viIt0fQSdmP1DENAj%250AwhTGmIS6IAMJ1EGnDmRBaupySwdqQ1K0tiQLb0DWAeD7QxggXWCI3hF1LpD6%250AGDVsxOIzJUnE1%252B%252FQTxDTBf4qfMVnWSB8xjjgu2AQ6cLukghbFAlFGFVvFmEK%250A%252FwCUCZQHI0ocxBihDknCWBdqUq2yXzKGHej%252Ftg6qdZbC6EQRzxA0uD%252BvV1o9%250AREPk68IMh8mjtIQoDiDzeMnNZuP7V4VOQnxLEHZ1AbYd4LSBVJpPNzf8f3UL%250Ags%252FsAF5dzGKKfAQZT6LWrNIiESowDs8sYzEKnus8ZqNZ7nC4vzDmvlnJxL%252Bw%250AC4DEi5CbXxsw%252B7xjGieQ11E7QZ%252BhyjWOoOtSjoUuSB25IWnthtSQQVXL88Q3%250AbqU1QAGh%252FDvnGciNTkswKpgKshiOkYupLogJo6JP%252BBnRx7ZY2D9LNqVG%252BwXU%250AZylyQ2vIWl2ua22tbuMzD1Ju41C5KaQ8pFtQgPlyxSRPOGJCHZ1eCflE8QX8%250AHSsuCSDmwPyEPIDOV%252FVfBwHQHaB3Troi6W1V11CFESeTEhJX%252FEaFFD9dmPEM%250AarJawVjYchLyQvrD7e5144UktNjZbHVqP7XJ472HMfL%252F2PwprDh7OAmKV1Xo%250Ar%252FYcDxUY47xSJfIL5f0kjsvlh1Z%252BaaHip5Ixh1X95ieAYXLibZtQxAkaIN8X%250A%252BiSIkhhR%252FkIjUvXxD9gxgzqXtBeStFrAPGPKvRQ9WmBWVZ9FPNYch1jYkRTR%250Aqk4YX7gOSBSLBfF1hESbU%252FDDwErLL6lU39X%252Fc%252BnXJv7yWruLmENxVA2fAbIx%250ADAVjsRfLPq0AEf7wURhmf75I7tkkleReHTpcZNWAKk%252BVSyjkXUDCABVzgnPn%250AJs4TpagciU%252BH%252Fy677oV8HkMVCqVUmBIW%252F834q8YD56U0Vp6kRrPRek6kqtVe%250AJxJ3gKEfJoFdUNlZbKwPMPnZz1%252BK%252Fr2pKxT4qHlGq3Ekan9piP%252FVC38ZRd%252B4%250AV1mxC2XQQ5kudPnTUxY57EuZIw%252FLz%252FeU%252F78Pu9Q8ptO0x8HQuMTez0p03o1w%250AtFvPFuAyXR6OmWdHxDKMJH1bHNn2pnyo3nXmKAdvaXgzsX2l6f7DRL1kcwNm%250AQp3pZnCdtw7dOD1f4%252Fc8wu5wbewvBjHdfO71WbK%252F7M0FsNT%252BeN2SVgxYa1Va%250A99bWsnsL8OGqDMKeMU32kZKq6mY2aMp7z2hrg4fzn%252Bdge6Gm%252FU0Nu7i%252Fl%252Bs5%250Aypx%252F9XvdudfCbROOxi063y%252B8O852B3ze4YDM86GxtA0lWZ1MLxSncmaabrfn%250AO1OZTPOR9Da0OjvHctTjMV%252Be7upyuZyAk6SNrPUpx6oTrG%252FWcXyfoURcd $ cat /etc/puppet/puppet.conf # The configuration file for puppet. Note that this file # is likely to have unused configuration parameters in it; any parameter that's # valid anywhere in Puppet can be in any config file, even if it's not used. # # Every section can specify three special parameters: owner, group, and mode. # These parameters affect the required permissions of any files specified after # their specification. Puppet will sometimes use these parameters to check its # own configured state, so they can be used to make Puppet a bit more self-managing. # # Generated on Fri Jun 11 10:36:05 +0200 2010. # [puppetmasterd] manifest = /home/puppet-admin/puppet_config/manifests/site.pp manifestdir = /home/puppet-admin/puppet_config/manifests modulepath = /home/puppet-admin/puppet_config/modules:/usr/share/puppet/modules templatedir = /home/puppet-admin/puppet_config/templates [puppetd] # The server to which server puppetd should connect # The default value is 'puppet'. # server = puppet server = servercharlie.bestgroup # The shell search path. Defaults to whatever is inherited # from the parent process. # The default value is 'none'. path = /opt/ruby-ee/bin:/opt/ruby-ee/sbin:/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin [puppet] # Whether to use lexical scoping (vs. dynamic). # lexical = false # Whether to validate types during parsing. # The default value is 'true'. # typecheck = true # Where Puppet looks for template files. Can be a list of colon-seperated # directories. # The default value is '$vardir/templates'. templatedir = /var/lib/puppet/templates # Whether to validate parameters during parsing. # The default value is 'true'. # paramcheck = true # Whether to only search for the complete # hostname as it is in the certificate when searching for node information # in the catalogs. # strict_hostname_checking = false # Wether the master should function as a certificate authority. # The default value is 'true'. # ca = true # Where puppetmasterd logs. This is generally not used, # since syslog is the default log destination. # The default value is '$logdir/puppetmaster.log'. masterlog = /var/lib/puppet/log/puppetmaster.log # How the puppetmaster determines the client's identity # and sets the 'hostname', 'fqdn' and 'domain' facts for use in the
Re: [Puppet Users] Using FACTER in other ruby code
On 2 September 2010 14:14, R.I.Pienaar r...@devco.net wrote: not sure where would be appropriate, I just got that from the facter code - looked what it does for --puppet :) Doh! M. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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 2.6.1rc2 eats up a lot of memory
Every 5 minutes? You may not be giving it enough time to garbage collect. Change that to 15 or 30 and see if it makes things better. Trevor On 9/2/10, Jean-Baptiste Quenot j...@caraldi.com wrote: Hi there, This morning I noticed puppet agent, which was running in daemon mode every 5 minutes since August 24th, is using 1.4GB of memory on all hosts. I was not experiencing that kind of memory usage with Puppet 0.24. This is what 'top' reports: 23209 root 20 0 1511m 1.4g 2432 S0 17.9 337:26.04 puppet I know it is difficult to find out what's wrong just with an observation like this, but I'd be glad to provide more details. I'd prefer not to run puppet in cron. Thanks in advance, -- Jean-Baptiste Quenot -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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. -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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] $name uppercased
I'm not sure if this is a bug or an intentional change, but I'm seeing the $name variable in my manifests initial-uppercased in 2.6.1-rc2; 0.25 didn't do this. Since I use this to generate some path variables in my modules, I now have to downcase it with an inline_template, which isn't a major inconvenience but certainly isn't pretty. Should I report this as a bug, or was this an intended change that I missed? -- Dan Urist dur...@ucar.edu 303-497-2459 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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 file recursion requires two passes to converge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So if you make a change in the directory it will correctly refresh
the services. However the next time puppet runs, it will notice
there is a mtime difference on the directory and this will also
trigger a refresh.
notice: //cdh::cdh3/File[cdh3_config]/checksum: checksum changed
'{mtime}Wed Sep 01 21:28:46 -0400 2010' to '{mtime}Thu Sep 02
08:53:56 -0400 2010'
This is not good since this forces the services to restart again,
which is really annoying.
We run, puppet 0.25.4.
This might be a bug. It would be good if you could test if it still
exists on lates 2.6.1rcX an/or file a bug if there isn't yet one.
pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkx/x+gACgkQbwltcAfKi3/GngCgh3gI8ufV4kIdGkp8f10D97BR
wrUAmgOoo1mnU989whu9hDoPSwk9qDk9
=PtFf
-END PGP SIGNATURE-
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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 2.6.1rc2 eats up a lot of memory
Jean-Baptiste Quenot j...@caraldi.com writes: This morning I noticed puppet agent, which was running in daemon mode every 5 minutes since August 24th, is using 1.4GB of memory on all hosts. I was not experiencing that kind of memory usage with Puppet 0.24. This is what 'top' reports: 23209 root 20 0 1511m 1.4g 2432 S0 17.9 337:26.04 puppet I know it is difficult to find out what's wrong just with an observation like this, but I'd be glad to provide more details. I'd prefer not to run puppet in cron. Heh. I *did* get that sort of nasty memory leak with the 0.24 series, and just gave up to using cron, so while I can't help solve it I can say that it isn't unique to the newer version in my experience. Daniel -- ✣ Daniel Pittman✉ dan...@rimspace.net☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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-server] - /var/lib/puppet while installing 0.25.5 puppet-server
just installed puppet-server using yum. but when i ran /etc/init.d/puppetmaster start, file directory /var/lib/ puppet is empty. how come it's empty as compared to installing from source? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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] err: Too many open files - /var/lib/puppet/state/state.yaml.tmp
I keep on getting this message: err: Too many open files - /var/lib/puppet/state/state.yaml.tmp Does anybody know what might be causing it? I'm also getting err: State got corrupted. Everything does seem to be kind of working, but it's sort of worrying getting these new errors. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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 stages in puppet
has anybody else noticed issues with nesting stage classes in 2.6.0?
Using Jeffs eariler post I easily make a stage script do what I need,
the problem is if you import it in site.pp it runs for every node in
the environment, it would seem becuase it is outside any class other
than it's special stage class . Any attempt to move the stageclass
structure inside a parent class to limit its execution seems to result
in script errors; As an example:
site.pp
--
import classes/works.pp
import classes/parent.pp
node my.domain.com {
include parent
}
works.pp
-
stage { pre: before = Stage[main] }
stage { post: require = Stage[main] }
class one { notify { class one, first stage: } }
class two { notify { class two, second stage: } }
class three { notify { class three, third stage: } }
class { one: stage = pre }
class { two: }
class { three: stage = post }
parent.pp
-
class parent {
stage { pre: before = Stage[main] }
stage { post: require = Stage[main] }
class one { notify { class one, first stage: } }
class two { notify { class two, second stage: } }
class three { notify { class three, third stage: } }
class { one: stage = pre }
class { two: }
class { three: stage = post }
}
the works.pp will work but will execute across all nodes regardless of
class structure or includes. parent.pp is one example of various
nesting attempts I have made to prevent staging from arbitrarily
executing the classes its using state on, but ultimatley always ends
up in an error. Through experimentation it seems that the special
stage class requires itself to be outside any other class, the problem
with this is that it will execute on any node in the environment
regardless of how you organize the classes its staging.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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 error Could not find value for 'ipaddress_eth0_0'
I am getting the following error when compiling a template Could not find value for 'ipaddress_eth0_0' but it seems that that fact exists sc...@li96-152:~$ facter | grep ipaddress_eth0_0 ipaddress_eth0_0 = 192.168.141.111 I'm using facter 1.5.7 on Debian Squeeze. What would cause this? I have another node with the same setup where the same template compiles correctly. Thanks, Scott -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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: Puppet hangs
On 2010-09-01 13:44, Fredrik Eriksson wrote: On 26 Aug, 16:22, Brice Figureau brice-pup...@daysofwonder.com wrote: On Thu, 2010-08-26 at 05:08 -0700, kit wrote: This server is 7.2-RELEASE-p4 #0 So it has the fix I sent. debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson This time it was able to ask for 3 files instead of freezing at the 1st one. (gdb) thread apply all Please specify a command following the thread ID list (gdb) bt full My bad, those two commands are in fact only one: thread apply all bt full But the issue is that I'm not sure we can find the issue. It is certainly some locking issues inside ruby that are invalid on FreeBSD. My advice if you really want to get rid of this issue is to rebuild ruby without pthreads. You might also open a ticket on ruby 1.8 bug tracker (or on the FreeBSD ruby port). -- Brice Figureau Follow the latest Puppet Community evolutions onwww.planetpuppet.org! Hello, I think this is the same problem I have seen with my experiments with puppet on freebsd. Puppet randomly hangs after exec-statements. A few examples of where it hangs (ruby18 --debug /usr/local/bin/puppet agent --test --debug --trace) /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: instance variable @virtual not initialized /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: instance variable @virtual not initialized /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: instance variable @virtual not initialized debug: /Stage[main]/Webbase::Backup/Line[sudo_backup]/Exec[echo 'backup ALL= ( root ) NOPASSWD: /usr/sbin/backup' '/usr/local/ etc/sudoers']: Executing check '/usr/bin/grep -qFx 'backup ALL= ( root ) NOPASSWD: /usr/sbin/backup' '/usr/local/etc/sudoers'' debug: Executing '/usr/bin/grep -qFx 'backup ALL= ( root ) NOPASSWD: /usr/sbin/backup' '/usr/local/etc/sudoers'' removing /tmp/puppet20100901-36732-16mgs1p-0...done puppet hangs debug: /Stage[main]/Webbase::Apache/Exec[apache_purge]: Executing check '/bin/test -e /usr/local/etc/apache/ssl.crt' debug: Executing '/bin/test -e /usr/local/etc/apache/ssl.crt' removing /tmp/puppet20100901-50535-1p6j13j-0...done puppet hangs /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: instance variable @virtual not initialized debug: /Stage[main]/Webbase::Nas/Exec[/sbin/mount /proc]: Executing check '/sbin/mount | /usr/bin/egrep ^procfs' debug: Executing '/sbin/mount | /usr/bin/egrep ^procfs' removing /tmp/puppet20100901-95974-1n5jg13-0...done puppet hangs I'm not really familliar with debugging tools (especially not for ruby applications), but I've added a few debug-statements and started a loop that runs puppet to see where it hangs. So far all I know is that it hangs after Puppet::Util::SUIDManager.run_and_capture() but before it returns from run(), I'll see if I can find exact statement where it hangs... Regards -- Fredrik Eriksson I created a bug report over at puppetlabs so that someone who has more knowledge and/or time could take a look at it: http://projects.puppetlabs.com/issues/4681 Regards -- Fredrik Eriksson -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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] err: Could not run Puppet configuration client: Invalid parameter stage at ...
Hi, I am getting the following error on my CentOS clients;
err: Could not run Puppet configuration client: Invalid parameter
stage at /etc/puppet/manifests/nodes.pp:32
The server is CentOS 5.4 with packages from the epel-puppet repos;
# rpm -qa | grep puppet
puppet-dashboard-1.0.3-3
puppet-2.6.1-0.3.rc3.el5
puppet-server-2.6.1-0.3.rc3.el5
The clients are;
# rpm -qa | grep puppet
puppet-0.25.5-1.el5
and my code to bootstrap the puppet install in nodes.pp looks like
this;
node default {
include puppet
if versioncmp($puppetversion, '2.6.0') 0 {
case $operatingsystem {
CentOS: {
notice('In the centos cases')
file { /etc/puppet/puppet.conf:
owner = root,
group = root,
mode = 644,
source =
puppet:///bpcommon/basenode/etc/puppet/puppet-
centos.conf,
**line 32 }
}
debian: {
file { /etc/puppet/puppet.conf:
owner = root,
group = root,
mode = 644,
source =
puppet:///bpcommon/basenode/etc/puppet/
puppet.deb.conf,
}
}
}
}
}
any suggestions what the error is about, I am guessing that the server
is providing a stage parameter which the client is rejecting. but I
was under the impression the server should work with older clients..
Any Suggesions?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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] $name uppercased
Dan Urist wrote: I'm not sure if this is a bug or an intentional change, but I'm seeing the $name variable in my manifests initial-uppercased in 2.6.1-rc2; 0.25 didn't do this. Since I use this to generate some path variables in my modules, I now have to downcase it with an inline_template, which isn't a major inconvenience but certainly isn't pretty. Should I report this as a bug, or was this an intended change that I missed? Dan That's a bug - can you please report. Cheers James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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] err: Too many open files - /var/lib/puppet/state/state.yaml.tmp
Colm O'Connor wrote: I keep on getting this message: err: Too many open files - /var/lib/puppet/state/state.yaml.tmp Does anybody know what might be causing it? I'm also getting err: State got corrupted. Everything does seem to be kind of working, but it's sort of worrying getting these new errors. What version? What platform? Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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] SVN pre-commit hook on wiki
On the wiki page
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Version_Control, the SVN
Pre-Commit Hook script needs to be fixed to not check the syntax on files
getting deleted.
The following line:
$SVNLOOK changed -t $TXN $REPOS | awk '{print $2}' | grep '\.pp$' | while
read line
needs to be:
$SVNLOOK changed -t $TXN $REPOS | grep -v ^D | awk '{print $2}' | grep
'\.pp$' | while read line
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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] SVN pre-commit hook on wiki
On 09/02/2010 02:34 PM, Carl Caum wrote:
On the wiki page
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Version_Control, the SVN
Pre-Commit Hook script needs to be fixed to not check the syntax on files
getting deleted.
The following line:
$SVNLOOK changed -t $TXN $REPOS | awk '{print $2}' | grep '\.pp$' | while
read line
needs to be:
$SVNLOOK changed -t $TXN $REPOS | grep -v ^D | awk '{print $2}' | grep
'\.pp$' | while read line
Sort of moot since the pre-commit was operational in the first place,
there should be no syntax errors in any committed files...
I think there might be a problem or two with that pre-commit in other areas.
--
Joe McDonagh
AIM: YoosingYoonickz
IRC: joe-mac on freenode
When the going gets weird, the weird turn pro.
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-us...@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] SVN pre-commit hook on wiki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/02/2010 08:34 PM, Carl Caum wrote: On the wiki page http://projects.puppetlabs.com/projects/1/wiki/Puppet_Version_Control, the SVN Pre-Commit Hook script needs to be fixed to not check the syntax on files getting deleted. as it is a wiki you can update it yourself! cheers pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkx/8R8ACgkQbwltcAfKi38SEQCdHEwyIysnuRZRnf+VgoZzW5R2 ZCsAoINHI7zrXn3IBYXzqPbQhWJ7eyf7 =D/kR -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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] SVN pre-commit hook on wiki
Huh. I didn't think I had permission to edit that. Turns out I already had a login and everything :P On Sep 2, 2010, at 1:46 PM, Peter Meier wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/02/2010 08:34 PM, Carl Caum wrote: On the wiki page http://projects.puppetlabs.com/projects/1/wiki/Puppet_Version_Control, the SVN Pre-Commit Hook script needs to be fixed to not check the syntax on files getting deleted. as it is a wiki you can update it yourself! cheers pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkx/8R8ACgkQbwltcAfKi38SEQCdHEwyIysnuRZRnf+VgoZzW5R2 ZCsAoINHI7zrXn3IBYXzqPbQhWJ7eyf7 =D/kR -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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-us...@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] variable set in site.pp not visible in nodes.pp
I have another glitch with 2.6.1-rc2 that worked in 0.25-- I set a global variable in my site.pp that is used in my nodes.pp, but it's no longer set there, though it still is in my modules. Is this a bug, or a design change? -- Dan Urist dur...@ucar.edu 303-497-2459 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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 defined(Class[]) on a subclass
I'm having trouble getting puppet to work when using a conditional to
check whether or not a subclass is defined.
Here is what I've tried to do
if ! defined (Class[server::cobbler]) {
# do something
}
With the above statement I get this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Syntax error at 'server::cobbler'; expected ']' at ...
So I tried quoting the class:
if ! defined (Class[server::cobbler]) {
# do something
}
This doesn't error out, but it doesn't do what I'm asking which is to
only run the section of code when the subclass server::cobbler is not
defined.
Any ideas?
--
You received this message because you are subscribed to the Google Groups Puppet
Users group.
To post to this group, send email to puppet-us...@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] variable set in site.pp not visible in nodes.pp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have another glitch with 2.6.1-rc2 that worked in 0.25-- I set a global variable in my site.pp that is used in my nodes.pp, but it's no longer set there, though it still is in my modules. Is this a bug, or a design change? I have a similar setup that works. But do you set it before or after you import nodes.pp? And do you have a minimal setup that reproduces that? cheers pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyAF/sACgkQbwltcAfKi3+2iQCeMjnZYjH45DdXmK0jnpVJ28/m IM0An0XiFPr2B0Yj82EEvRlbDhw+/Ne3 =+Gfw -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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 file recursion requires two passes to converge
Hi Pete,
It does seem fixed in 2.6.1rc3, however 0.25.5 it is still happens. Has there
been a convergence of opinion on how to roll out 2.6.x? Server first then
clients? Clients first then the server? Everything at once? (that is hard
obviously)
Thanks,
derek
On Sep 2, 2010, at 11:51 AM, Peter Meier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So if you make a change in the directory it will correctly refresh
the services. However the next time puppet runs, it will notice
there is a mtime difference on the directory and this will also
trigger a refresh.
notice: //cdh::cdh3/File[cdh3_config]/checksum: checksum changed
'{mtime}Wed Sep 01 21:28:46 -0400 2010' to '{mtime}Thu Sep 02
08:53:56 -0400 2010'
This is not good since this forces the services to restart again,
which is really annoying.
We run, puppet 0.25.4.
This might be a bug. It would be good if you could test if it still
exists on lates 2.6.1rcX an/or file a bug if there isn't yet one.
pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkx/x+gACgkQbwltcAfKi3/GngCgh3gI8ufV4kIdGkp8f10D97BR
wrUAmgOoo1mnU989whu9hDoPSwk9qDk9
=PtFf
-END PGP SIGNATURE-
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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.
Derek Yarnell
UNIX Systems Administrator
University of Maryland
Institute for Advanced Computer Studies
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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 file recursion requires two passes to converge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It does seem fixed in 2.6.1rc3, however 0.25.5 it is still happens. Has there been a convergence of opinion on how to roll out 2.6.x? Server first then clients? Clients first then the server? Everything at once? (that is hard obviously) always update master first. It is also important to note when upgrading that not all versions are backwards compatible. Newer clients may not work with older servers and vice-versa. Where possible backwards-compatibility is maintained but it?s not always totally successful. The best approach is to ensure your master and clients are the same version. When upgrading it is also recommended that you upgrade your master first. http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyAGW4ACgkQbwltcAfKi38jMQCfdBKAE1Iwyoytcb1i5liO5ZGB P7sAn0nwH0duT0RLJXtUUWmOkc0gAjkh =3Ajp -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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] help adding line to /etc/inittab
Hi everyone. I am attempting to add this line to /etc/inittab so that a
user will be forced to enter a password to get into single user mode:
~:S:wait:/sbin/sulogin
I have tried all kinds of things, but seem to be having no luck. Here is
the puppet class I am trying to make:
class gen20 {
# Description: The UNIX host is bootable in single user mode
without a password.
# Insert ~~:S:wait:/sbin/sulogin into /etc/inittab
augeas { inittab :
context = /files/etc/inittab,
changes = [
set ~ /~,
set ~/runlevels S,
set ~/action wait,
set ~/process /sbin/sulogin,
]
}
}
Here is the pertinent debug output from a manual run feeding that code to
puppet:
debug: Augeas[inittab](provider=augeas): Opening augeas with root /, lens
path , flags 0
debug: Augeas[inittab](provider=augeas): Augeas version 0.5.0 is installed
debug: Augeas[inittab](provider=augeas): Will attempt to save and only run
if files changed
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~, /~]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/runlevels, S]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/action, wait]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/process, /sbin/sulogin]
debug: Augeas[inittab](provider=augeas): Files changed, should execute
debug: Augeas[inittab](provider=augeas): Closed the augeas connection
debug: //ia/Augeas[inittab]: Changing returns
debug: //ia/Augeas[inittab]: 1 change(s)
debug: Augeas[inittab](provider=augeas): Opening augeas with root /, lens
path , flags 0
debug: Augeas[inittab](provider=augeas): Augeas version 0.5.0 is installed
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~, /~]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/runlevels, S]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/action, wait]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/process, /sbin/sulogin]
debug: Augeas[inittab](provider=augeas): Closed the augeas connection
err: //ia/Augeas[inittab]/returns: change from need_to_run to 0 failed: Save
failed with return code false
debug: Finishing transaction -612453418 with 1 changes
Can anyone show me the proper way to insert this line into inittab using
augeas and puppet?
Thanks
Kit Stube
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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: err: Could not run Puppet configuration client: Invalid parameter stage at ...
here is the output from a client that was previously working;
# puppetd --test --debug
debug: Creating default schedules
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/
puppet/ssl/certs/cirrusj1626.hpl.hp.com.pem]: Autorequiring File[/var/
lib/puppet/ssl/certs]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/
puppet/ssl]: Autorequiring File[/var/lib/puppet]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/
puppet/ssl/private]: Autorequiring File[/var/lib/puppet/ssl]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/
puppet/ssl/public_keys/cirrusj1626.hpl.hp.com.pem]: Autorequiring
File[/var/lib/puppet/ssl/public_keys]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/
lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/
state]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/etc/
puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/
puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/
puppet/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/
certs]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/
puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/
puppet/ssl/private_keys/cirrusj1626.hpl.hp.com.pem]: Autorequiring
File[/var/lib/puppet/ssl/private_keys]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/
puppet/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/
lib/puppet/classes.txt]: Autorequiring File[/var/lib/puppet]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/lib/
puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/
puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl]
debug: /Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/var/lib/
puppet/ssl/csr_cirrusj1626.hpl.hp.com.pem]: Autorequiring File[/var/
lib/puppet/ssl]
debug: Finishing transaction 70100229842160 with 0 changes
debug: Loaded state in 0.00 seconds
debug: Retrieved facts in 0.30 seconds
debug: Retrieving catalog
debug: Calling puppetmaster.getconfig
debug: Retrieved catalog in 0.35 seconds
debug: Puppet::Network::Client::File: defining fileserver.describe
debug: Puppet::Network::Client::File: defining fileserver.list
debug: Puppet::Network::Client::File: defining fileserver.retrieve
debug: /File[/etc/puppet/puppet.conf]: {:stage=:main}
err: Could not create /etc/puppet/puppet.conf: Class file does not
accept argument(s) stage at /etc/puppet/manifests/nodes.pp:41
warning: Not using cache on failed catalog
warning: Configuration could not be instantiated: Class file does not
accept argument(s) stage at /etc/puppet/manifests/nodes.pp:41
node default {
include puppet
if versioncmp($puppetversion, '2.6.0') 0 {
case $operatingsystem {
redhat: {
file { /etc/puppet/puppet.conf:
owner = root,
group = root,
mode = 644,
source =
puppet:///bpcommon/basenode/etc/puppet/puppet.conf,
}
}
CentOS: {
notice('In the centos cases')
file { /etc/puppet/puppet.conf:
owner = root,
group = root,
mode = 644,
source =
puppet:///bpcommon/basenode/etc/puppet/puppet-
centos.conf,
}
}
debian: {
file { /etc/puppet/puppet.conf:
owner = root,
group = root,
mode = 644,
source =
puppet:///bpcommon/basenode/etc/puppet/
puppet.deb.conf,
}
}
}
}
if versioncmp($puppetversion, '2.6.0') = 0 {
case $operatingsystem {
redhat: {
err('something is pulling
Re: [Puppet Users] Re: err: Could not run Puppet configuration client: Invalid parameter stage at ...
We're taking a look at this and the nested stages issue currently. Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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 defined(Class[]) on a subclass
I believe there is a bug, but I can't find it to reference it now.
Try this:
if ! defined(server::cobler) {
# do something
}
On Sep 2, 5:07 pm, Steven L. Seed slseed1...@gmail.com wrote:
I'm having trouble getting puppet to work when using a conditional to
check whether or not a subclass is defined.
Here is what I've tried to do
if ! defined (Class[server::cobbler]) {
# do something
}
With the above statement I get this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Syntax error at 'server::cobbler'; expected ']' at ...
So I tried quoting the class:
if ! defined (Class[server::cobbler]) {
# do something
}
This doesn't error out, but it doesn't do what I'm asking which is to
only run the section of code when the subclass server::cobbler is not
defined.
Any ideas?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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-server] - /var/lib/puppet while installing 0.25.5 puppet-server
I would assume that the package maintainer moved the default directory location. Try this: puppetmaster --genconfig | grep libdir = On Sep 2, 2010, at 8:37 AM, kid17 wrote: just installed puppet-server using yum. but when i ran /etc/init.d/puppetmaster start, file directory /var/lib/ puppet is empty. how come it's empty as compared to installing from source? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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-us...@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 stages in puppet
Richard -- If I'm understanding you correctly, you've accurately described the behaviour but it isn't really a problem. Stages aren't classes, and they don't do anything unless you put resources in them, so there's no real downside to having them global (which they effectively are). Conversely, it isn't really meaningful to nest them in classes, since they only exist as an organizing system among classes. Think of stages as named time intervals like before breakfast or right after falling asleep or even just after typing the 43rd letter of an e-mail; we all have them (they are global) but only a few of us ever even think about them. Does that help? -- Markus -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@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] help adding line to /etc/inittab
My inittab is slightly different, does this work for you?
class inittab {
define conf (
$id,
$runlevels = '123456',
$action = 'respawn',
$process
) {
augeas {inittab_$id:
context = /files/etc/inittab,
changes = [
set $id/runlevels $runlevels,
set $id/action $action,
set $id/process '$process',
],
}
}
}
and I call that definition as follows:
inittab::conf{supervisor:
id = 'supe',
runlevels = 'a',
action = 'respawn',
process = '/usr/bin/supervisord -n',
# this require is actually evaluated in the inittab::conf
definition
require = [Exec[install
supervisor],Package[python-setuptools]],
}
On Thu, Sep 2, 2010 at 4:47 PM, Kit Stube kst...@gmail.com wrote:
Hi everyone. I am attempting to add this line to /etc/inittab so that a
user will be forced to enter a password to get into single user mode:
~:S:wait:/sbin/sulogin
I have tried all kinds of things, but seem to be having no luck. Here is
the puppet class I am trying to make:
class gen20 {
# Description: The UNIX host is bootable in single user mode
without a password.
# Insert ~~:S:wait:/sbin/sulogin into /etc/inittab
augeas { inittab :
context = /files/etc/inittab,
changes = [
set ~ /~,
set ~/runlevels S,
set ~/action wait,
set ~/process /sbin/sulogin,
]
}
}
Here is the pertinent debug output from a manual run feeding that code to
puppet:
debug: Augeas[inittab](provider=augeas): Opening augeas with root /, lens
path , flags 0
debug: Augeas[inittab](provider=augeas): Augeas version 0.5.0 is installed
debug: Augeas[inittab](provider=augeas): Will attempt to save and only run
if files changed
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~, /~]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/runlevels, S]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/action, wait]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/process, /sbin/sulogin]
debug: Augeas[inittab](provider=augeas): Files changed, should execute
debug: Augeas[inittab](provider=augeas): Closed the augeas connection
debug: //ia/Augeas[inittab]: Changing returns
debug: //ia/Augeas[inittab]: 1 change(s)
debug: Augeas[inittab](provider=augeas): Opening augeas with root /, lens
path , flags 0
debug: Augeas[inittab](provider=augeas): Augeas version 0.5.0 is installed
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~, /~]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/runlevels, S]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/action, wait]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
[/files/etc/inittab/~/process, /sbin/sulogin]
debug: Augeas[inittab](provider=augeas): Closed the augeas connection
err: //ia/Augeas[inittab]/returns: change from need_to_run to 0 failed:
Save failed with return code false
debug: Finishing transaction -612453418 with 1 changes
Can anyone show me the proper way to insert this line into inittab using
augeas and puppet?
Thanks
Kit Stube
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
Jason Koppe
jason.robert.ko...@gmail.com
Cell (210) 445-8242
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@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.
