I have also set preferred_serialization_format = yaml but I did need it in
order to be able to use puppet at windows machines (they did not accept
PSON due an OutOfMemory exception.
I'll try without that setting.
On Wednesday, October 10, 2012 10:14:22 PM UTC+2, thbe wrote:
Hi Josh,
Nobody has found this issue?
On Monday, October 8, 2012 5:08:33 PM UTC+2, David Campos wrote:
Hi all,
I'm trying to migrate our configuration from puppet 2.6.7 to 3.0.0 but I
am having a strange issue whilst applying the catalog.
Error: Could not retrieve catalog from remote server:
I haven't seen this specific issue yet.
How did you upgrade from 2.6 to 3.0.0? A common problem when
upgrading from source or with rubygems is having multiple copies of
puppet installed. This can cause issues loading code from both
versions of Puppet into the same process.
-Jeff
On Wed, Oct
2012/10/10 Jeff McCune j...@puppetlabs.com
I haven't seen this specific issue yet.
[...]
I saw this issue after an upgrade to 3.0.0 when I used manifests with a
package/service definition inside. Unfortunately I didn't had the time to
investigate this issue, so no solution from my side ...
On Wed, Oct 10, 2012 at 10:42 AM, Thomas Bendler
thomas.bend...@gmail.com wrote:
2012/10/10 Jeff McCune j...@puppetlabs.com
I haven't seen this specific issue yet.
[...]
I saw this issue after an upgrade to 3.0.0 when I used manifests with a
package/service definition inside. Unfortunately
Hi Josh,
2012/10/10 Josh Cooper j...@puppetlabs.com
[...]
I think puppet agent is expecting yaml, and is either receiving json
or otherwise can't parse the yaml it's receiving. We made performance
improvements in Puppet 3 relating to yaml parsing, so perhaps that is
the issue.
you are the
Hi Thomas,
On Wed, Oct 10, 2012 at 1:13 PM, Thomas Bendler
thomas.bend...@gmail.com wrote:
Hi Josh,
2012/10/10 Josh Cooper j...@puppetlabs.com
[...]
I think puppet agent is expecting yaml, and is either receiving json
or otherwise can't parse the yaml it's receiving. We made performance
