Re: [Puppet Users] b64_zlib_yaml errros after server upgrade to
Another thing to verify if you're you're using passenger you'll need to have the ssl header lines enabled in the puppet.conf: ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY On Wednesday, October 2, 2013 10:37:41 PM UTC-7, Tim Fall wrote: > > That might have been it, but I wiped out foreman and foreman-proxy and > reinstalled. > > On Thursday, October 3, 2013 2:29:05 PM UTC+9, Henrik Nicolaisen wrote: >> >> > I'm having the same issue as well. I tried enabling the dev repo, but >> no luck there with 3.3.1rc2. Also running in passenger under Foreman. >> >> try checking if you have both a repos version and a gem version >> installed, and if they are different, that was the error on my setup >> >> //Henrik > > -- 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
That might have been it, but I wiped out foreman and foreman-proxy and reinstalled. On Thursday, October 3, 2013 2:29:05 PM UTC+9, Henrik Nicolaisen wrote: > > > I'm having the same issue as well. I tried enabling the dev repo, but no > luck there with 3.3.1rc2. Also running in passenger under Foreman. > > try checking if you have both a repos version and a gem version installed, > and if they are different, that was the error on my setup > > //Henrik -- 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
> I'm having the same issue as well. I tried enabling the dev repo, but no luck > there with 3.3.1rc2. Also running in passenger under Foreman. try checking if you have both a repos version and a gem version installed, and if they are different, that was the error on my setup //Henrik -- 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
Thanks. Unfortunately I cannot further post any logs easily. That is the only puppet master instance that I currently run. I could upgrade and retry per request though. One more piece of information: the puppet master runs under passenger (I don't know how to enable --trace in this case). On Thu, Sep 19, 2013 at 4:02 PM, Henrik Nicolaisen wrote: > > > On Thursday, September 19, 2013 12:45:43 AM UTC+2, Patrick Carlisle wrote: > >> >> On Tue, Sep 17, 2013 at 1:14 AM, Andrei-Florian Staicu < >> andrei...@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. >> > > I created it here https://projects.puppetlabs.com/issues/22614 > > -- > 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. > -- Beware of programmers who carry screwdrivers! -- 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
On Thursday, September 19, 2013 12:45:43 AM UTC+2, Patrick Carlisle wrote: > > > On Tue, Sep 17, 2013 at 1:14 AM, Andrei-Florian Staicu < > andrei...@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. > I created it here https://projects.puppetlabs.com/issues/22614 -- 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] 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.
[Puppet Users] b64_zlib_yaml errros after server upgrade to
Hi, After upgrading the puppet server to puppet-server-3.3.0-1.el6.noarch, I get the following on a puppet-3.2.2-1.el6.noarch client: puppet agent --test --noop Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from b64_zlib_yaml: invalid bit length repeat Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run However, the erros look different with debug: puppet agent --test --noop --debug Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from b64_zlib_yaml: invalid bit length repeat Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run And with trace: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not intern from b64_zlib_yaml: invalid bit length repeat /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:185:in `is_http_200?' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:100:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:197:in `find' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:243:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:351:in `thinmark' /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:350:in `thinmark' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:242:in `retrieve_new_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:67:in `retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:107:in `prepare_and_retrieve_catalog' /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:159:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:20:in `lock' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/1.8/sync.rb:230:in `synchronize' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:45:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:119:in `with_client' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:42:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:84:in `run_in_fork' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:41:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:in `call' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:179:in `controlled_run' /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:39:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:353:in `onetime' /usr/lib/ruby/site_ruby/1.8/puppet/application/agent.rb:327:in `run_command' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:456:in `plugin_hook' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:504:in `exit_on_fail' /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:364:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:132:in `run' /usr/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:86:in `execute' /usr/bin/puppet:4 Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run Any idea if this is a recognized bug? Thanks. -- Beware of programmers who carry screwdrivers! -- 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.