On 06/03/25 Martin Hicks via linux said:
> Any chance that the kernel OOM handler is swooping in to save you?
Possible. I usually see that in the logs.
The vps has little resources
msoulier@nicodemus:~$ free -m
total used free shared buff/cache available
Mem: 457 174 117 3 179 282
Swap: 1023 222 801
Oh look at that.
kern.log:2025-03-06T03:43:55.631747+00:00 nicodemus kernel: [549916.988900] systemd-journal invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=-250
kern.log:2025-03-06T03:44:00.631168+00:00 nicodemus kernel: [549917.668001] systemd invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
kern.log:2025-03-06T03:53:22.312779+00:00 nicodemus kernel: [550484.460616] do-agent invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=-900
kern.log:2025-03-06T03:53:22.583143+00:00 nicodemus kernel: [550484.465167] containerd invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=-999
kern.log:2025-03-06T04:10:29.603663+00:00 nicodemus kernel: [551511.300658] do-agent invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=-900
kern.log:2025-03-06T04:23:31.416498+00:00 nicodemus kernel: [552293.566993] dpkg-query invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
and more, and more
Looks like resources are so tight that it's coming up a lot.
Guess I should pay for more or find a way to run leaner. Maybe DigitalOcean's
defaults are just too small.
Mike
Attachment:
signature.asc
Description: PGP signature