Re: [Puppet Users] Re: PuppetDB SSL error
Russel: Can you confirm the same error message that Hugh is receiving in your own puppetdb.log? Hugh: I'd suggest raising a bug with all the details: http://projects.puppetlabs.com/projects/puppetdb/issues/new ... Russell, if the problem looks the same I'd confirm it in the same ticket so we can correlate. The more people seeing the issue that can help with debugging the problem the better. At first glance any details around command/query frequency would be useful as well, so we can understand if its load related (or not). Also - details around exact Ruby version and distro/version, version of OpenSSL linked to Ruby and exact flavour/version of Java you are using with PuppetDB might help. Anyone else getting this same error? I have not seen it before so I would be curious to hear if its prevalent. ken. On Fri, Mar 22, 2013 at 6:12 PM, Hugh Cole-Baker wrote: > On Friday, March 22, 2013 10:47:15 AM UTC, Russell Parsloe wrote: >> >> I'm running PuppetDB 1.1.1 with Puppet 3.1, both on the same server. >> Occasionally nodes report this error: >> >>> err: Could not retrieve catalog from remote server: Error 400 on SERVER: >>> Could not retrieve resources from the PuppetDB at >>> puppet.mydomain.local:8081: SSL_connect SYSCALL returned=5 errno=0 >>> state=SSLv3 read finished A on node client-2.mydomain.local >> >> >> It doesn't happen on every agent run - most times it runs just fine. >> >> The names on my SSL certificates appear to be correct, aka its the same >> one that is used in puppet.conf. >> >> Any ideas on things I can at least check to try and track down and get rid >> of this error? I could understand it if the error occurred on every run, but >> its bugging me that its just occasional. > > > I'm also seeing intermittent failure reports from nodes, with the same error > message from the master. It's normally accompanied by a message in the > PuppetDB logs: > WARN [qtp1193921293-27694] [io.nio] javax.net.ssl.SSLHandshakeException: > Invalid Padding length: 114 > or > WARN [qtp1193921293-39] [io.nio] javax.net.ssl.SSLHandshakeException: > Invalid TLS padding data > > -- > 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?hl=en. > 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] err: Could not retrieve catalog from remote server: Error 400 on SERVER: Error 403 on SERVER: Forbidden request:
Puppet runs fine on RHEL 6.2. It looks like your auth.conf is missing some entries. Do you perhaps have an auth.conf.rpmnew you need to move into place? - Keith Hi All, I am trying to follow the documentation at this link: http://docs.puppetlabs.com/pe/latest/quick_start.html When I get to the part where one runs ... sudo puppet agent --test I get this error message ... err: Could not retrieve catalog from remote server: Error 400 on SERVER: Error 403 on SERVER: Forbidden request: red-cricket-pe-master (xxx.xxx.xxx.xx) access to /facts/red-cricket-agent [save] authenticated at line 45 warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Both systems are Red Hat Enterprise Linux Server release 6.2 (Santiago) ... maybe puppet does not support this version of redhat? Thanks Red -- 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?hl=en. 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet augeas with more than one array in a single key
Anyone, Dude ! Sir ?
NOTE : I am using Puppet-3.0.2.x.
On Friday, March 22, 2013 1:48:55 PM UTC-5, iamauser wrote:
>
> I am trying to put together a set of puppet policies for grub/menu.lst.
> The serial::grubmenulst looks like this :
>
> define serial::grubmenulst ( $value ) {
>$key = $title
>$context = "/files/boot/grub/menu.lst"
>augeas { "grubmenulst/${key}":
> context => "$context",
> onlyif => "get $key != '$value'",
> changes => "set $key '$value'",
>}
> }
>
> It is implemented in the following way :
>
> $svar = "${serial_tty},${serial_speed}n8r"
> serial::grubmenulst {
> "terminal/console" : value => "";
> "title[1]/kernel/elevator" : value => "deadline";
> "title[1]/kernel/console[1]" : value => "${svar}"; *### It Fails
> for this Line otherwise it works*
> }
>
> Puppet agent complains during the run (see below). Note that, the code
> works if I comment out the last line: "title[1]/kernel/console[1]" :
> value => "${svar}". My initial guess is that puppet-augeas is not able
> to parse more than one array values for a single key... (!?)
>
> Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError:
> Invalid resource type serial::grubmenulst at
> /etc/puppet/modules/serial/manifests/serial.pp:16 on node
>
> Any suggestions ?
>
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Patch Management
What Module do I install to use Puppet as Patch management? I have WSUS on my network already , but I need a patch management application to patch 3rd party software like java, flash, Thanks -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] "could not retrieve catalog from server" error on windows
Hello I get the error in title when I run puppet agent on my windows 7 machine I can ping puppet master just fine with no problem. thanks -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] warning: Could not retrieve fact fqdn
Hi;
After applying this pp i get this error.
*file {'/tmp/test1':*
* ensure => present,*
* content => "Hi.",*
*}*
*
*
*file {'/tmp/test2':*
* ensure => directory,*
* mode => 0644,*
*}*
*
*
*file {'/tmp/test3':*
* ensure => link,*
* target => '/tmp/test1',*
*}*
*
*
*notify {"I'm notifying you.":} # Whitespace is fungible, remember.*
*notify {"So am I!":}*
*warning: Could not retrieve fact fqdn*
Any one know why?
Regards
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: How to override $::operatingsystem fact
EDIT: In fact it does work. I found out, because I still had some keys (e.g. hostname) in my debugging config. And these values were used by puppet correctly. However a local "facter -p" won't show these values. In this case the original hostname will be used. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: PuppetDB SSL error
I was helping someone on IRC with a similar issue the other day...it looks like there may be a bug in very recent 1.7 OpenJDK versions that cause this to happen. Reverting to an earlier JDK version resolved the issue. As Ken mentioned, it would be most helpful if we could get the Ruby/OpenSSL/JDK versions from your masters and puppetdb servers. Thanks! On Sat, Mar 23, 2013 at 2:04 AM, Ken Barber wrote: > Russel: Can you confirm the same error message that Hugh is receiving > in your own puppetdb.log? > > Hugh: I'd suggest raising a bug with all the details: > http://projects.puppetlabs.com/projects/puppetdb/issues/new ... > Russell, if the problem looks the same I'd confirm it in the same > ticket so we can correlate. The more people seeing the issue that can > help with debugging the problem the better. At first glance any > details around command/query frequency would be useful as well, so we > can understand if its load related (or not). Also - details around > exact Ruby version and distro/version, version of OpenSSL linked to > Ruby and exact flavour/version of Java you are using with PuppetDB > might help. > > Anyone else getting this same error? I have not seen it before so I > would be curious to hear if its prevalent. > > ken. > > On Fri, Mar 22, 2013 at 6:12 PM, Hugh Cole-Baker wrote: > > On Friday, March 22, 2013 10:47:15 AM UTC, Russell Parsloe wrote: > >> > >> I'm running PuppetDB 1.1.1 with Puppet 3.1, both on the same server. > >> Occasionally nodes report this error: > >> > >>> err: Could not retrieve catalog from remote server: Error 400 on > SERVER: > >>> Could not retrieve resources from the PuppetDB at > >>> puppet.mydomain.local:8081: SSL_connect SYSCALL returned=5 errno=0 > >>> state=SSLv3 read finished A on node client-2.mydomain.local > >> > >> > >> It doesn't happen on every agent run - most times it runs just fine. > >> > >> The names on my SSL certificates appear to be correct, aka its the same > >> one that is used in puppet.conf. > >> > >> Any ideas on things I can at least check to try and track down and get > rid > >> of this error? I could understand it if the error occurred on every > run, but > >> its bugging me that its just occasional. > > > > > > I'm also seeing intermittent failure reports from nodes, with the same > error > > message from the master. It's normally accompanied by a message in the > > PuppetDB logs: > > WARN [qtp1193921293-27694] [io.nio] javax.net.ssl.SSLHandshakeException: > > Invalid Padding length: 114 > > or > > WARN [qtp1193921293-39] [io.nio] javax.net.ssl.SSLHandshakeException: > > Invalid TLS padding data > > > > -- > > 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?hl=en. > > 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?hl=en. > 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: PuppetDB SSL error
Awesome news Deepak, I suspected "SSL something" which is why I was asking for JDK and OpenSSL details ... be good to nail down exact revisions (and distros in case of special patching they might do) so we can get an errata out somehow - so if anyone has seen this - be kind & report! :-). On Sat, Mar 23, 2013 at 8:32 PM, Deepak Giridharagopal wrote: > I was helping someone on IRC with a similar issue the other day...it looks > like there may be a bug in very recent 1.7 OpenJDK versions that cause this > to happen. Reverting to an earlier JDK version resolved the issue. As Ken > mentioned, it would be most helpful if we could get the Ruby/OpenSSL/JDK > versions from your masters and puppetdb servers. Thanks! > > > On Sat, Mar 23, 2013 at 2:04 AM, Ken Barber wrote: >> >> Russel: Can you confirm the same error message that Hugh is receiving >> in your own puppetdb.log? >> >> Hugh: I'd suggest raising a bug with all the details: >> http://projects.puppetlabs.com/projects/puppetdb/issues/new ... >> Russell, if the problem looks the same I'd confirm it in the same >> ticket so we can correlate. The more people seeing the issue that can >> help with debugging the problem the better. At first glance any >> details around command/query frequency would be useful as well, so we >> can understand if its load related (or not). Also - details around >> exact Ruby version and distro/version, version of OpenSSL linked to >> Ruby and exact flavour/version of Java you are using with PuppetDB >> might help. >> >> Anyone else getting this same error? I have not seen it before so I >> would be curious to hear if its prevalent. >> >> ken. >> >> On Fri, Mar 22, 2013 at 6:12 PM, Hugh Cole-Baker wrote: >> > On Friday, March 22, 2013 10:47:15 AM UTC, Russell Parsloe wrote: >> >> >> >> I'm running PuppetDB 1.1.1 with Puppet 3.1, both on the same server. >> >> Occasionally nodes report this error: >> >> >> >>> err: Could not retrieve catalog from remote server: Error 400 on >> >>> SERVER: >> >>> Could not retrieve resources from the PuppetDB at >> >>> puppet.mydomain.local:8081: SSL_connect SYSCALL returned=5 errno=0 >> >>> state=SSLv3 read finished A on node client-2.mydomain.local >> >> >> >> >> >> It doesn't happen on every agent run - most times it runs just fine. >> >> >> >> The names on my SSL certificates appear to be correct, aka its the same >> >> one that is used in puppet.conf. >> >> >> >> Any ideas on things I can at least check to try and track down and get >> >> rid >> >> of this error? I could understand it if the error occurred on every >> >> run, but >> >> its bugging me that its just occasional. >> > >> > >> > I'm also seeing intermittent failure reports from nodes, with the same >> > error >> > message from the master. It's normally accompanied by a message in the >> > PuppetDB logs: >> > WARN [qtp1193921293-27694] [io.nio] >> > javax.net.ssl.SSLHandshakeException: >> > Invalid Padding length: 114 >> > or >> > WARN [qtp1193921293-39] [io.nio] javax.net.ssl.SSLHandshakeException: >> > Invalid TLS padding data >> > >> > -- >> > 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?hl=en. >> > 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?hl=en. >> 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?hl=en. > 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
