Hi,
On Sun, 2 Feb 2025, Jérôme Charaoui wrote:
According to the log it seems like there's a segfault happening in the Ruby
SELinux binding. Do you have SELinux installed/enabled on this system?
libselinux1 and ruby-selinux were installed, but I think SELinux was not
configured at all.
After
Hi,
On 25-02-03 16:46:28, Grégory Brusick wrote:
> Since I don't have selinux installed, removing the package
> ruby-selinux solved the issue for me
The above worked for me as well.
Cheers,
Georg
Hi,
Same issue for me, but the issue seems to be related to ruby-selinux that was
updated from 3.7-3+b1, to 3.7-3.1 at the same time as puppet-agent from
8.10.0-2.1 to 8.10.0-4
Since I don't have selinux installed, removing the package ruby-selinux solved
the issue for me
Regards
Gregory
Hi,
On 02.02.25 15:32, Jérôme Charaoui wrote:
According to the log it seems like there's a segfault happening in the
Ruby SELinux binding. Do you have SELinux installed/enabled on this
system?
libselinux and ruby-selinux are installed, but I didn't configure
SELinux. So it should still hav
Hello,
Le 2025-02-02 à 05 h 01, Thorsten Alteholz a écrit :
Source: puppet-agent
Version: 8.10.0-2.1
Severity: serious
Hi,
when running "puppet agent -v -d -t" on Debian Trixie, I get the
attached backtrace. Is there some dependency missing? As this happens on
several VMs, I selected Severit
5 matches
Mail list logo
