Re: [Puppet Users] Re: Problem using hiera-eyaml
Hey Werner.
I just added the 'read' permission to the global setting on the installed
gems' directories after the 'gem install' command. I had to do it for
hiera-eyaml and the gems that were installed with it.
Kit.
On Jan 2, 2014 8:39 AM, "Werner Bahlke" wrote:
> Hi Kit,
>
> I am glad you found the cause. Can you tell me a bit more how you resolved
> it? I probably can figure it out eventually but any hints will be greatly
> appreciated.
>
> Thanks,
>
> Werner
>
>
> On Mon, Dec 30, 2013 at 11:17 AM, Kit Plummer wrote:
>
>> Hey Werner. I did resolve my issue. It turned out to be a path issue,
>> with how the PE’s rubygems installs gems. While the eyaml commands were
>> working, the directory for the hiera-eyaml (and it’s dependent gems) didn’t
>> allow the pe-puppet user (global perms) to get to the lib .rb files in the
>> installed gems.
>>
>> It’s a bug and I need to remember to file it.
>>
>> Kit
>>
>>
>> --
>> From: wernerbahlke werner.bah...@gmail.com
>> Reply: puppet-users@googlegroups.com puppet-users@googlegroups.com
>> Date: December 30, 2013 at 9:12:48 AM
>> To: puppet-users@googlegroups.com puppet-users@googlegroups.com
>> Subject: [Puppet Users] Re: Problem using hiera-eyaml
>>
>> >
>> > Hi Kit,
>> >
>> > Thanks for posting. No, I did not resolve it and have put it on the
>> > back
>> > burner. Quite possible that it is a Ruby / gems issue.
>> >
>> > Keep us posted if you resolve it before me.
>> >
>> > Werner
>> >
>> > On Saturday, December 21, 2013 11:13:46 AM UTC-5, Kit Plummer
>> > wrote:
>> > >
>> > > Did you resolve this?
>> > >
>> > > I'm having a similar problem. But, I think it is because the eyaml
>> > > backend isn't getting loaded :) :
>> > >
>> > > "Cannot load backend eyaml: cannot load such file --
>> > > hiera/backend/eyaml_backend"
>> > >
>> > > I'm wondering if this is because the Ruby version/Gems that
>> > are used by PE.
>> > >
>> > > On Friday, December 6, 2013 8:10:35 AM UTC-7, wernerbahlke
>> > wrote:
>> > >>
>> > >> I am trying to use hiera-eyaml and have followed the README
>> > instructions.
>> > >>
>> > >> eyaml seems to work, I can encrypt and decrypt files and passwords.
>> > >>
>> > >> I can also use hiera -c to get at an encrypted value like so:
>> > >>
>> > >> hiera -c /etc/puppetlabs/puppet/hiera.yaml rootpwd
>> > >>
>> > >> But when running this simple test module it fails with cannot
>> > find the
>> > >> data item rootpwd defined in hieradata/defaults.eyaml.
>> > >>
>> > >> class test {
>> > >> $test = hiera('test')
>> > >> $rootpwd = hiera('rootpwd')
>> > >> notify { "Test: ${test}": }
>> > >> }
>> > >> If I just have the test variable defined in defaults.yaml it
>> > works fine.
>> > >> So it cannot find the defaults.eyaml file.
>> > >>
>> > >> Here is my hiera.yaml:
>> > >> --
>> > >>
>> > >> :backends:
>> > >>
>> > >> - yaml
>> > >> - eyaml
>> > >> - :hierarchy:
>> > >> - defaults
>> > >> - "%{clientcert}"
>> > >> - "%{environment}"
>> > >> - global
>> > >> - :yaml: :datadir: /etc/puppetlabs/puppet/modules/hieradata
>> > >> - :eyaml: :datadir: /etc/puppetlabs/puppet/modules/hieradata
>> > >> - :pkcs7_private_key:
>> > >> /etc/puppetlabs/puppet/secure/keys/private_key.pkcs7.pem
>> > >> - :pkcs7_public_key:
>> > >> /etc/puppetlabs/puppet/secure/keys/public_key.pkcs7.pem
>> > >>
>> > >> And my defaults.eyaml file:
>> > >> --
>> > >>
>> > >> rootpwd: >
>> > >>
>> ENC[PKCS7,MIIBeQYJKoZIhvcNAQcDoIIBajCCAWYCAQAxggEhMIIBHQIBADAFMAACAQAwDQYJKoZIhvcNAQE
>> > >> ...]
>> > >> Any hints will be greatly appreciated.
>> > >>
>> > >> I am running Puppet Enterprise 3.1.0 on Ubuntu 12.04.
>> > >>
>> > >
>> >
>> > --
>> > You received this message because you are subscribed to a topic
>> > in the Google Groups "Puppet Users" group.
>> > To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/puppet-users/qpia1_TR2dI/unsubscribe.
>> > To unsubscribe from this group and all its topics, send an email
>> > to puppet-users+unsubscr...@googlegroups.com.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/eed4dd1d-6fc0-4538-b1c5-1621f78ab509%40googlegroups.com
>> .
>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >
>>
>>
>
>
> --
> *Werner Bahlke <http://wernerbahlke.com/> | T: 503-438-9466
> <503-438-9466> | Skype: wernerbahlke*
> <http://www.linkedin.com/in/wernerbahlke>
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAHUyvnpTnWsKH3Wu0rMVJ_ZK9tvKyEJ%3DBhOG6%2BYrzHndxAmLaA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Problem using hiera-eyaml
Hey Werner. I did resolve my issue. It turned out to be a path issue, with
how the PE’s rubygems installs gems. While the eyaml commands were working,
the directory for the hiera-eyaml (and it’s dependent gems) didn’t allow the
pe-puppet user (global perms) to get to the lib .rb files in the installed gems.
It’s a bug and I need to remember to file it.
Kit
--
From: wernerbahlke werner.bah...@gmail.com
Reply: puppet-users@googlegroups.com puppet-users@googlegroups.com
Date: December 30, 2013 at 9:12:48 AM
To: puppet-users@googlegroups.com puppet-users@googlegroups.com
Subject: [Puppet Users] Re: Problem using hiera-eyaml
>
> Hi Kit,
>
> Thanks for posting. No, I did not resolve it and have put it on the
> back
> burner. Quite possible that it is a Ruby / gems issue.
>
> Keep us posted if you resolve it before me.
>
> Werner
>
> On Saturday, December 21, 2013 11:13:46 AM UTC-5, Kit Plummer
> wrote:
> >
> > Did you resolve this?
> >
> > I'm having a similar problem. But, I think it is because the eyaml
> > backend isn't getting loaded :) :
> >
> > "Cannot load backend eyaml: cannot load such file --
> > hiera/backend/eyaml_backend"
> >
> > I'm wondering if this is because the Ruby version/Gems that
> are used by PE.
> >
> > On Friday, December 6, 2013 8:10:35 AM UTC-7, wernerbahlke
> wrote:
> >>
> >> I am trying to use hiera-eyaml and have followed the README
> instructions.
> >>
> >> eyaml seems to work, I can encrypt and decrypt files and passwords.
> >>
> >> I can also use hiera -c to get at an encrypted value like so:
> >>
> >> hiera -c /etc/puppetlabs/puppet/hiera.yaml rootpwd
> >>
> >> But when running this simple test module it fails with cannot
> find the
> >> data item rootpwd defined in hieradata/defaults.eyaml.
> >>
> >> class test {
> >> $test = hiera('test')
> >> $rootpwd = hiera('rootpwd')
> >> notify { "Test: ${test}": }
> >> }
> >> If I just have the test variable defined in defaults.yaml it
> works fine.
> >> So it cannot find the defaults.eyaml file.
> >>
> >> Here is my hiera.yaml:
> >> --
> >>
> >> :backends:
> >>
> >> - yaml
> >> - eyaml
> >> - :hierarchy:
> >> - defaults
> >> - "%{clientcert}"
> >> - "%{environment}"
> >> - global
> >> - :yaml: :datadir: /etc/puppetlabs/puppet/modules/hieradata
> >> - :eyaml: :datadir: /etc/puppetlabs/puppet/modules/hieradata
> >> - :pkcs7_private_key:
> >> /etc/puppetlabs/puppet/secure/keys/private_key.pkcs7.pem
> >> - :pkcs7_public_key:
> >> /etc/puppetlabs/puppet/secure/keys/public_key.pkcs7.pem
> >>
> >> And my defaults.eyaml file:
> >> --
> >>
> >> rootpwd: >
> >> ENC[PKCS7,MIIBeQYJKoZIhvcNAQcDoIIBajCCAWYCAQAxggEhMIIBHQIBADAFMAACAQAwDQYJKoZIhvcNAQE
> >>
> >> ...]
> >> Any hints will be greatly appreciated.
> >>
> >> I am running Puppet Enterprise 3.1.0 on Ubuntu 12.04.
> >>
> >
>
> --
> You received this message because you are subscribed to a topic
> in the Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/qpia1_TR2dI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email
> to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/eed4dd1d-6fc0-4538-b1c5-1621f78ab509%40googlegroups.com.
>
> 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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/etPan.52c19c95.19495cff.e175%409route.local.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Problem using hiera-eyaml
Did you resolve this?
I'm having a similar problem. But, I think it is because the eyaml backend
isn't getting loaded :) :
"Cannot load backend eyaml: cannot load such file --
hiera/backend/eyaml_backend"
I'm wondering if this is because the Ruby version/Gems that are used by PE.
On Friday, December 6, 2013 8:10:35 AM UTC-7, wernerbahlke wrote:
>
> I am trying to use hiera-eyaml and have followed the README instructions.
>
> eyaml seems to work, I can encrypt and decrypt files and passwords.
>
> I can also use hiera -c to get at an encrypted value like so:
>
> hiera -c /etc/puppetlabs/puppet/hiera.yaml rootpwd
>
> But when running this simple test module it fails with cannot find the
> data item rootpwd defined in hieradata/defaults.eyaml.
>
> class test {
> $test = hiera('test')
> $rootpwd = hiera('rootpwd')
> notify { "Test: ${test}": }
> }
> If I just have the test variable defined in defaults.yaml it works fine.
> So it cannot find the defaults.eyaml file.
>
> Here is my hiera.yaml:
> --
>
> :backends:
>
>- yaml
>- eyaml
>- :hierarchy:
> - defaults
> - "%{clientcert}"
> - "%{environment}"
> - global
> - :yaml: :datadir: /etc/puppetlabs/puppet/modules/hieradata
> - :eyaml: :datadir: /etc/puppetlabs/puppet/modules/hieradata
> -:pkcs7_private_key:
> /etc/puppetlabs/puppet/secure/keys/private_key.pkcs7.pem
> -:pkcs7_public_key:
> /etc/puppetlabs/puppet/secure/keys/public_key.pkcs7.pem
>
> And my defaults.eyaml file:
> --
>
> rootpwd: >
> ENC[PKCS7,MIIBeQYJKoZIhvcNAQcDoIIBajCCAWYCAQAxggEhMIIBHQIBADAFMAACAQAwDQYJKoZIhvcNAQE
>
> ...]
> Any hints will be greatly appreciated.
>
> I am running Puppet Enterprise 3.1.0 on Ubuntu 12.04.
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/7728bda5-6074-499b-90e0-e522f2715bcb%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Facter on a VM...
Hey. Just getting back to this issue. It happens on just about every OS, or VM enviro. I'm currently testing on MacOSX, but have also seen it on various Linux distros, most recently CentOS-6. I can reproduce it in AWS, VMware, and Virtualbox, but only from my app. It never happens if in IRB, or just a simple script. The output is hitting stderr. Any ideas? On Aug 22, 10:06 am, Brian Troutwine wrote: > Kit, > > What puppet/facter versions, which OS and what VM? Also, what is the content > of your fstab? > > On Mon, Aug 22, 2011 at 12:59 PM, Kit Plummer wrote: > > > > > > > > > > > Am I the only one seeing this? Permissions, or OS thing? > > > On Aug 18, 8:14 pm, Kit Plummer wrote: > > > Hey. > > > > I'm using Facter to publish VM capabilities - and every time I get the > > > facts I get a couple of errors along with: > > > > Could not retrieve network_lo: wrong number of arguments (1 for 0) > > > Could not retrieve network_lo: wrong number of arguments (1 for 0) > > > Could not retrieve network_eth0: wrong number of arguments (1 for 0) > > > Could not retrieve network_eth0: wrong number of arguments (1 for 0) > > > > Any ideas? Is there something I can filter? > > > > TIA, > > > Kit > > > -- > > 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. > > -- > Brian L. Troutwine -- 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: Facter on a VM...
Am I the only one seeing this? Permissions, or OS thing? On Aug 18, 8:14 pm, Kit Plummer wrote: > Hey. > > I'm using Facter to publish VM capabilities - and every time I get the > facts I get a couple of errors along with: > > Could not retrieve network_lo: wrong number of arguments (1 for 0) > Could not retrieve network_lo: wrong number of arguments (1 for 0) > Could not retrieve network_eth0: wrong number of arguments (1 for 0) > Could not retrieve network_eth0: wrong number of arguments (1 for 0) > > Any ideas? Is there something I can filter? > > TIA, > Kit -- 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] Facter on a VM...
Hey. I'm using Facter to publish VM capabilities - and every time I get the facts I get a couple of errors along with: Could not retrieve network_lo: wrong number of arguments (1 for 0) Could not retrieve network_lo: wrong number of arguments (1 for 0) Could not retrieve network_eth0: wrong number of arguments (1 for 0) Could not retrieve network_eth0: wrong number of arguments (1 for 0) Any ideas? Is there something I can filter? TIA, Kit -- 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 hangs
Fixed by updating to ruby-1.8.7.302 On 27 Okt, 15:35, Nigel Kersten wrote: > On Wed, Oct 27, 2010 at 1:34 AM, kit wrote: > > Thanks Fredrik for submitting the bug report. > > > Hopefully it will be looked at soon. I like puppet, > > however when it keeps hanging it's next to unusable. > > > Doesn't look like anything's happened over at puppet > > yet though, and it's been two months already. > > You mean this one? I feel the log does a decent job of capturing the current > state, and that is a great bug report Fredrik. > > http://projects.puppetlabs.com/issues/4681 > > Is anyone on FreeBSD 8 *not* seeing this issue? kit, it would be helpful if > you appended to the bug if you're seeing the same issue with a newer puppet > version than 2.6.1r2 as well. > > > > > > > > > > > Regards > > Erik > > > On 1 Sep, 20:21, Fredrik Eriksson wrote: > > > On 2010-09-01 13:44, Fredrik Eriksson wrote: > > > > > On 26 Aug, 16:22, Brice Figureau > > > > wrote: > > > >> On Thu, 2010-08-26 at 05:08 -0700, kit wrote: > > > >>> This server is 7.2-RELEASE-p4 #0 > > > > >> So it has the fix I sent. > > > > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > > > >>> yaml; using pson > > > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > > > >>> yaml; using pson > > > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > > > >>> yaml; using pson > > > > >> This time it was able to ask for 3 files instead of freezing at the > > 1st > > > >> one. > > > > >>> (gdb) thread apply all > > > >>> Please specify a command following the thread ID list > > > >>> (gdb) bt full > > > > >> My bad, those two commands are in fact only one: > > > > >> thread apply all bt full > > > > >> But the issue is that I'm not sure we can find the issue. It is > > > >> certainly some locking issues inside ruby that are invalid onFreeBSD. > > > > >> My advice if you really want to get rid of this issue is to rebuild > > ruby > > > >> without pthreads. > > > > >> You might also open a ticket on ruby 1.8 bug tracker (or on theFreeBSD > > > >> ruby port). > > > >> -- > > > >> Brice Figureau > > > >> Follow the latest Puppet Community evolutions onwww.planetpuppet.org! > > > > > Hello, > > > > > I think this is the same problem I have seen with my experiments with > > > > puppet onfreebsd. Puppet randomly hangs after exec-statements. A few > > > > examples of where it hangs (ruby18 --debug /usr/local/bin/puppet agent > > > > --test --debug --trace) > > > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > > > instance variable @virtual not initialized > > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > > > instance variable @virtual not initialized > > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > > > instance variable @virtual not initialized > > > > debug: /Stage[main]/Webbase::Backup/Line[sudo_backup]/Exec[echo > > > > 'backup ALL= ( root ) NOPASSWD: /usr/sbin/backup' >> '/usr/local/ > > > > etc/sudoers']: Executing check '/usr/bin/grep -qFx 'backup ALL= > > > > ( root ) NOPASSWD: /usr/sbin/backup' '/usr/local/etc/sudoers'' > > > > debug: Executing '/usr/bin/grep -qFx 'backup ALL= ( root ) > > > > NOPASSWD: /usr/sbin/backup' '/usr/local/etc/sudoers'' > > > > removing /tmp/puppet20100901-36732-16mgs1p-0...done > > > > > > > > > debug: /Stage[main]/Webbase::Apache/Exec[apache_purge]: Executing > > > > check '/bin/test -e /usr/local/etc/apache/ssl.crt' > > > > debug: Executing '/bin/test -e /usr/local/etc/apache/ssl.crt' > > > > removing /tmp/puppet20100901-50535-1p6j13j-0...done > > > > > > > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > > > instance variable @virtual not initialized > > > > debug: /Stage[main]/Webbase::Nas/Exec[/sbin/mount /proc]: Executing > > > > check '/sbin/mount | /usr/bin/egrep ^proc
[Puppet Users] Re: Puppet hangs
Thanks Fredrik for submitting the bug report. Hopefully it will be looked at soon. I like puppet, however when it keeps hanging it's next to unusable. Doesn't look like anything's happened over at puppet yet though, and it's been two months already. Regards Erik On 1 Sep, 20:21, Fredrik Eriksson wrote: > On 2010-09-01 13:44, Fredrik Eriksson wrote: > > > > > > > On 26 Aug, 16:22, Brice Figureau > > wrote: > >> On Thu, 2010-08-26 at 05:08 -0700, kit wrote: > >>> This server is 7.2-RELEASE-p4 #0 > > >> So it has the fix I sent. > > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > >>> yaml; using pson > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > >>> yaml; using pson > >>> debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > >>> yaml; using pson > > >> This time it was able to ask for 3 files instead of freezing at the 1st > >> one. > > >>> (gdb) thread apply all > >>> Please specify a command following the thread ID list > >>> (gdb) bt full > > >> My bad, those two commands are in fact only one: > > >> thread apply all bt full > > >> But the issue is that I'm not sure we can find the issue. It is > >> certainly some locking issues inside ruby that are invalid onFreeBSD. > > >> My advice if you really want to get rid of this issue is to rebuild ruby > >> without pthreads. > > >> You might also open a ticket on ruby 1.8 bug tracker (or on theFreeBSD > >> ruby port). > >> -- > >> Brice Figureau > >> Follow the latest Puppet Community evolutions onwww.planetpuppet.org! > > > Hello, > > > I think this is the same problem I have seen with my experiments with > > puppet onfreebsd. Puppet randomly hangs after exec-statements. A few > > examples of where it hangs (ruby18 --debug /usr/local/bin/puppet agent > > --test --debug --trace) > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > instance variable @virtual not initialized > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > instance variable @virtual not initialized > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > instance variable @virtual not initialized > > debug: /Stage[main]/Webbase::Backup/Line[sudo_backup]/Exec[echo > > 'backup ALL= ( root ) NOPASSWD: /usr/sbin/backup' >> '/usr/local/ > > etc/sudoers']: Executing check '/usr/bin/grep -qFx 'backup ALL= > > ( root ) NOPASSWD: /usr/sbin/backup' '/usr/local/etc/sudoers'' > > debug: Executing '/usr/bin/grep -qFx 'backup ALL= ( root ) > > NOPASSWD: /usr/sbin/backup' '/usr/local/etc/sudoers'' > > removing /tmp/puppet20100901-36732-16mgs1p-0...done > > > > > debug: /Stage[main]/Webbase::Apache/Exec[apache_purge]: Executing > > check '/bin/test -e /usr/local/etc/apache/ssl.crt' > > debug: Executing '/bin/test -e /usr/local/etc/apache/ssl.crt' > > removing /tmp/puppet20100901-50535-1p6j13j-0...done > > > > > /usr/local/lib/ruby/site_ruby/1.8/puppet/type.rb:1881: warning: > > instance variable @virtual not initialized > > debug: /Stage[main]/Webbase::Nas/Exec[/sbin/mount /proc]: Executing > > check '/sbin/mount | /usr/bin/egrep ^procfs' > > debug: Executing '/sbin/mount | /usr/bin/egrep ^procfs' > > removing /tmp/puppet20100901-95974-1n5jg13-0...done > > > > > I'm not really familliar with debugging tools (especially not for ruby > > applications), but I've added a few debug-statements and started a > > loop that runs puppet to see where it hangs. So far all I know is that > > it hangs after Puppet::Util::SUIDManager.run_and_capture() but before > > it returns from run(), I'll see if I can find exact statement where it > > hangs... > > > Regards > > -- > > Fredrik Eriksson > > I created a bug report over at puppetlabs so that someone who has more > knowledge and/or time could take a look at > it:http://projects.puppetlabs.com/issues/4681 > > Regards > -- > Fredrik Eriksson -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] help adding line to /etc/inittab
Thanks for the replies. I tried Rob's fix first since it just meant
removing one line from what I had. It worked like a charm!
Here is the final config to add that line to /etc/inittab:
augeas { "inittab" :
context => "/files/etc/inittab",
changes => [
"set ~/runlevels S",
"set ~/action wait",
"set ~/process /sbin/sulogin",
]
}
On Fri, Sep 3, 2010 at 7:44 AM, Rob McBroom wrote:
> 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.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] help adding line to /etc/inittab
Hi everyone. I am attempting to add this line to /etc/inittab so that a
user will be forced to enter a password to get into single user mode:
~:S:wait:/sbin/sulogin
I have tried all kinds of things, but seem to be having no luck. Here is
the puppet class I am trying to make:
class gen20 {
# Description: The UNIX host is bootable in single user mode
without a password.
# Insert "~~:S:wait:/sbin/sulogin" into /etc/inittab
augeas { "inittab" :
context => "/files/etc/inittab",
changes => [
"set ~ /~",
"set ~/runlevels S",
"set ~/action wait",
"set ~/process /sbin/sulogin",
]
}
}
Here is the pertinent debug output from a manual run feeding that code to
puppet:
debug: Augeas[inittab](provider=augeas): Opening augeas with root /, lens
path , flags 0
debug: Augeas[inittab](provider=augeas): Augeas version 0.5.0 is installed
debug: Augeas[inittab](provider=augeas): Will attempt to save and only run
if files changed
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
["/files/etc/inittab/~", "/~"]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
["/files/etc/inittab/~/runlevels", "S"]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
["/files/etc/inittab/~/action", "wait"]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
["/files/etc/inittab/~/process", "/sbin/sulogin"]
debug: Augeas[inittab](provider=augeas): Files changed, should execute
debug: Augeas[inittab](provider=augeas): Closed the augeas connection
debug: //ia/Augeas[inittab]: Changing returns
debug: //ia/Augeas[inittab]: 1 change(s)
debug: Augeas[inittab](provider=augeas): Opening augeas with root /, lens
path , flags 0
debug: Augeas[inittab](provider=augeas): Augeas version 0.5.0 is installed
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
["/files/etc/inittab/~", "/~"]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
["/files/etc/inittab/~/runlevels", "S"]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
["/files/etc/inittab/~/action", "wait"]
debug: Augeas[inittab](provider=augeas): sending command 'set' with params
["/files/etc/inittab/~/process", "/sbin/sulogin"]
debug: Augeas[inittab](provider=augeas): Closed the augeas connection
err: //ia/Augeas[inittab]/returns: change from need_to_run to 0 failed: Save
failed with return code false
debug: Finishing transaction -612453418 with 1 changes
Can anyone show me the proper way to insert this line into inittab using
augeas and puppet?
Thanks
Kit Stube
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Managing the same file from multiple modules/classes/manifests
You wouldn't by any chance be able to share those DISA SRR manifests to others would you?I've got to do the same thing here at work and it could be a good starting point. On Thu, Dec 17, 2009 at 8:21 PM, David Pheasant wrote: > Hey everyone, > > I accidentally sent an earlier (unfinished) version of this message to > the list, but hopefully it was moderated out. In any case, I'm > wondering about the best way to manage the contents of a single file > from multiple modules or maninfests/classes within the same module. > Specifically, I'm trying to manage the entries in /etc/pam.d/system- > auth-ac (we're running RedHat). > > Currently we have a module called 'unix-srr' that implements the DISA > unix security guidelines. One of the classes within this module (unix- > srr::pam) implements security settings that are involved with the > system-auth-ac file (password requirements, password history, su > usage). All the unix-srr::pam class does is define a file type that > updates/ensures the local file matches the version in the unix-srr/ > files/etc/pam.d/ module directory on the puppetmaster. > > Given the above scenario, what would be the best way to add the > ability to configure kerberos based authentication? This will also > require edits to the system-auth-ac file. I would like to put this > into a separate module/class since not all sites will need/require > kerberos authentication. As I see it there are two options: > > 1. Another class that re-implements the file based approach where the > source system-auth-ac file already includes the unix-srr changes. > > 2. Another class that implements an Augeas based solution. > > I think that we can all agree that Option 1 is a kludge since any > changes to the unix-srr version of the system-auth-ac file will also > have to be made to the kerberos-auth version; otherwise we'd have one > overwriting the other in an infinite loop. Option 2 is viable, but I > am annoyed by the amount of time that is required for changes via > Augeas since by default Augeas parses all files under /etc/. I have > tried setting the 'root' option of the augeas type to '/etc/pam.d/' > but this does not work as expected (I also tried this with augtool via > the AUGEAS_ROOT environment variable and it failed as well, so this is > an issue with Augeas and not puppet). > > So, does anyone have a suggestion for how to deal with this? I'm > pretty new to puppet so it may well be possible that the layout > described above is fundamentally flawed. > > Thanks in advance, > > -Dave > > -- > > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-us...@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet hangs
ib/libz.so.4
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
[Switching to Thread 0x28a79690 (LWP 100097)]
0x281b81a7 in __error () from /lib/libthr.so.3
(gdb) thread apply all
Please specify a command following the thread ID list
(gdb) bt full
#0 0x281b81a7 in __error () from /lib/libthr.so.3
No symbol table info available.
#1 0x281b7d88 in __error () from /lib/libthr.so.3
No symbol table info available.
#2 0x29f02060 in ?? ()
No symbol table info available.
#3 0x0008 in ?? ()
No symbol table info available.
#4 0x0001 in ?? ()
No symbol table info available.
#5 0x29f02040 in ?? ()
No symbol table info available.
#6 0xbc6faf2c in ?? ()
No symbol table info available.
#7 0x80018701 in ?? ()
No symbol table info available.
#8 0x in ?? ()
No symbol table info available.
#9 0x281b66df in pthread_setcancelstate () from /lib/libthr.so.3
No symbol table info available.
#10 0x281b5f7d in pthread_cond_signal () from /lib/libthr.so.3
No symbol table info available.
#11 0x280c34d4 in thread_timer (dummy=0xbf9aae5c) at eval.c:12318
running = (struct timer_thread *) 0x2816468c
start = (pthread_cond_t *) 0x28164698
to = {tv_sec = 1282824111, tv_nsec = 286055088}
err = 60
all_signals = {__bits = {4294967295, 4294967295, 4294967295,
4294967295}}
#12 0x281ad6ff in pthread_getprio () from /lib/libthr.so.3
No symbol table info available.
#13 0xbc5f9fec in ?? ()
No symbol table info available.
Erik
On 26 Aug, 13:51, Brice Figureau
wrote:
> On Thu, 2010-08-26 at 03:46 -0700, kit wrote:
> > [snip]
> > debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw
> > yaml; using pson
> > info: Caching catalog for kitbackup002.mid.dmz
>
> It just downloaded the catalog.
>
>
>
>
>
> > debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date-
> > nox does not exist
> > debug: Puppet::Type::Package::ProviderYum: file yum does not exist
> > debug: Puppet::Type::Package::ProviderAptrpm: file apt-get does not
> > exist
> > debug: Puppet::Type::Package::ProviderApt: file /usr/bin/apt-get does
> > not exist
> > debug: Puppet::Type::Package::ProviderFink: file /sw/bin/fink does not
> > exist
> > debug: Puppet::Type::Package::ProviderNim: file /usr/sbin/nimclient
> > does not exist
> > debug: Puppet::Type::Package::ProviderSun: file /usr/bin/pkginfo does
> > not exist
> > debug: Puppet::Type::Package::ProviderDpkg: file /usr/bin/dpkg does
> > not exist
> > debug: Puppet::Type::Package::ProviderUrpmi: file urpmi does not exist
> > debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper
> > does not exist
> > debug: Puppet::Type::Package::ProviderAptitude: file /usr/bin/aptitude
> > does not exist
> > debug: Puppet::Type::Package::ProviderRpm: file rpm does not exist
> > debug: Puppet::Type::Package::ProviderAix: file /usr/bin/lslpp does
> > not exist
> > debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/eix does
> > not exist
> > debug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not
> > exist
> > debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does
> > not exist
> > debug: Puppet::Type::Package::ProviderHpux: file /usr/sbin/swlist does
> > not exist
> > debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not
> > exist
> > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
> > yaml; using pson
>
> At this stage, it tries to fetch file metadata for a sourced file.
>
>
>
>
>
> > From gdb:
> > [Switching to Thread 0x28a79580 (LWP 100120)]
> > 0x281b81a7 in __error () from /lib/libthr.so.3
> > (gdb) set $ary = (int)backtrace(-1)
> > (gdb) set $count = *($ary+8)
> > (gdb) set $index = 0
> > (gdb) while $index < $count
> > >x/1s *((int)rb_ary_entry($ary, $index)+12)
> > >set $index = $index + 1
> > >end
> > 0x29f020c0: "/usr/local/lib/ruby/1.8/timeout.rb:59:in `start'"
> > 0x29f02100: "/usr/local/lib/ruby/1.8/timeout.rb:58:in `timeout'"
> > 0x29f02140: "/usr/local/lib/ruby/1.8/timeout.rb:93:in `timeout'"
> > 0x29f02180: "/usr/local/lib/ruby/1.8/net/protocol.rb:134:in
> > `rbuf_fill'"
> > 0x29f021c0: "/usr/local/lib/ruby/1.8/net/protocol.rb:116:in
> > `readuntil'"
> > 0x29f02200: "/usr/local/lib/ruby/1.8/net/protocol.rb:126:in
> > `readline'"
> > 0x29f02240: "/usr/local/lib/ruby/1.8/net/http.rb:2024:in
> > `read_status_line'"
> > 0x29f02280: "/usr/local/lib/ruby/1.8/net
[Puppet Users] Re: Puppet hangs
"/usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb: 39" 0x29f03650: "/usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb: 101:in `with_client'" 0x29f02500: "/usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb: 37" 0x29f036a0: "/usr/local/lib/ruby/site_ruby/1.8/puppet/ application.rb:171:in `call'" 0x29f036f0: "/usr/local/lib/ruby/site_ruby/1.8/puppet/ application.rb:171:in `controlled_run'" 0x29f02540: "/usr/local/lib/ruby/site_ruby/1.8/puppet/agent.rb: 35:in `run'" 0x29f03740: "/usr/local/lib/ruby/site_ruby/1.8/puppet/application/ agent.rb:114:in `onetime'" 0x29f043a0: "/usr/local/lib/ruby/site_ruby/1.8/puppet/application/ agent.rb:88:in `run_command'" 0x29f03790: "/usr/local/lib/ruby/site_ruby/1.8/puppet/ application.rb:300:in `run'" 0x29f037e0: "/usr/local/lib/ruby/site_ruby/1.8/puppet/ application.rb:397:in `exit_on_fail'" 0x29f03830: "/usr/local/lib/ruby/site_ruby/1.8/puppet/ application.rb:300:in `run'" 0x29f01040: "/usr/local/sbin/puppetd:4" (gdb) where #0 0x281b81a7 in __error () from /lib/libthr.so.3 #1 0x281b7d88 in __error () from /lib/libthr.so.3 #2 0x29f02060 in ?? () #3 0x0008 in ?? () #4 0x0001 in ?? () #5 0x29f02040 in ?? () #6 0xbc7fbf2c in ?? () #7 0x80018718 in ?? () #8 0x in ?? () #9 0x281b66df in pthread_setcancelstate () from /lib/libthr.so.3 #10 0x281b5f7d in pthread_cond_signal () from /lib/libthr.so.3 #11 0x280c34d4 in thread_timer (dummy=0xbf9ad2ac) at eval.c:12318 #12 0x281ad6ff in pthread_getprio () from /lib/libthr.so.3 #13 0xbc6fafec in ?? () On 26 Aug, 11:03, Brice Figureau wrote: > On Thu, 2010-08-26 at 01:08 -0700, kit wrote: > > I've never coded any ruby and don't know much about debugging, > > but I tried nevertheless to follow the guide so here's what I got. > > There's a lot of > > output here so please bear with me.. > > > First, I ran ruby --debug puppetd --trace --test, here's the output: > > # ruby --debug /usr/local/sbin/puppetd --server puppet.kulturit.no -- > > rundir /var/run/puppet --vardir /var/puppet --trace --verbose --test > > You ran ruby in debug mode, but in fact we don't care, what we want is > to run puppet in debug mode. > Can you try: > ruby /usr/local/sbin/puppetd --server puppet.kulturit.no --rundir > /var/run/puppet --vardir /var/puppet --trace --test --debug > > > [snip] > > The process is stuck here, tailing the however logfile claims puppetd > > is done...: > > > Aug 26 09:54:15 kitbackup002 puppet-agent[50287]: Reopening log files > > Aug 26 09:54:21 kitbackup002 puppet-agent[50287]: Finished catalog run > > in 3.03 seconds > > Hmm, why does it say "reopening log files"? > Did you restart it or change puppet.conf? > > > > > Second, I start gdb: > > # gdb `which ruby` 50403 > > > [Switching to Thread 0x28a7a130 (LWP 100152)] > > 0x2819d1a7 in __error () from /lib/libthr.so.3 > > Looks like there is a problem. > > > (gdb) set $ary = (int)backtrace(-1) > > (gdb) set $count = *($ary+8) > > (gdb) set $index = 0 > > (gdb) while $index < $count > > >x/1s *((int)rb_ary_entry($ary, $index)+12) > > >set $index = $index + 1 > > >end > > 0x29e020c0: "/usr/local/lib/ruby/1.8/net/protocol.rb:126:in > > `readline'" > > Apparently the thread is stuck in the net/http waiting for answer from > the master. > It looks like it is downloading some sourced files from the master. > > > > > > > 0x29e02100: "/usr/local/lib/ruby/1.8/net/http.rb:2024:in > > `read_status_line'" > > 0x29e02140: "/usr/local/lib/ruby/1.8/net/http.rb:2013:in > > `read_new'" > > 0x29e02180: "/usr/local/lib/ruby/1.8/net/http.rb:1050:in > > `request'" > > 0x29e021c0: "/usr/local/lib/ruby/1.8/net/http.rb:1037:in > > `request'" > > 0x29e02200: "/usr/local/lib/ruby/1.8/net/http.rb:543:in `start'" > > 0x29e02240: "/usr/local/lib/ruby/1.8/net/http.rb:1035:in > > `request'" > > 0x29e02280: "/usr/local/lib/ruby/1.8/net/http.rb:772:in `get'" > > 0x29e03060: "/usr/local/lib/ruby/site_ruby/1.8/puppet/indirector/ > > rest.rb:71:in `find'" > > 0x29e04040: "/usr/local/lib/ruby/site_ruby/1.8/puppet/indirector/ > > indirection.rb:193:in `find'" > > 0x29e030b0: "/usr/local/lib/ruby/site_ruby/1.8/puppet/ > > indirector.rb:50:in `find'" > >
[Puppet Users] Re: Puppet hangs
Hi We've got a main freebsd-class which all the servers use. It works like this: 1. Copies over a set over standardized configuration files (csh.cshrc, make.conf, vimrc +++), 2. Install some ports (just small ones (sudo, rsync +++), no big ones going on). 3. Edit some files such as sshd_config and crontab to set some options 4. Finally, enable some services in rc.conf It's all plain simple, nothing extraordinary, it really shouldn't crash the process... Erik On 25 Aug, 14:38, denmat wrote: > What sort of things are you trying to do? I've seen an issue like that > which was due to a recursive operation on a large file system (nfs > mounted). > You probably need to provide more information to get greater help. > > Cheers > DenMat > > On 25/08/2010, at 9:57 PM, kit wrote: > > > > > Yes, we tried that, that's actually the way we are running at the > > moment. However, to no avail.. > > > Thanks for the tip though :) > > > On 25 Aug, 13:26, merritt wrote: > >> Have you considered running puppet out of the cron and not as a > >> daemon? Since i have started running puppet out of the cron it works > >> pretty well. > > >>http://projects.reductivelabs.com/projects/puppet/wiki/Cron_Patterns > > >> Merritt. > > >> On Aug 25, 12:50 pm, kit wrote: > > >>> Hello, > > >>> we have one puppet server managing approx servers, all FreeBSD. > > >>> The problem is that the puppet clients all hangs, one by one, > >>> eventually. They will run for anything between an hour up to a week. > >>> But eventually the all hang. > > >>> We really like puppet and want to keep using it. But the way it is now > >>> is completely unusable. We've tried many versions, from 24.x, and now > >>> 2.6.1rc1. But the problem persists. > > >>> Ruby in debugging mode haven't revealed anything special as far as I > >>> can see. Now error in /var/log/messages, it just stalls... > > >>> Have anybody seen something similar? Please help! 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.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-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Puppet hangs
Yes, we tried that, that's actually the way we are running at the moment. However, to no avail.. Thanks for the tip though :) On 25 Aug, 13:26, merritt wrote: > Have you considered running puppet out of the cron and not as a > daemon? Since i have started running puppet out of the cron it works > pretty well. > > http://projects.reductivelabs.com/projects/puppet/wiki/Cron_Patterns > > Merritt. > > On Aug 25, 12:50 pm, kit wrote: > > > > > Hello, > > > we have one puppet server managing approx servers, all FreeBSD. > > > The problem is that the puppet clients all hangs, one by one, > > eventually. They will run for anything between an hour up to a week. > > But eventually the all hang. > > > We really like puppet and want to keep using it. But the way it is now > > is completely unusable. We've tried many versions, from 24.x, and now > > 2.6.1rc1. But the problem persists. > > > Ruby in debugging mode haven't revealed anything special as far as I > > can see. Now error in /var/log/messages, it just stalls... > > > Have anybody seen something similar? Please help! 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.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet hangs
Hello, we have one puppet server managing approx servers, all FreeBSD. The problem is that the puppet clients all hangs, one by one, eventually. They will run for anything between an hour up to a week. But eventually the all hang. We really like puppet and want to keep using it. But the way it is now is completely unusable. We've tried many versions, from 24.x, and now 2.6.1rc1. But the problem persists. Ruby in debugging mode haven't revealed anything special as far as I can see. Now error in /var/log/messages, it just stalls... Have anybody seen something similar? Please help! 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.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Weird SSL problem
I'm suddenly getting this weird error message. I don't recall changing any settings. Any help? # puppetca -l err: Could not create resources for managing Puppet's files and directories in sections [:main, :ssl, :ca]: Could not find a default provider for file err: Could not create resources for managing Puppet's files and directories in sections [:main, :ssl]: Could not find a default provider for file err: Could not create resources for managing Puppet's files and directories in sections [:main, :ssl]: Could not find a default provider for file err: Could not create resources for managing Puppet's files and directories in sections [:main, :ssl]: Could not find a default provider for file -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-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] Could not run Puppet configuration client: undefined method `keys' for nil:NilClass
I'm getting this error message quite often on the puppet clients. I don't know what it means. Restarting puppet often helps and the messages will go away, but suddenly it will come back again. Any thoughts? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Could not retrieve catalog from remote server
Nevermind, I found out that I had accidentially overwritten the puppet.conf... Luckily I had a backup and everything is up and running again :) On 9 Jun, 09:32, kit wrote: > I'm getting this frustrating error message and can't figure out why. > Puppet claims I'm missing a template file: > > err: Could not retrieve catalog from remote server: Error 400 on > SERVER: Could not find template 'nagios/nrpe.cfg/MASTER.erb' at /usr/ > local/etc/puppet/modules/nrpe/manifests/init.pp:22 on node > auth001.mid.no > warning: Not using cache on failed catalog > err: Could not retrieve catalog; skipping run > > I do know, however, that the template is there: > # ll /usr/local/etc/puppet/modules/nrpe/manifests/init.pp > -rw-rw-r-- 1 root wheel 1599 30 mar 14:34 /usr/local/etc/puppet/ > modules/nrpe/manifests/init.pp > # ll /usr/local/etc/puppet/templates/nagios/nrpe.cfg/MASTER.erb > -rw-rw-r-- 1 root wheel 7225 26 mar 16:06 templates/nagios/nrpe.cfg/ > MASTER.erb > > And the syntax is also correct: > # erb -x -T '-' /usr/local/etc/puppet/modules/nrpe/manifests/init.pp | > ruby -c > Syntax OK > # erb -x -T '-' templates/nagios/nrpe.cfg/MASTER.erb | ruby -c > Syntax OK > > So what is it then that is wrong? -- 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] Could not retrieve catalog from remote server
I'm getting this frustrating error message and can't figure out why. Puppet claims I'm missing a template file: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find template 'nagios/nrpe.cfg/MASTER.erb' at /usr/ local/etc/puppet/modules/nrpe/manifests/init.pp:22 on node auth001.mid.no warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run I do know, however, that the template is there: # ll /usr/local/etc/puppet/modules/nrpe/manifests/init.pp -rw-rw-r-- 1 root wheel 1599 30 mar 14:34 /usr/local/etc/puppet/ modules/nrpe/manifests/init.pp # ll /usr/local/etc/puppet/templates/nagios/nrpe.cfg/MASTER.erb -rw-rw-r-- 1 root wheel 7225 26 mar 16:06 templates/nagios/nrpe.cfg/ MASTER.erb And the syntax is also correct: # erb -x -T '-' /usr/local/etc/puppet/modules/nrpe/manifests/init.pp | ruby -c Syntax OK # erb -x -T '-' templates/nagios/nrpe.cfg/MASTER.erb | ruby -c Syntax OK So what is it then that is wrong? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Could not retrieve catalog from remote server: undefined method `closed?' for nil:NilClass
Thanks James, I installed the patch and got the proper error message "err: Could not retrieve catalog from remote server: hostname was not match with the server certificate". I'm using ruby 1.8.7. It's still weird however that it complains about the hostname as it was working before. Nevertheless, I remade the CA and it's now working so I'm happy. On 8 Jun, 18:46, James Turnbull wrote: > kit wrote: > > If I start ruby in debug mode and puppet in test the error message is > > different: > > ~# /usr/local/bin/ruby --debug /usr/local/sbin/puppetd --server > > puppet.kit.no --rundir /var/run/puppet --test > > Exception `OpenSSL::SSL::SSLError' at /usr/local/lib/ruby/1.8/openssl/ > > ssl.rb:123 - hostname wasnotmatch with theservercertificate > > Exception `NoMethodError' at /usr/local/lib/ruby/1.8/net/http.rb:1060 > > - undefined method `closed?' for nil:NilClass > > err:Couldnotretrievecatalogfromremoteserver: undefined method > > `closed?' for nil:NilClass > > warning:Notusing cache on failedcatalog > > err:Couldnotretrievecatalog; skipping run > > > However if I ommit the --test part in debug mode the certificate error > > goes away and I get the usual error message in the /var/log/message > > (Couldnotretrievecatalogfromremoteserver: undefined method > > `closed?' for nil:NilClass). So now I'm just really confused about the > > whole thing, been fighting with it for half a day. Anyone got some > > insights. Funny thing is that it was working fine until the reboot, > > but no changes were made... > > What Ruby version and platform are you on? This rather annoying message > is often the result of a Ruby 1.8.7 bug that hides the actual problem. > > See: > > http://projects.puppetlabs.com/issues/3101 > > And the patch (in Puppet 0.25.5): > > http://projects.puppetlabs.com/projects/puppet/repository/revisions/a... > > I suspect the underlying message above about a hostname mismatch is your > actual problem - has anything changed there? > > Regards > > James Turnbull -- 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] Could not retrieve catalog from remote server: undefined method `closed?' for nil:NilClass
We are getting this frustrating error on all of our servers after restarting the puppet server. Can't seem to get rid of it no matter what. The following pops up in /var/log/messages after trying to start puppetd: Jun 8 10:59:04 svn001 puppetd[92558]: Could not retrieve catalog; skipping run Jun 8 10:59:18 svn001 puppetd[92597]: Could not retrieve catalog from remote server: undefined method `closed?' for nil:NilClass Jun 8 10:59:18 svn001 puppetd[92597]: Not using cache on failed catalog Trying to start puppetd in test mode: ~# /usr/local/sbin/puppetd --test err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find template 'nagios/nrpe.cfg/MASTER.erb' at /usr/ local/etc/puppet/modules/nrpe/manifests/init.pp:22 on node svn001.mid.no warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run I have verified multiple times that the template puppet claims not to exists actually does exists so it must be a bogus error message. If I start ruby in debug mode and puppet in test the error message is different: ~# /usr/local/bin/ruby --debug /usr/local/sbin/puppetd --server puppet.kit.no --rundir /var/run/puppet --test Exception `OpenSSL::SSL::SSLError' at /usr/local/lib/ruby/1.8/openssl/ ssl.rb:123 - hostname was not match with the server certificate Exception `NoMethodError' at /usr/local/lib/ruby/1.8/net/http.rb:1060 - undefined method `closed?' for nil:NilClass err: Could not retrieve catalog from remote server: undefined method `closed?' for nil:NilClass warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run However if I ommit the --test part in debug mode the certificate error goes away and I get the usual error message in the /var/log/message (Could not retrieve catalog from remote server: undefined method `closed?' for nil:NilClass). So now I'm just really confused about the whole thing, been fighting with it for half a day. Anyone got some insights. Funny thing is that it was working fine until the reboot, but no changes were made... -- 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.
