Am 24.08.2021 um 00:34 schrieb Thomas Goirand:
On 8/23/21 5:40 PM, stoeni wrote:
Package: puppet
Version: 5.5.22-2
Severity: normal
X-Debbugs-Cc: none
After upgrading some Raspberry Pi (Zero, Model3/4) from buster to
bullseye, the puppet client no longer works on this architecture.
Steps to reproduce this error:
- install rasbian buster on a Raspberry Pi
- upgrade to bullseye
- run e.g. "puppet agent"
running puppet without arguments works:
------------------<8------------------
root@moon:~# puppet
See 'puppet help' for help on available puppet subcommands
------------------>8------------------
running puppet with arguments aborts:
------------------<8------------------
root@moon:~# puppet help
Aborted
------------------>8------------------
puppet 5.5.10 runs well on buster with amd64 or arm architecture, 5.5.22
runs on bullseye and amd64, not on arm.
as there are no log entries or any usable output how can i help to track
this thing down? maybe its ruby related?
would some strace output help?
Hi,
Are you *SURE* that the problem is the arch, and not the (very small)
amount of RAM you get on such a small device?
I do remember running puppet agent on 512 MB device, and it was eating a
lot of RAM already. This was 5 years ago... I wouldn't be surprised if
newer ruby and newer puppet agent used more memory...
Maybe you could try adding a lot of SWAP, just to try? (not saying that
a device swapping a lot is usable, but I just want to know if that would
work...)
Cheers,
Thomas Goirand (zigo)
Hi Thomas,
8G of RAM (without swap) on a Pi4 should be sufficient ;-)
------------------<8------------------
root@moon:~# free -h
total used free shared buff/cache available
Mem: 7.6Gi 62Mi 7.1Gi 0.0Ki 409Mi 7.4Gi
Swap: 0B 0B 0B
------------------8>------------------
5.5.10 runs well, but slow on the Pi zeros (512MB).
OOM should be logged via kernel/dmesg? But there is nothing logged....
--
cheers,
stoeni
* yes, we scan ! *
