Control: reassign -1 libaugeas0
Control: found -1 1.2.0-1
Control: fixed -1 1.5.0-1
Control: tags -1 upstream fixed-upstream
Hi,
On 21:39 Mon 18 Jan , Felix Hagemann wrote:
> Program received signal SIGSEGV, Segmentation fault.
> strlen () at ../sysdeps/x86_64/strlen.S:106
> 106
On 17 January 2016 Markus Frosch wrote:
> Can you verify that the following test brings the same crash?
Yes, I can reproduce the test with your minimal example:
# cat augtest2.pp
augeas { "sshd_config":
changes => [
"set /files/etc/ssh/sshd_config/PermitRootLogin no",
],
}
# puppet apply
On 12.01.2016 21:00, Felix Hagemann wrote:
> I hope this helps.
I'm afraid not, got basically the same environment on my notebook, and I
haven't got any problems with augeas.
Can you verify that the following test brings the same crash?
If so, we need to continue with gdb to find out what lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08.01.2016 23:47, Felix Hagemann wrote:
> /usr/lib/ruby/vendor_ruby/puppet/provider/augeas/augeas.rb:346: [BUG]
> Segmentation fault at 0x01 ruby 2.2.3p173
> (2015-08-18) [x86_64-linux-gnu]
This sounds a lot like a problem between
Markus Frosch wrote:
>> /usr/lib/ruby/vendor_ruby/puppet/provider/augeas/augeas.rb:346: [BUG]
>> Segmentation fault at 0x01 ruby 2.2.3p173
>> (2015-08-18) [x86_64-linux-gnu]
>
> This sounds a lot like a problem between ruby-augeas and libaugeas0.
>
> Can you share us:
> * dpkg -l
Felix Hagemann writes:
> Segmentation fault at 0x01
> ruby 2.2.3p173 (2015-08-18) [x86_64-linux-gnu]
According to
https://docs.puppetlabs.com/guides/platforms.html#ruby-versions, puppet
3.x is incompatible with ruby 2.2.
Please see if you can reproduce the
Package: puppet
Version: 3.8.4-1
Severity: important
Dear Maintainer,
wondering why puppet agent has not been applying configuration changes
for a while, I ran puppet agent manually in debug mode and realised
that it is segfaulting when applying the configuration changes.
First few lines:
7 matches
Mail list logo