[Puppet Users] Re: hiera_array() default value not taken
we end up doing this a lot:
$var = hiera_hash('key','SOMESTRING')
if is_hash($var) {
}
not the most elegant
On Friday, April 6, 2012 11:52:58 AM UTC-5, psychobyte wrote:
I don't think hiera likes defaults as array/hashes explicitly
I usually do a
$empty_hsh = {}
$empty_arr = []
and use those as default values.
HTH
On Monday, April 2, 2012 5:03:37 AM UTC-7, pablo.f...@cscs.ch wrote:
Hi,
There is probably something stupid I am missing, but I just can't see
it. I do:
$iptables_open_ports_public = hiera_array ('iptables_open_ports_public',
[])
And I have not defined that in the hiera tree, so the default (an empty
array) should be returned. But I get, instead:
Error 400 on SERVER: Could not find data item
iptables_open_ports_public in any Hiera data file and no default supplied
Is there any special way to define an empty array as a parameter?
Thanks!
Pablo
--
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/-/Ikyx3E7QWogJ.
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: hiera_array() default value not taken
I have this problem too. Do defaults work for anyone?
On Apr 2, 7:03 am, Pablo Fernandez pablo.fernan...@cscs.ch wrote:
Hi,
There is probably something stupid I am missing, but I just can't see
it. I do:
$iptables_open_ports_public = hiera_array ('iptables_open_ports_public', [])
And I have not defined that in the hiera tree, so the default (an empty
array) should be returned. But I get, instead:
Error 400 on SERVER: Could not find data item
iptables_open_ports_public in any Hiera data file and no default supplied
Is there any special way to define an empty array as a parameter?
Thanks!
Pablo
--
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: hiera_array() default value not taken
I'm using the YAML backend. Not sure if that's going to matter.
On Apr 6, 11:07 am, Jason Koppe jason.robert.ko...@gmail.com wrote:
I have this problem too. Do defaults work for anyone?
On Apr 2, 7:03 am, Pablo Fernandez pablo.fernan...@cscs.ch wrote:
Hi,
There is probably something stupid I am missing, but I just can't see
it. I do:
$iptables_open_ports_public = hiera_array ('iptables_open_ports_public', [])
And I have not defined that in the hiera tree, so the default (an empty
array) should be returned. But I get, instead:
Error 400 on SERVER: Could not find data item
iptables_open_ports_public in any Hiera data file and no default supplied
Is there any special way to define an empty array as a parameter?
Thanks!
Pablo
--
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: Adding a parameter to a custom Puppet type/provider
Added to the pastie: http://pastie.org/private/em9dve6walcxyfjyssvya On Feb 11, 10:21 am, Stefan Schulte stefan.schu...@taunusstein.net wrote: Can you provide your resource definition where you use the logical_volume type? -Stefan On Sat, Feb 11, 2012 at 09:31:36AM -0600, Jason Koppe wrote: I do have /var/lib/puppet/lib/puppet/type/logical_volume.rb on my puppet master and I still get the same error. On Wed, Dec 7, 2011 at 6:01 AM, Stefan Schulte stefan.schu...@taunusstein.net wrote: On Tue, Dec 06, 2011 at 10:34:47AM -0800, Jason Koppe wrote: http://pastie.org/private/t9nl5wa91bd6rx1afad7sqis a pastie of my changes tohttps://github.com/puppetlabs/puppet-lvmand the error i'm seeing is err: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter physical_volume at file.pp:26 at node Parameter validation happens on your puppet master so I guess you have to update /var/lib/puppet/lib/puppet/type/logical_volume.rb on your master first. -Stefan -- 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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group athttp://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: Adding a parameter to a custom Puppet type/provider
I do have /var/lib/puppet/lib/puppet/type/logical_volume.rb on my puppet master and I still get the same error. On Wed, Dec 7, 2011 at 6:01 AM, Stefan Schulte stefan.schu...@taunusstein.net wrote: On Tue, Dec 06, 2011 at 10:34:47AM -0800, Jason Koppe wrote: http://pastie.org/private/t9nl5wa91bd6rx1afad7sq is a pastie of my changes to https://github.com/puppetlabs/puppet-lvm and the error i'm seeing is err: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter physical_volume at file.pp:26 at node Parameter validation happens on your puppet master so I guess you have to update /var/lib/puppet/lib/puppet/type/logical_volume.rb on your master first. -Stefan -- 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-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: Adding a parameter to a custom Puppet type/provider
restarting the puppet master didn't help me. On Nov 15, 12:10 am, Gonzalo Servat gser...@gmail.com wrote: ... and I just found this (http://docs.puppetlabs.com/guides/troubleshooting.html): err: Could not retrieve catalog: Invalid parameter ‘foo’ for type ‘bar’ When you are developing new custom types, you should restart both the puppetmasterd and the puppetd before running the configuration using the new custom type. The pluginsync feature will then synchronise the files and the new code will be loaded when both daemons are restarted. Restarted puppetmaster and it's now OK. Caused me many hours of grief!! - Gonzalo On Tue, Nov 15, 2011 at 4:48 PM, Gonzalo Servat gser...@gmail.com wrote: Hi All, I've downloaded a Puppet module and I'm trying to add a parameter to it by editing lib/puppet/type/resource.rb. I simply added: newproperty(:pcfree) do desc My description here end In the corresponding file in lib/puppet/provider, I do something with :pcfree. Whenever I call the resource from Puppet with my new parameter, it keeps saying Invalid parameter pcfree. Do I have to define the new parameter in any other file? Thanks in advance. - Gonzalo -- 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: Adding a parameter to a custom Puppet type/provider
http://pastie.org/private/t9nl5wa91bd6rx1afad7sq is a pastie of my changes to https://github.com/puppetlabs/puppet-lvm and the error i'm seeing is err: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter physical_volume at file.pp:26 at node On Dec 6, 12:22 pm, Jason Koppe jason.robert.ko...@gmail.com wrote: restarting the puppet master didn't help me. On Nov 15, 12:10 am, Gonzalo Servat gser...@gmail.com wrote: ... and I just found this (http://docs.puppetlabs.com/guides/troubleshooting.html): err: Could not retrieve catalog: Invalid parameter ‘foo’ for type ‘bar’ When you are developing new custom types, you should restart both the puppetmasterd and the puppetd before running the configuration using the new custom type. The pluginsync feature will then synchronise the files and the new code will be loaded when both daemons are restarted. Restarted puppetmaster and it's now OK. Caused me many hours of grief!! - Gonzalo On Tue, Nov 15, 2011 at 4:48 PM, Gonzalo Servat gser...@gmail.com wrote: Hi All, I've downloaded a Puppet module and I'm trying to add a parameter to it by editing lib/puppet/type/resource.rb. I simply added: newproperty(:pcfree) do desc My description here end In the corresponding file in lib/puppet/provider, I do something with :pcfree. Whenever I call the resource from Puppet with my new parameter, it keeps saying Invalid parameter pcfree. Do I have to define the new parameter in any other file? Thanks in advance. - Gonzalo -- 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] extlookup not working correctly in 2.7.6
I'm trying to upgrade from 2.6.7 to to 2.7.6 and I'm running into an issue in my extlookup() calls. A lot of the variables which should be defined aren't defined within extlookup.rb. I've tested 2.6.7 agent and 2.7.5 agent against the 2.6.7 master and 2.7.6 master. I adjusted extlookup.rb slightly to provide some debug output. http://pastie.org/private/jsmyxrfhggcvflxcioibq shows: * my 2.7.5 puppet agent failure when run against the 2.7.6 puppet master * git diff of extlookup.rb in the 2.7.6 branch * debug extlookup log output from the 2.7.6 master * debug extlookup log output from the 2.6.7 master * extlookup precedence set in site.pp The same manifests/extlookup configuration work on the newpuppet environment when using a 2.6.7 agent against the 2.6.7 master. -- 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: extlookup not working correctly in 2.7.6
I diff'd the extlookup.rb between 2.6.7 and 2.7.6 and noticed this was
different, so I changed it back and things are working again:
-- git diff ./lib/puppet/parser/functions/extlookup.rb
diff --git a/lib/puppet/parser/functions/extlookup.rb b/lib/puppet/
parser/functions/extlookup.rb
index 5fbf26c..818f7c7 100644
--- a/lib/puppet/parser/functions/extlookup.rb
+++ b/lib/puppet/parser/functions/extlookup.rb
@@ -93,7 +93,7 @@ This is for back compatibility to interpolate
variables with %. % interpolation
extlookup_datadir = undef_as('',lookupvar('::extlookup_datadir'))
- extlookup_precedence =
undef_as([],lookupvar('::extlookup_precedence')).collect { |var|
var.gsub(/%\{(.+?)\}/) { lookupvar(::#{$1}) } }
+ extlookup_precedence =
undef_as([],lookupvar('::extlookup_precedence')).collect { |var|
var.gsub(/%\{(.+?)\}/) { lookupvar($1) } }
datafiles = Array.new
On Oct 24, 6:04 pm, Jason Koppe jason.robert.ko...@gmail.com wrote:
I'm trying to upgrade from 2.6.7 to to 2.7.6 and I'm running into an
issue in my extlookup() calls. A lot of the variables which should be
defined aren't defined within extlookup.rb. I've tested 2.6.7 agent
and 2.7.5 agent against the 2.6.7 master and 2.7.6 master. I adjusted
extlookup.rb slightly to provide some debug output.
http://pastie.org/private/jsmyxrfhggcvflxcioibqshows:
* my 2.7.5 puppet agent failure when run against the 2.7.6 puppet
master
* git diff of extlookup.rb in the 2.7.6 branch
* debug extlookup log output from the 2.7.6 master
* debug extlookup log output from the 2.6.7 master
* extlookup precedence set in site.pp
The same manifests/extlookup configuration work on the newpuppet
environment when using a 2.6.7 agent against the 2.6.7 master.
--
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: extlookup not working correctly in 2.7.6
looks like that's it. i'll use the workaround nigel recommended in that issue (same as my diff above) until that issue is resolved. thanks for the quick response, R.I.! On Oct 24, 6:10 pm, R.I.Pienaar r...@devco.net wrote: - Original Message - I'm trying to upgrade from 2.6.7 to to 2.7.6 and I'm running into an issue in my extlookup() calls. A lot of the variables which should be defined aren't defined within extlookup.rb. I've tested 2.6.7 agent and 2.7.5 agent against the 2.6.7 master and 2.7.6 master. I adjusted extlookup.rb slightly to provide some debug output. http://pastie.org/private/jsmyxrfhggcvflxcioibqshows: * my 2.7.5 puppet agent failure when run against the 2.7.6 puppet master * git diff of extlookup.rb in the 2.7.6 branch * debug extlookup log output from the 2.7.6 master * debug extlookup log output from the 2.6.7 master * extlookup precedence set in site.pp The same manifests/extlookup configuration work on the newpuppet environment when using a 2.6.7 agent against the 2.6.7 master. might be this, not sure. http://projects.puppetlabs.com/issues/9854 -- 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: Puppet 2.7 allows dash in variable names: bug or feature?
We have interpolations like $name-tomcat all over our manifests.
It's possible to adjust them all to ${name}-tomcat but it's not
going to be fun :)
On Oct 6, 1:19 am, Evgeny eokole...@gmail.com wrote:
perhaps you should enclose the variables in quotes to something like
this:
http://${yumserver}/repos/vmware-${esxversion-rhel6-64};
On Oct 5, 8:46 pm, Steve Snodgrass phe...@gmail.com wrote:
While testingpuppet2.7, I found that one of my manifests broke
because of the following quoted string:
http://$yumserver/repos/vmware-$esxversion-rhel6-64;
Everything in the resulting string after vmware- was blank. After
some experiments I found thatpuppet2.7allowsdashes invariable
names, and was interpreting $esxversion-rhel6-64 as one big
variable. Of course adding curly braces fixes the problem, but that
seems like a significant change. Was it intended?
Results of applying a simple test manifest:
notice(Dashtest: $fqdn-is-my-hostname)
Puppet2.6.11:
notice: Scope(Class[main]): Dashtest: foobar.example.com-is-my-
hostname
Puppet2.7.5:
notice: Scope(Class[main]): Dashtest:
-Steve
--
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 2.6.1rc2 does not honor agent's --tags option
Are automatic tags working for others in 2.6? On Wed, Sep 1, 2010 at 6:54 AM, Jason Koppe jason.robert.ko...@gmail.comwrote: Automatic tags don't work for me but explicit tags do since moving to 2.6. On Mon, Aug 30, 2010 at 1:47 PM, Todd Zullinger t...@pobox.com wrote: Jean-Baptiste Quenot wrote: After upgrading Puppet from 0.24.8 to 2.6.1rc2 at my company, I notice that puppet agent's --tags option is not honored anymore: Did you happen to file a ticket for this yet? I need to test more myself, but I believe I saw this the other day too, with rc3. -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgphttp://www.pobox.com/%7Etmz/pgp ~~ Years ago fairy tales all began with Once upon a time..., now we know they all begin with, If I am elected... -- Carolyn Warner -- Jason Koppe jason.robert.ko...@gmail.com Cell (210) 445-8242 -- 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.
Re: [Puppet Users] Puppet 2.6.1rc2 does not honor agent's --tags option
Thanks! On Fri, Sep 3, 2010 at 9:50 AM, Ryan Y. Coleman dudei...@gmail.com wrote: - Original Message - From: Jason Koppe jason.robert.ko...@gmail.com To: puppet-users@googlegroups.com Sent: Friday, September 3, 2010 7:12:34 AM Subject: Re: [Puppet Users] Puppet 2.6.1rc2 does not honor agent's --tags option Are automatic tags working for others in 2.6? No, but see: http://projects.reductivelabs.com/issues/4631 On Wed, Sep 1, 2010 at 6:54 AM, Jason Koppe jason.robert.ko...@gmail.com wrote: Automatic tags don't work for me but explicit tags do since moving to 2.6. On Mon, Aug 30, 2010 at 1:47 PM, Todd Zullinger t...@pobox.com wrote: Jean-Baptiste Quenot wrote: After upgrading Puppet from 0.24.8 to 2.6.1rc2 at my company, I notice that puppet agent's --tags option is not honored anymore: Did you happen to file a ticket for this yet? I need to test more myself, but I believe I saw this the other day too, with rc3. -- Todd OpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgphttp://www.pobox.com/%7Etmz/pgp ~~ Years ago fairy tales all began with Once upon a time..., now we know they all begin with, If I am elected... -- Carolyn Warner -- Jason Koppe jason.robert.ko...@gmail.com Cell (210) 445-8242 -- 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.compuppet-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-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.
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.
Re: [Puppet Users] Puppet 2.6.1rc2 does not honor agent's --tags option
Automatic tags don't work for me but explicit tags do since moving to 2.6. On Mon, Aug 30, 2010 at 1:47 PM, Todd Zullinger t...@pobox.com wrote: Jean-Baptiste Quenot wrote: After upgrading Puppet from 0.24.8 to 2.6.1rc2 at my company, I notice that puppet agent's --tags option is not honored anymore: Did you happen to file a ticket for this yet? I need to test more myself, but I believe I saw this the other day too, with rc3. -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgphttp://www.pobox.com/%7Etmz/pgp ~~ Years ago fairy tales all began with Once upon a time..., now we know they all begin with, If I am elected... -- Carolyn Warner -- 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.
Re: [Puppet Users] Re: custom functions from a module in a different environment
I'm using 2.6.1rc1 (source from github) for the puppetmaster and 0.25.5 (rpm from epel) for my clients and haven't noticed any problems. On Thu, Aug 19, 2010 at 2:55 AM, Darren Worrall iwebdar...@gmail.comwrote: Thanks Dan. Are people using 0.25.x clients with a 2.6 master in the wild ok? I'm open to trying 2.6 on the master(s) but maintaining 2.6 agents would be a bridge too far at this stage. On Aug 18, 5:33 pm, Dan Bode d...@puppetlabs.com wrote: This feature is not supported until 2.6 (and I have seen some issues with 2.6 http://projects.puppetlabs.com/issues/4409) . I would recommend either: 1. trying your use case with 2.6 2. keep a single copy of your plugins in the puppetmaster's modulepath. hope this helps, Dan On Wed, Aug 18, 2010 at 3:38 AM, Darren Worrall iwebdar...@gmail.com wrote: Hey folks, I have just created a puppet environment called testing by adding the following to puppet.conf on the puppetmaster: [testing] manifest = /etc/puppet/testing/manifests/site.pp modulepath = /etc/puppet/testing/modules We are collecting all our customisations into a module, lets say mymodule, and I'm writing a custom function within that, and it lives in /etc/puppet/testing/modules/mymodule/lib/puppet/parser/functions/ myfunc.rb When call that function, on a host in that environment, puppet throws an error ( Error 400 on SERVER: Unknown function myfunc at /etc/puppet/ testing/modules/mymodule/manifests/classes/manifestfile.pp:29 ). If I copy myfunc.rb to the same location in the live module path, it works. So, I'm getting the manifests from the testing environment, but the functions from live :/ The documentation for custom functions says that the search path for them in $modulepath/modulename, and $modulepath is set correctly in puppet.conf (indeed I'm getting the correct manifest files). I imagine I'm missing a config file directive - any pointers? 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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.compuppet-users%2bunsubscr...@googlegroups.com puppet-users%2bunsubscr...@google groups.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.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.
Re: [Puppet Users] Re: Problems with require inside a definition
Thanks, that works as expected.
On Sun, Aug 8, 2010 at 4:58 PM, Peter Meier peter.me...@immerda.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/07/2010 01:31 AM, Jason Koppe wrote:
I ended up getting this syntax to work:
just minor note:
4 $id,
5 $runlevels = '123456',
6 $action = 'respawn',
7 $process
8 ) {
9
10 augeas {inittab_$id:
11 context = /files/etc/inittab,
12 force = true,
13 require = $require,
you don't need to pass the require, the require to the define will
automatically be passed to all it's containing resources.
cheers pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxfKHcACgkQbwltcAfKi3/JcACfeTWMlELe1ZQ7MZeXCUP4LCZe
iLcAn3yLUEvX3JcF4O5WDo8BJscm2TOE
=4yz3
-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.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.
Re: [Puppet Users] Re: Problems with require inside a definition
Yes, that's part of the reason. I was working on my module at an obscene
hour and that probably factors in to my extra require dance.
On Tue, Aug 10, 2010 at 10:39 AM, Nigel Kersten nig...@google.com wrote:
Argh. Everyone is doing this require dance because of the docs on
definitions right?
http://docs.puppetlabs.com/guides/language_tutorial.html#definitions
We had a chat about that on the list a while ago and realized that was
horribly out of date, I'll try to get a patch in to fix it.
On Tue, Aug 10, 2010 at 12:31 AM, Jason Koppe
jason.robert.ko...@gmail.com wrote:
Thanks, that works as expected.
On Sun, Aug 8, 2010 at 4:58 PM, Peter Meier peter.me...@immerda.ch
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/07/2010 01:31 AM, Jason Koppe wrote:
I ended up getting this syntax to work:
just minor note:
4 $id,
5 $runlevels = '123456',
6 $action = 'respawn',
7 $process
8 ) {
9
10 augeas {inittab_$id:
11 context = /files/etc/inittab,
12 force = true,
13 require = $require,
you don't need to pass the require, the require to the define will
automatically be passed to all it's containing resources.
cheers pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxfKHcACgkQbwltcAfKi3/JcACfeTWMlELe1ZQ7MZeXCUP4LCZe
iLcAn3yLUEvX3JcF4O5WDo8BJscm2TOE
=4yz3
-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.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.compuppet-users%2bunsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
nigel
--
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.
[Puppet Users] Wacky environment column in puppet.hosts
I installed puppet 2.6 on my master and increased dbconnections in hopes that it would get me past some 0.25.5 hurdles (one described in http://groups.google.com/group/puppet-users/browse_thread/thread/7ac829c7cb3b2d18/a58f9c8472f2dd8f) -- the upgrade definitely helped because puppetmasterd is updating more in the puppet database without a max connections limit, but I'm seeing some other fun stuff. Below I null out the environment column, show that it's null for a particular host, then run puppetd a few times on the host. mysql for r...@localhost on indadm1 update hosts set environment = NULL; Query OK, 1 row affected (0.01 sec) Rows matched: 99 Changed: 1 Warnings: 0 mysql for r...@localhost on indadm1 select * from hosts where name like 'iad-web2%'; ++-+---+-+-+-+-+-++-+ | id | name| ip| environment | last_compile| last_freshcheck | last_report | updated_at | source_file_id | created_at | ++-+---+-+-+-+-+-++-+ | 9 | iad-web2.indeed.net | 10.24.186.136 | NULL| 2010-08-06 03:31:23 | NULL| NULL| 2010-08-06 03:31:23 | NULL | 2010-06-08 19:47:22 | ++-+---+-+-+-+-+-++-+ 1 row in set (0.00 sec) mysql for r...@localhost on indadm1 select * from hosts where name like 'iad-web2%'; ++-+---++-+-+-+-++-+ | id | name| ip| environment| last_compile| last_freshcheck | last_report | updated_at | source_file_id | created_at | ++-+---++-+-+-+-++-+ | 9 | iad-web2.indeed.net | 10.24.186.136 | --- production | 2010-08-06 03:31:23 | NULL| NULL| 2010-08-06 03:32:42 | NULL | 2010-06-08 19:47:22 | ++-+---++-+-+-+-++-+ 1 row in set (0.00 sec) mysql for r...@localhost on indadm1 select * from hosts where name like 'iad-web2%'; ++-+---+--+-+-+-+-++-+ | id | name| ip| environment | last_compile| last_freshcheck | last_report | updated_at | source_file_id | created_at | ++-+---+--+-+-+-+-++-+ | 9 | iad-web2.indeed.net | 10.24.186.136 | --- --- production | 2010-08-06 03:32:50 | NULL| NULL| 2010-08-06 03:32:50 | NULL | 2010-06-08 19:47:22 | ++-+---+--+-+-+-+-++-+ 1 row in set (0.00 sec) -- 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.
Re: [Puppet Users] Wacky environment column in puppet.hosts
http://projects.puppetlabs.com/issues/4487 On Fri, Aug 6, 2010 at 3:44 AM, James Turnbull ja...@puppetlabs.com wrote: Jason Koppe wrote: I installed puppet 2.6 on my master and increased dbconnections in hopes that it would get me past some 0.25.5 hurdles (one described in http://groups.google.com/group/puppet-users/browse_thread/thread/7ac829c7cb3b2d18/a58f9c8472f2dd8f ) -- the upgrade definitely helped because puppetmasterd is updating more in the puppet database without a max connections limit, but I'm seeing some other fun stuff. Below I null out the environment column, show that it's null for a particular host, then run puppetd a few times on the host. mysql for r...@localhost on indadm1 update hosts set environment = NULL; Query OK, 1 row affected (0.01 sec) Rows matched: 99 Changed: 1 Warnings: 0 Jason That's a bug - can you please log a ticket. Thanks 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.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.
Re: [Puppet Users] Re: Problems with require inside a definition
I'm having similar problems, should it be:
class inittab {
define conf (
$id,
$runlevels = '123456',
$action = 'respawn',
$process
) {
$require {
$require
}
augeas {inittab_$id:
context = /files/etc/inittab,
changes = [
set $id/runlevels $runlevels,
set $id/action $action,
set $id/process $process,
],
}
}
}
With that, I get:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not parse for environment jkoppe: Syntax error at '{'; expected '}' at
/home/jkoppe/svn/production/puppet/modules/inittab/manifests/init.pp:10 on
node indtst5
On Mon, Jul 12, 2010 at 6:48 AM, Tim tkedwa...@fastmail.com.au wrote:
Thanks, that fixed it.
On Jul 9, 5:10 pm, Alan Barrett a...@cequrux.com wrote:
On Fri, 09 Jul 2010, Tim wrote:
# Generic config file
define config-file ($fullpath, $source) {
if $require {
require $require
}
file { $fullpath:
source =
puppet://puppet.hq.eso.org/modules/${source}http://puppet.hq.eso.org/modules/$%7Bsource%7D
,
backup = mainbackup,
mode = 644,
ensure = file,
group = root,
owner = root
}
}
Just delete the if statement and the explicit require statement, and
the right thing should happen. Any require passed to your definition
should propagate to the file resource insuide the definition
automatically.
--apb (Alan Barrett)
--
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.
Re: [Puppet Users] Re: Problems with require inside a definition
If you just mean this:
1 # generic class to allow /etc/inittab management
2 class inittab {
3 define conf (
4 $id,
5 $runlevels = '123456',
6 $action = 'respawn',
7 $process
8 ) {
9 $require
10
11 augeas {inittab_$id:
12 context = /files/etc/inittab,
13 changes = [
14 set $id/runlevels $runlevels,
15 set $id/action $action,
16 set $id/process $process,
17 ],
18 }
19 }
20
21 }
Now, I'm getting this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not parse for environment jkoppe: Syntax error at 'augeas'; expected
'}' at
/home/jkoppe/svn/production/puppet/modules/inittab/manifests/init.pp:11 on
node indtst5
On Fri, Aug 6, 2010 at 6:13 PM, Jason Koppe jason.robert.ko...@gmail.comwrote:
I'm having similar problems, should it be:
class inittab {
define conf (
$id,
$runlevels = '123456',
$action = 'respawn',
$process
) {
$require {
$require
}
augeas {inittab_$id:
context = /files/etc/inittab,
changes = [
set $id/runlevels $runlevels,
set $id/action $action,
set $id/process $process,
],
}
}
}
With that, I get:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not parse for environment jkoppe: Syntax error at '{'; expected '}' at
/home/jkoppe/svn/production/puppet/modules/inittab/manifests/init.pp:10 on
node indtst5
On Mon, Jul 12, 2010 at 6:48 AM, Tim tkedwa...@fastmail.com.au wrote:
Thanks, that fixed it.
On Jul 9, 5:10 pm, Alan Barrett a...@cequrux.com wrote:
On Fri, 09 Jul 2010, Tim wrote:
# Generic config file
define config-file ($fullpath, $source) {
if $require {
require $require
}
file { $fullpath:
source =
puppet://puppet.hq.eso.org/modules/${source}http://puppet.hq.eso.org/modules/$%7Bsource%7D
,
backup = mainbackup,
mode = 644,
ensure = file,
group = root,
owner = root
}
}
Just delete the if statement and the explicit require statement, and
the right thing should happen. Any require passed to your definition
should propagate to the file resource insuide the definition
automatically.
--apb (Alan Barrett)
--
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
--
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.
Re: [Puppet Users] Re: Problems with require inside a definition
I ended up getting this syntax to work:
Here is the class calling the define:
2 class supervisor {
...
13 exec{install supervisor:
...
32
33 # running 'init a' will start supervisord -- should be called at
the end of /etc/init.d/Indeed to start tomcats after slaving/caching
34 inittab::conf{supervisor:
35 id = 'supe',
36 runlevels = 'a',
37 action = 'respawn',
38 process = '/usr/local/bin/supervisord -n',
39 require = Exec[install supervisor],
40 }
Here is the inittab module with the define:
1 # generic class to allow /etc/inittab management
2 class inittab {
3 define conf (
4 $id,
5 $runlevels = '123456',
6 $action = 'respawn',
7 $process
8 ) {
9
10 augeas {inittab_$id:
11 context = /files/etc/inittab,
12 force = true,
13 require = $require,
14 changes = [
15 set $id/runlevels $runlevels,
16 set $id/action $action,
17 set $id/process $process,
18 ],
19 }
20 }
21
22 }
On Fri, Aug 6, 2010 at 6:21 PM, Jason Koppe jason.robert.ko...@gmail.comwrote:
If you just mean this:
1 # generic class to allow /etc/inittab management
2 class inittab {
3 define conf (
4 $id,
5 $runlevels = '123456',
6 $action = 'respawn',
7 $process
8 ) {
9 $require
10
11 augeas {inittab_$id:
12 context = /files/etc/inittab,
13 changes = [
14 set $id/runlevels $runlevels,
15 set $id/action $action,
16 set $id/process $process,
17 ],
18 }
19 }
20
21 }
Now, I'm getting this error:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not parse for environment jkoppe: Syntax error at 'augeas'; expected
'}' at
/home/jkoppe/svn/production/puppet/modules/inittab/manifests/init.pp:11 on
node indtst5
On Fri, Aug 6, 2010 at 6:13 PM, Jason Koppe
jason.robert.ko...@gmail.comwrote:
I'm having similar problems, should it be:
class inittab {
define conf (
$id,
$runlevels = '123456',
$action = 'respawn',
$process
) {
$require {
$require
}
augeas {inittab_$id:
context = /files/etc/inittab,
changes = [
set $id/runlevels $runlevels,
set $id/action $action,
set $id/process $process,
],
}
}
}
With that, I get:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not parse for environment jkoppe: Syntax error at '{'; expected '}' at
/home/jkoppe/svn/production/puppet/modules/inittab/manifests/init.pp:10 on
node indtst5
On Mon, Jul 12, 2010 at 6:48 AM, Tim tkedwa...@fastmail.com.au wrote:
Thanks, that fixed it.
On Jul 9, 5:10 pm, Alan Barrett a...@cequrux.com wrote:
On Fri, 09 Jul 2010, Tim wrote:
# Generic config file
define config-file ($fullpath, $source) {
if $require {
require $require
}
file { $fullpath:
source =
puppet://puppet.hq.eso.org/modules/${source}http://puppet.hq.eso.org/modules/$%7Bsource%7D
,
backup = mainbackup,
mode = 644,
ensure = file,
group = root,
owner = root
}
}
Just delete the if statement and the explicit require statement,
and
the right thing should happen. Any require passed to your definition
should propagate to the file resource insuide the definition
automatically.
--apb (Alan Barrett)
--
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
--
Jason Koppe
jason.robert.ko...@gmail.com
Cell (210) 445-8242
--
Jason Koppe
jason.robert.ko...@gmail.com
Re: [Puppet Users] Storeconfigs connection pool problem
I didn't read anything over last weekend but I'm anxious to find out how to fix this for my environment. What is the OS of your puppetmaster? I've got CentOS and there's another thread about CentOS5 leaking file descriptors which seems to be related. On Mon, Jun 21, 2010 at 10:30 AM, Christopher Johnston chjoh...@gmail.comwrote: Any findings? From what I can tell it defaults to sqlite leaving me with an issue of my hosts bombing out when more then 6 runs are happening. I would prefer to have it use mysql for a cache then let the queuing daemon fwd its data to a central mysql server. On Thu, Jun 10, 2010 at 1:39 PM, Jason Koppe jason.robert.ko...@gmail.com wrote: I'm not sure, I can't seem to find README.queuing or much documentation about how it's supposed to work. I'll checkout the code this weekend if there aren't responses here. On Thu, Jun 10, 2010 at 9:32 AM, Christopher Johnston chjoh...@gmail.com wrote: I have the same issue as well, seems puppetqd uses sqlite for caching? On Wed, Jun 9, 2010 at 4:11 PM, Jason Koppe jason.robert.ko...@gmail.com wrote: Queuing support from ActiveMQ doesn't even make a difference for me -- I thought the purpose of adding the queuing support was to queue the data in puppetqd's memory and let that flush out to the database when it could. I'm still seeing this error from the puppetmaster (not puppetqd). err: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it. Am I misunderstanding how puppetmasterd+puppetqd is supposed to function? On Wed, Jun 9, 2010 at 3:51 AM, Dan Carley dan.car...@gmail.comwrote: On 9 June 2010 06:09, Jason Koppe jason.robert.ko...@gmail.comwrote: On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh joseph.e.mcdon...@gmail.com wrote: Daniel Kerwin wrote: Hi list, i just enabled storeconfigs and cannot use puppetrun on more than 5 hosts. When i try 6+ i get the error message: puppetmasterd[16209]: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it. My Mysql setup allows a lot more connections (500). Any suggestions? Do you have the proper rubygem for mysql installed? I think on deb/ubuntu it's something like libmysql-ruby1.8. I'm having the same problem with the mysql gem installed and the gem appears to be in-use The gem version is a bit of a red herring, so long are using the gem and not Ruby's own connector. As the warning suggests, ActiveRecord's pool option simply needs raising if it's to be put under any strain at all. There is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's configuration. But it's not due to be delivered until 2.6/rowlf. I've been slipstreaming the patch into 0.25 myself because storeconfigs grinds to a halt without it in my environment. Given the simplicity of the diff and that it seems to be affecting a number of people I think it probably warrants being brought forward to 0.25. [0] http://projects.puppetlabs.com/issues/2568 -- 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.compuppet-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-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.compuppet-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
Re: [Puppet Users] Puppetmaster with stored configs leaks file descriptors on CentOS 5
I'm having the same issue on CentOS5.2 with the following packages: *yum* puppet-0.25.5-1.el5 puppet-server-0.25.5-1.el5 rubygems-1.3.1-1.el5 ruby-shadow-1.4.1-7.el5 ruby-devel-1.8.6.111-1 ruby-1.8.6.111-1 ruby-ri-1.8.6.111-1 ruby-docs-1.8.5-5.el5_3.7 ruby-augeas-0.3.0-1.el5 ruby-irb-1.8.6.111-1 ruby-rdoc-1.8.6.111-1 ruby-mode-1.8.5-5.el5_3.7 libselinux-ruby-1.33.4-5.5.el5 ruby-libs-1.8.6.111-1 *gem* activerecord (2.3.8, 2.3.4) activeresource (2.3.8) activesupport (2.3.8, 2.3.4) mysql (2.8.1) rack (1.1.0) rails (2.3.8) Suggestions? On Thu, Apr 29, 2010 at 10:58 AM, Arnaud Gomes-do-Vale arnaud.go...@ircam.fr wrote: Christopher chris...@pricegrabber.com writes: I ran into this same thing. Update (rebuild) to the following rpms versions from fedora 11: rubygem-activerecord.noarch 1:2.3.2-4.fc11 rubygem-activesupport.noarch1:2.3.2-2.fc11 rubygem-rack.noarch 1.0.0-1.fc11 Thanks, this fixed the issue. -- Arnaud -- 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.
Re: [Puppet Users] Storeconfigs connection pool problem
I'm not sure, I can't seem to find README.queuing or much documentation about how it's supposed to work. I'll checkout the code this weekend if there aren't responses here. On Thu, Jun 10, 2010 at 9:32 AM, Christopher Johnston chjoh...@gmail.comwrote: I have the same issue as well, seems puppetqd uses sqlite for caching? On Wed, Jun 9, 2010 at 4:11 PM, Jason Koppe jason.robert.ko...@gmail.comwrote: Queuing support from ActiveMQ doesn't even make a difference for me -- I thought the purpose of adding the queuing support was to queue the data in puppetqd's memory and let that flush out to the database when it could. I'm still seeing this error from the puppetmaster (not puppetqd). err: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it. Am I misunderstanding how puppetmasterd+puppetqd is supposed to function? On Wed, Jun 9, 2010 at 3:51 AM, Dan Carley dan.car...@gmail.com wrote: On 9 June 2010 06:09, Jason Koppe jason.robert.ko...@gmail.com wrote: On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh joseph.e.mcdon...@gmail.com wrote: Daniel Kerwin wrote: Hi list, i just enabled storeconfigs and cannot use puppetrun on more than 5 hosts. When i try 6+ i get the error message: puppetmasterd[16209]: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it. My Mysql setup allows a lot more connections (500). Any suggestions? Do you have the proper rubygem for mysql installed? I think on deb/ubuntu it's something like libmysql-ruby1.8. I'm having the same problem with the mysql gem installed and the gem appears to be in-use The gem version is a bit of a red herring, so long are using the gem and not Ruby's own connector. As the warning suggests, ActiveRecord's pool option simply needs raising if it's to be put under any strain at all. There is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's configuration. But it's not due to be delivered until 2.6/rowlf. I've been slipstreaming the patch into 0.25 myself because storeconfigs grinds to a halt without it in my environment. Given the simplicity of the diff and that it seems to be affecting a number of people I think it probably warrants being brought forward to 0.25. [0] http://projects.puppetlabs.com/issues/2568 -- 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.compuppet-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-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.
Re: [Puppet Users] Storeconfigs connection pool problem
Queuing support from ActiveMQ doesn't even make a difference for me -- I thought the purpose of adding the queuing support was to queue the data in puppetqd's memory and let that flush out to the database when it could. I'm still seeing this error from the puppetmaster (not puppetqd). err: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it. Am I misunderstanding how puppetmasterd+puppetqd is supposed to function? On Wed, Jun 9, 2010 at 3:51 AM, Dan Carley dan.car...@gmail.com wrote: On 9 June 2010 06:09, Jason Koppe jason.robert.ko...@gmail.com wrote: On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh joseph.e.mcdon...@gmail.com wrote: Daniel Kerwin wrote: Hi list, i just enabled storeconfigs and cannot use puppetrun on more than 5 hosts. When i try 6+ i get the error message: puppetmasterd[16209]: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it. My Mysql setup allows a lot more connections (500). Any suggestions? Do you have the proper rubygem for mysql installed? I think on deb/ubuntu it's something like libmysql-ruby1.8. I'm having the same problem with the mysql gem installed and the gem appears to be in-use The gem version is a bit of a red herring, so long are using the gem and not Ruby's own connector. As the warning suggests, ActiveRecord's pool option simply needs raising if it's to be put under any strain at all. There is a bug/feature ticket as #2568 [0] which exposes this option to Puppet's configuration. But it's not due to be delivered until 2.6/rowlf. I've been slipstreaming the patch into 0.25 myself because storeconfigs grinds to a halt without it in my environment. Given the simplicity of the diff and that it seems to be affecting a number of people I think it probably warrants being brought forward to 0.25. [0] http://projects.puppetlabs.com/issues/2568 -- 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.
Re: [Puppet Users] Storeconfigs connection pool problem
I'm having the same problem with the mysql gem installed and the gem appears to be in-use jko...@indadm1 in ~ at 2010-06-08 23:58:59 -- gem list mysql *** LOCAL GEMS *** mysql (2.8.1) jko...@indadm1 in ~ at 2010-06-08 23:59:00 -- cd /var/lib/puppet/log/ jko...@indadm1 in /var/lib/puppet/log at 2010-06-09 00:00:20 -- sudo cat rails.log [sudo] password for jkoppe: # Logfile created on Tue Jun 08 09:04:41 -0500 2010 by logger.rb/1.5.2.9 jko...@indadm1 in /var/lib/puppet/log at 2010-06-09 00:00:25 -- jko...@indadm1 in /var/lib/puppet/log at 2010-06-09 00:08:03 -- sudo lsof | grep 30870 | grep mysql puppetmas 30870 root mem REG8,320837281218568 /usr/lib/libmysqlclient.so.15.0.0 puppetmas 30870 root mem REG8,3 1480351251352 /usr/lib/ruby/gems/1.8/gems/mysql-2.8.1/lib/mysql_api.so puppetmas 30870 root7u IPv4 45902539 TCP indadm1.indeed.net:37895-indadm1.indeed.net:mysql (ESTABLISHED) puppetmas 30870 root9u IPv4 45898759 TCP indadm1.indeed.net:37874-indadm1.indeed.net:mysql (ESTABLISHED) puppetmas 30870 root 11u IPv4 45902499 TCP indadm1.indeed.net:37893-indadm1.indeed.net:mysql (ESTABLISHED) puppetmas 30870 root 19u IPv4 45902527 TCP indadm1.indeed.net:37894-indadm1.indeed.net:mysql (ESTABLISHED) puppetmas 30870 root 22u IPv4 45902542 TCP indadm1.indeed.net:37896-indadm1.indeed.net:mysql (ESTABLISHED) jko...@indadm1 in /var/lib/puppet/log at 2010-06-09 00:08:06 -- On Fri, Feb 12, 2010 at 12:28 AM, Joe McDonagh joseph.e.mcdon...@gmail.comwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Kerwin wrote: Hi list, i just enabled storeconfigs and cannot use puppetrun on more than 5 hosts. When i try 6+ i get the error message: puppetmasterd[16209]: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it. My Mysql setup allows a lot more connections (500). Any suggestions? Thanks, Daniel Do you have the proper rubygem for mysql installed? I think on deb/ubuntu it's something like libmysql-ruby1.8. - -- Joe McDonagh AIM: YoosingYoonickz IRC: joe-mac on freenode L'ennui est contre-révolutionnaire -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkt05xoACgkQRkBieEaRmubRKACglFzvJCGtN1rChmbuZqfJKN7/ yYUAn1/KdvVfD8DURsk+lzc+/VAxb1fG =lPum -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.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.
