Re: [Puppet Users] Random errors in AIX-Zlinux clients
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. 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 :? Finally I tested compiling a newer version of ruby (ruby-1.8.7-p174 = ruby-1.8.7-p302) and without pthreads (./configure --disable-pthreads) and it seems that it fixes the problem. Now I am not getting Segmentation Faults or random ruby syntax errors on AIX. But I still have the Mysql::Error: MySQL server has gone away error, both on AIX and ZLinux. Somebody opened a new ticket in the traker: http://projects.reductivelabs.com/issues/4694 -- 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.
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] err: Too many open files - /var/lib/puppet/state/state.yaml.tmp
2010/9/3 Héctor Rivas Gándara key...@gmail.com: To workaround the problem you can increase the ulimit for open files (/etc/security/limits.conf) and restart puppetmaster periodically (¿each 6h?). About this solution, I think that I found another bug in puppetmasterd: http://projects.reductivelabs.com/issues/4707 If you change the ulimits probably you should start the daemon using sudo -u puppet initscript. -- 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.
Re: [Puppet Users] [puppet-server] - /var/lib/puppet while installing 0.25.5 puppet-server
On Sep 2, 2010, at 7:46 PM, Patrick wrote: I would assume that the package maintainer moved the default directory location. It's been a while, but I think when I installed the Puppetmaster package (from EPEL), it was set up to use `/etc/puppet/` while the client package uses `/var/lib/puppet/`. I couldn't be completely wrong about that, though. -- Rob McBroom http://www.skurfer.com/ The magnitude of a problem does not affect its ownership. -- 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
On Sep 2, 2010, at 5:47 PM, Kit Stube wrote: changes = [ set ~ /~, set ~/runlevels S, set ~/action wait, set ~/process /sbin/sulogin, ] Try removing the first item in your changes. In many cases, Augeas will create a path for you if you set something that doesn't exist. I have a resource that adds to inittab and it's almost identical to yours, but it only has the last 3 changes. If it still doesn't work, it may be that something doesn't like the ~ character. -- Rob McBroom http://www.skurfer.com/ Before you give the government new power to go after bad guys, remember this: The power will be permanent. The definition of “bad guys ” will not. -- 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
- 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/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. -- 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
On Thu, 02 Sep 2010 23:32:43 +0200
Peter Meier peter.me...@immerda.ch wrote:
-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?
I've done a little bit more digging, and it looks like the variable is
set within a node definition, but not outside it.
site.pp:
$testvar = TESTVAR_VALUE
import nodes
nodes.pp:
notice(testvar outside node is: ${testvar})
node 'test.puppet.cms.ucar.edu' {
notice(testvar inside node is: ${testvar})
}
In my logs, I get:
puppet-master[3757]: (Scope(Class[main])) testvar outside node is:
puppet-master[3757]: (Scope(Node[test.puppet.cms.ucar.edu])) testvar
inside node is: TESTVAR_VALUE
If I then attempt to assign the variable in nodes.pp,
but outside of the node definition, I get an error:
nodes.pp:
$testvar = TESTVAR_SET_IN_NODES
notice(testvar outside node is: ${testvar})
node 'test.puppet.cms.ucar.edu' {
notice(testvar inside node is: ${testvar})
}
Here's the error log entry:
puppet-master[3754]: (Scope(Class[main])) testvar outside node is:
TESTVAR_SET_IN_NODES
puppet-master[3754]: Cannot reassign variable testvar at
/usr/local/puppet/dev/site.pp:18 on node test.puppet.cms.ucar.edu
puppet-master[3754]: Cannot reassign variable testvar at
/usr/local/puppet/dev/site.pp:18 on node test.puppet.cms.ucar.edu
So it looks like there are two different scopes now? In 0.25, I was
setting the variable outside of the node definition; I was using
this to set some path variables. Is this a bug, or was this change
intended?
--
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 So it looks like there are two different scopes now? In 0.25, I was setting the variable outside of the node definition; I was using this to set some path variables. Is this a bug, or was this change intended? Hmm the only difference to how I use such variables is that I have everything within the site.pp, so the variable declaration and the nodes. Can you try if that works? What I could imagine is that imports are now evaluated before variables. But if this is a behavior change between 0.25 and 2.6 you should file a bug report. at least it should be document. pete -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkyBFsAACgkQbwltcAfKi38lzQCgk/xA5/T1StKbFLsfCrpx9BHf 8pMAnjSmhK9dOxS6RtocGx4ZasqRRdvg =PEQ3 -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] Filebucket NameError
I have a backup policy set up on my puppetmaster to back up all files to a /backup directory on each local machine, which it does flawlessly, and have verified even backups run locally work correctly, however when I try to restore I get an uninitialized constant error, to whit: [r...@iron ~]# filebucket backup -b /backup /etc/sudoers /etc/sudoers: 593cc6c8daa910ac404229da56e89b0e [r...@iron ~]# filebucket restore -b /backup /etc/sudoers 593cc6c8daa910ac404229da56e89b0e /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/file_bucket/ dipper.rb:60:in `restore': uninitialized constant Puppet::FileBucket::Dipper::Digest (NameError) from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application/filebucket.rb:46:in `restore' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application/filebucket.rb:18:in `send' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application/filebucket.rb:18:in `run_command' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application.rb:301:in `run' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application.rb:398:in `exit_on_fail' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application.rb:301:in `run' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/bin/filebucket:7 from /usr/bin/filebucket:19:in `load' from /usr/bin/filebucket:19 [r...@iron ~]# -- 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] Filebucket NameError
Richard That looks like a bug to me. Can you please log it - it'll be a simple naming fix. Thanks James Turnbull Richard Knight wrote: I have a backup policy set up on my puppetmaster to back up all files to a /backup directory on each local machine, which it does flawlessly, and have verified even backups run locally work correctly, however when I try to restore I get an uninitialized constant error, to whit: [r...@iron ~]# filebucket backup -b /backup /etc/sudoers /etc/sudoers: 593cc6c8daa910ac404229da56e89b0e [r...@iron ~]# filebucket restore -b /backup /etc/sudoers 593cc6c8daa910ac404229da56e89b0e /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/file_bucket/ dipper.rb:60:in `restore': uninitialized constant Puppet::FileBucket::Dipper::Digest (NameError) from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application/filebucket.rb:46:in `restore' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application/filebucket.rb:18:in `send' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application/filebucket.rb:18:in `run_command' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application.rb:301:in `run' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application.rb:398:in `exit_on_fail' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/lib/puppet/ application.rb:301:in `run' from /usr/lib/ruby/gems/1.8/gems/puppet-2.6.0/bin/filebucket:7 from /usr/bin/filebucket:19:in `load' from /usr/bin/filebucket:19 [r...@iron ~]# -- 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] variable set in site.pp not visible in nodes.pp
On Fri, 03 Sep 2010 17:39:46 +0200 Peter Meier peter.me...@immerda.ch wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So it looks like there are two different scopes now? In 0.25, I was setting the variable outside of the node definition; I was using this to set some path variables. Is this a bug, or was this change intended? Hmm the only difference to how I use such variables is that I have everything within the site.pp, so the variable declaration and the nodes. Can you try if that works? That does indeed work. What I could imagine is that imports are now evaluated before variables. But if this is a behavior change between 0.25 and 2.6 you should file a bug report. at least it should be document. That seems like a pretty major change in behavior to me... global variables are no longer really global? Anyway, I've filed a bug: http://projects.reductivelabs.com/issues/4717 Thanks for your help. -- 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] Re: Using defined(Class[]) on a subclass
This doesn't work. It appears that puppet is looking to see if the value
is defined anywhere at all in the manifest when called this way. Since I
have defined a class server::cobbler it skips over the code even
though the node I'm running it on doesn't have the class defined for it.
John Lyman wrote:
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] Creating tests for the yum package provider
Hi Oliver, Sorry for taking so long to respond on this. We definitely appreciate the help writing some tests for that patch as it looks like something that would definitely help people once it gets merged in. Writing tests for puppet providers can be tricky, as you're finding. I'll take a look and see where you're running into problems. Hopefully I'll have some help for you by the end of Monday. (note: this is a duplicate of the email I sent to puppet-dev, which is definitely more frequently read by developers who can help out with this kind of stuff) Matt On Mon, Aug 16, 2010 at 4:32 AM, Oliver ohook...@gmail.com wrote: Sorry, but this is a blatant call for help. I'm desperately out of my depth with creating tests due to my lack of experience with just about every component involved. The background is, I'm trying to create the necessary tests to have #2866 accepted. I'm running into problems just getting a basic should specify the package version if one is asked for test running. I've looked through the yum provider code, the other providers, tests for other providers etc but can't seem to come up with something that works. I'm quite certain it is mostly due to lack of knowledge but perhaps also is related to the providers working in slightly different ways. Here is what I have so far: - #!/usr/bin/env ruby require File.dirname(__FILE__) + '/../../../spec_helper' provider = Puppet::Type.type(:package).provider(:yum) describe provider do before do # Create a mock resource �...@resource = stub 'resource' # A catch all; no parameters set �...@resource.stubs(:[]).returns nil # We have to set a name, though �...@resource.stubs(:[]).with(:name).returns mypackage �...@resource.stubs(:[]).with(:ensure).returns :installed �...@resource.stubs(:[]).with(:ensure).returns 1.0 �...@provider = provider.new(@resource) �...@provider.stubs(:resource).returns @resource end it should have an install method do �...@provider.should respond_to(:install) end it should be versionable do provider.should be_versionable end it should use erase to purge do �...@provider.expects(:yum).with(-y, :erase, mypackage) �...@provider.purge end describe when installing do it should specify the package version if one is asked for do �...@resource.expects(:name).with(:ensure).returns 1.0 �...@resource.expects(:name) �...@provider.expects(:yum).with(-d, 0, -e, 0, -y, :install, mypackage-1.0) �...@provider.stubs(:yum).returns yum �...@provider.install end end end - My output is as follows: - Puppet::Type::Package::ProviderYum - should have an install method - should be versionable - should use erase to purge Puppet::Type::Package::ProviderYum when installing - should specify the package version if one is asked for (FAILED - 1) 1) Puppet::Error in 'Puppet::Type::Package::ProviderYum when installing should specify the package version if one is asked for' Could not find package ./spec/unit/provider/package/yum.rb:45: /home/ohookins/work/puppet/spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:22:in `run' /home/ohookins/work/puppet/spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in `each' /home/ohookins/work/puppet/spec/monkey_patches/add_confine_and_runnable_to_rspec_dsl.rb:17:in `run' Finished in 0.160654 seconds 4 examples, 1 failure - I guess that I am not pre-setting the correct information in the mocked provider, so that it thinks the relevant package is available to be installed. I previously did not have the @resource.expects(:name) line in the last test, and it complained about an unexpected invocation to Mock#resource.name() which does not make sense to me but then, not much of this does. Some kind soul helped me out last week on the IRC channel and mentioned there may be bugs in the actual provider, but I cannot comment on that. Any input or flames are welcome. Best Regards, Oliver -- 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.
