Closed bphd closed 1 year ago
Sorry, but this is not actionable. There's no information about the environment or how to reproduce the issue, and just judging by the logs the system seems to be severely misconfigured. It doesn't seem to be a systemd issue, systemd is just a messenger here.
Env: Arch Didn't do anything for it to happpen, so idk how to reproduce What can be misconfigured?
Env: Arch
That's not enough. Is that a VM? Bare metal machine? Something else?
Didn't do anything for it to happpen, so idk how to reproduce What can be misconfigured?
Given the amount of OOM kills I'd say the machine runs low on memory. Nevertheless, the provided logs are not enough, we'd need the full journal from the boot.
Bare metal
It's not really about low memory, I even swap and all. It's these program that grow exponentially even when I'm not using them. Those program has a lot of issues reported of being ressource hungry even on big machines
There's really nothing we can do about this from systemd side. The machine clearly ran out of memory, so you need to investigate what caused that scenario in the first place.
It's these program that grow exponentially even when I'm not using them. Those program has a lot of issues reported of being ressource hungry even on big machines
It's these program that grow exponentially even when I'm not using them. Those program has a lot of issues reported of being ressource hungry even on big machines
systemd version the issue has been seen with
254.1-1
Used distribution
No response
Linux kernel version used
No response
CPU architectures issue was seen on
None
Component
No response
Expected behaviour you didn't see
No response
Unexpected behaviour you saw
No response
Steps to reproduce the problem
No response
Additional program output to the terminal or log subsystem illustrating the issue