+1 here.
We see this problem kind of problem on Puppet 3.4.3 and Scientific Linux
6.5.
Only the files causing the segfault are different from your case:
/usr/lib/ruby/site_ruby/1.8/puppet/util/autoload.rb:88: [BUG]
Segmentation fault
ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
Hi,
there seems to be no package for Debian 8 (Jessie) on apt.puppetlabs.com.
Neither in the jessie dist tree nor testing, where Puppet 3.8.1 for jessie
could be found previously.
Is this a mistake or will they be added later?
Regards,
Stefan
- Original Message -
From: Kylo Ginsberg
Hello,
we tried to today to migrate our Puppet Masters from Apache/Passenger to Puppet
Server 1.1.1.
However, Puppet Server just dies with error messages as soon as we increase the
number of JRuby instances to 24 and a JVM heapsize of 16GB.
During startup of Puppet Server, it starts to spawn
Hello,
in order to finish our Puppet 4.x migration (and than Puppet 5.x, yay),
PuppetDB has to be upgraded as well.
If I read the upgrade docs correctly, a direct upgrade from PuppetDB 2.3.x is
not supported [1].
So in order to do this, an upgrade to the latest version for each major release
ent: Wednesday, December 6, 2017 12:29:24 AM
> Subject: Re: [Puppet Users] Multiple Upgrades required for PuppetDB 2.3.x ->
> 4.4.1 and 5.x requirement?
> On 12/05/2017 01:57 PM, Dietrich, Stefan wrote:
>> Hello,
>>
>> in order to finish our Puppet 4.x migration (and tha
Hello Michael,
oh, another Puppet on Pi user :)
Any specific reason to drop the pl-build-tools for Debian 9 [1] ?
I have recently build Puppet Agent 1.10.10 for Debian 8/9 on armhf as
well...and for RHEL 7 on ppc64 (big endian).
I still found it easier to build the pl-build-tools packages than
Hello,
the release notes for Puppet Agent 7.27.0 mention an update of the bundled
Augeas to 1.14.1
However the packages still include Augeas 1.13.0 [1]:
[~]# rpm -q puppet-agent
puppet-agent-7.27.0-1.el8.x86_64
[~]# /opt/puppetlabs/puppet/bin/augtool --version
augtool 1.13.0
Hello,
> With the advent of RHEL 9, Red Hat has removed the ability to define
> network config using the old flat file method. It had been deprecated
> for a couple of major versions, but it's fully removed in RHEL 9.
> NetworkManager is the only option now.
according to the documentation, the