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
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
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 javascript: wrote:
Any idea if this is a recognized bug?
I don't think it is. Please file a bug report at projects.puppetlabs.comand
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
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
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
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
