Leah Neukirchen on Nostr: Pro tip: If you use systemd-run (v250.4) as a glorified setsid(2) wrapper, consider ...
Pro tip: If you use systemd-run (v250.4) as a glorified setsid(2) wrapper, consider also using --collect; else, failing runs will accumulate systemd units, which keep around a network cgroup, which by default has an eBPF filter, and at some point these filters clog the 1.5G vmalloc area, resulting in kernel oom, which causes crashes somewhere down that stack.
Published at
2023-10-04 21:29:50Event JSON
{
"id": "ea5ba66c0fbb8ea725b2bc28c5451ecc63e862cee7d067bc86e2337981e00e7e",
"pubkey": "7aa203c84c694cba0553d8ba8efe07656bcfeedd1bd432c310bfb14886c1ec7f",
"created_at": 1696454990,
"kind": 1,
"tags": [
[
"content-warning",
"systemd"
],
[
"proxy",
"https://blahaj.social/users/leah/statuses/111178874273762258",
"activitypub"
]
],
"content": "Pro tip: If you use systemd-run (v250.4) as a glorified setsid(2) wrapper, consider also using --collect; else, failing runs will accumulate systemd units, which keep around a network cgroup, which by default has an eBPF filter, and at some point these filters clog the 1.5G vmalloc area, resulting in kernel oom, which causes crashes somewhere down that stack.",
"sig": "bf29d727381831d5211a19822d284451fa7ef15d2aae5ea86fc19593ea83309928e3551ffdc833d489f205b4bab7aaa75ec2679dd093fcfdf068ee79eff73e4f"
}
