Re: [Puppet Users] b64_zlib_yaml errros after server upgrade to
On Tue, Sep 17, 2013 at 1:14 AM, Andrei-Florian Staicu andrei.sta...@gmail.com wrote: Any idea if this is a recognized bug? I don't think it is. Please file a bug report at projects.puppetlabs.comand we can investigate this further. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] b64_zlib_yaml errros after server upgrade to
Do either of you happen to have multiple versions of the puppet installed on the master? One through rubygems and one through yum? I've only been able to reproduce this so far when I accidentally ran a 3.3.0 master that loaded some code from 3.2.4. If not, can you run the master with --trace and --debug flags and track down the stack trace in the master's log? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Disable certain facter facts?
Is it possible to tell facter to ignore certain facts? Couldn't find a config file for it and not sure how puppet tells it to gather facts. There's no configuration right now. I think you have a pretty reasonable case, and you should file a feature request at http://projects.puppetlabs.com/projects/facter. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] undefined method `[]' for nil:NilClass
To diagnose this you'll want to get a full stack trace. Since the error is
on the master you run the master with --trace and then find the stack trace
in the log.
On Tue, Jun 18, 2013 at 11:08 AM, Greg Chavez greg.cha...@gmail.com wrote:
I upgrade our infrastructure (mostly RHEL5, some RHEL6) from 3.1 to
puppet-3.2.1-1.el5. Ruby sits at ruby-1.8.7.370-1.el5. I ran some
tests and everything seemed good so I pushed it out.
Since then, all my puppet clients are failing with this:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: undefined method `[]' for nil:NilClass at
/etc/puppet/modules/site/manifests/init.pp:7 on node
maps-cs-vm-03u.streamsage.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Googling shows that this is a common error that crops up for any
number of reasons. I wonder what my reason is in this case. I use
Cobbler as my ENC, so I have no node statements. Since I'm not using
hiera yet, my site/init.pp looks like this:
class site {
if $::operatingsystem == RedHat {
include puppet
include ypbind
include sudo
if $::ipaddress =~ /^192\.168\./ {
Class[puppet] - Class[ypbind] - Class[sudo]
} else {
include snmp
Class[puppet] - Class[snmp] - Class[ypbind] -
Class[sudo]
}
if $::hostname =~ /[dqcpu]$/ {
include yum
include java
}
# Fixes for mayhem caused by Dell Puppet repos
package {dell-omsa-repository: ensure = absent }
file {/etc/yum.repos.d/dell-omsa-repository.repo: ensure = absent
}
file {/etc/yum.repos.d/puppet-delete-me.repo: ensure = absent}
notify {ENV == ${environment}:}
package { koan:
ensure = latest,
}
# artifact of setting the OOB IP in Cobbler
file { /etc/sysconfig/network-scripts/ifcfg-oob:
ensure = absent;
}
} elsif $::operatingsystem == Ubuntu {
notify {Howdies! I am running Ubuntu!: }
include ntp
include puppet
Class['ntp'] - Class['puppet']
}
}
Line 7 is include sudo. This is a modified version of saz-sudo-2.0.2.
Any ideas? Thanks.
--
\*..+.-
--Greg Chavez
+//..;};
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an
email to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Upgrade from 2.7 to 3.0, problem with run_mode in application.rb
On Fri, Sep 28, 2012 at 2:29 PM, Forrie for...@gmail.com wrote: I'm not at PuppetConf, unfortunately. In this case, all I did was a simple CentOS service puppetmaster restart as I have in the past. But, I wonder if the fact there are older versions still present might contribute to this -- though it shouldn't be reading code from those locations. Definitely. Your stack trace shows puppetmasterd running out of 2.7 but the main puppet code loaded out of 3.0. This is probably because 3.0 no longer ships a puppetmasterd command (it was deprecated in 2.7 in favor of 'puppet master'). Rubygems allows you to have multiple versions installed at the same time, so probably all you need to do is make sure only 3.0 is installed and then make sure your init script calls puppet master instead of puppetmasterd. -Patrick -- 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-lint error
It looks like an incompatibility between puppet-lint and ruby 1.9, which removed the String#each method that was in earlier versions. On Wed, Apr 18, 2012 at 11:30 PM, Joseph cheng...@gmail.com wrote: Hi, this is not strictly puppet related but I am hoping someone here who uses puppet-lint can tell me what is going on here. $ puppet-lint init.pp /Users/jc/.rvm/rubies/ruby-1.9.3-p125/lib/ruby/site_ruby/1.9.1/ rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead. /Users/jc/.rvm/gems/ruby-1.9.3-p125/gems/puppet-lint-0.1.13/bin/puppet- lint:89:in `top (required)': undefined method `each' for service.pp:String (NoMethodError) from /Users/jc/.rvm/gems/ruby-1.9.3-p125/bin/puppet-lint:19:in `load' from /Users/jc/.rvm/gems/ruby-1.9.3-p125/bin/puppet-lint:19:in `main' puppet (2.7.12) puppet-lint (0.1.13) Thx! J. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] agent suddenly disabled
This is a bug in the error message ( http://projects.puppetlabs.com/issues/13299). The correct command is 'puppet agent --enable'. -- 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: Puppet with Ruby1.9 issue
That should be fine as long as you're only running on Ruby 1.9. A fix for this issue went into our 2.7.x branch yesterday [ https://github.com/puppetlabs/puppet/commit/933844567fbe4078cb76f2c089ced1cb6c4170b7]. I'd love to hear if that solves your problems, although I think on 1.9.2 it's functionally equivalent to what you're already doing. On Fri, Dec 16, 2011 at 4:50 AM, linuxbsdfreak linuxbsdfr...@gmail.comwrote: Hi, As i already mentioned on the 1st post. I have edited the file and changed the entries mentioned in the post. I changed /usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/ application/cert.rb Eg: option(--all, -a) do @all = true end to option(--all, -a) do |*_| @all = true end Is the syntax correct or wrong. Regards, Kevin On Dec 15, 8:57 pm, Ken Barber k...@puppetlabs.com wrote: Okay - so its a known issue: http://projects.puppetlabs.com/issues/7428 Looks like there is a workaround there Kevin. Let us know how you go. ken. On Thu, Dec 15, 2011 at 7:40 PM, Ken Barber k...@puppetlabs.com wrote: Dan - Some distro's pinned these kind of directories at 1.9.1. For example in Debian the package is called ruby-1.9.1 even though its version 1.9.2/1.9.3 (depending on release). # ruby1.9.1 --version ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux] # ls /usr/lib/ruby/ 1.8 1.9.1 vendor_ruby Anyhow ... what is interesting, is that I can replicate this on wheezy. # gem1.9.1 install puppet # ruby1.9.1 /usr/local/bin/puppet cert --list /var/lib/gems/1.9.1/gems/facter-1.6.4/lib/facter/util/config.rb:7: Use RbConfig instead of obsolete and deprecated Config. /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead. Could not parse options: wrong number of arguments (1 for 0) And switching back to the packaged version: # /usr/bin/puppet cert --list --all + dashboard (B6:1F:91:F3:70:E4:AD:C5:4C:B8:40:BF:0D:2A:7D:C5) + db1.vms.cloud.bob.sh (C6:B2:F7:3E:9A:DB:F7:75:22:CD:6F:30:55:3E:C5:06) + foremanweb1.vms.cloud.bob.sh(F8:0D:12:BB:F8:D1:3A:AD:A2:73:46:E2:78:85:69:86) + k...@bob.sh (CB:9C:4E:67:41:59:4B:43:39:0C:4B:DD:25:A2:19:D8) + lb1.vms.cloud.bob.sh (73:C7:B3:4D:C9:5A:1D:D6:80:C2:57:96:B5:0A:A9:C1) + mc-server-global (52:63:C0:02:14:83:CD:9D:36:0D:82:3F:E3:19:03:E1) + node1.cloud.bob.sh (4B:12:11:DE:8F:21:71:EA:50:3A:70:97:81:0C:A9:E4) (alt names: DNS:puppet, DNS:node1.cloud.bob.sh, DNS:puppet.cloud.bob.sh) + web1.vms.cloud.bob.sh (68:CC:0A:6F:80:CC:84:DE:3D:37:0A:02:E5:2A:BA:6D) root@node1:~# Odd. I'll dig a bit further. ken. On Thu, Dec 15, 2011 at 7:20 PM, Daniel Pittman dan...@puppetlabs.com wrote: On Thu, Dec 15, 2011 at 02:33, linuxbsdfreak linuxbsdfr...@gmail.com wrote: Hey there. I have a running puppetmaster with nginx and passenger and ruby 1.9.2. I see something odd here - 1.9.2 in the line above, and ... When i do puppet cert --trace --list . i get the following error. /usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application/ cert.rb:43:in `block (2 levels) in class:Cert' ... 1.9.1 here. Which we don't actually support. My guess is you are running with 1.9.1 accidentally, and that is breaking. Daniel -- ⎋ Puppet Labs Developer –http://puppetlabs.com ♲ 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-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. -- 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.
