jacobgc
commented
5 years ago [Sun Dec 9 06:56:07 2018] [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name
[Sun Dec 9 06:56:07 2018] [ 228] 0 228 3051 160 12 3 624 0 haveged
[Sun Dec 9 06:56:07 2018] [ 231] 0 231 9234 586 21 3 21 0 systemd-journal
[Sun Dec 9 06:56:07 2018] [ 485] 0 485 4030 52 12 3 162 0 dhclient
[Sun Dec 9 06:56:07 2018] [ 579] 109 579 10725 61 26 4 74 -900 dbus-daemon
[Sun Dec 9 06:56:07 2018] [ 583] 0 583 6933 29 18 3 40 0 cron
[Sun Dec 9 06:56:07 2018] [ 585] 108 585 64098 152 27 4 238 0 rsyslogd
[Sun Dec 9 06:56:07 2018] [ 589] 0 589 5024 22 13 3 40 0 systemd-logind
[Sun Dec 9 06:56:07 2018] [ 654] 0 654 3665 0 12 3 38 0 agetty
[Sun Dec 9 06:56:07 2018] [ 655] 0 655 3619 0 12 3 34 0 agetty
[Sun Dec 9 06:56:07 2018] [ 697] 0 697 16377 38 34 4 141 -1000 sshd
[Sun Dec 9 06:56:07 2018] [ 716] 106 716 10066 42 22 3 101 0 ntpd
[Sun Dec 9 06:56:07 2018] [ 1407] 1001 1407 6667 300 16 3 24 0 screen
[Sun Dec 9 06:56:07 2018] [ 1408] 1001 1408 5287 2 15 3 430 0 bash
[Sun Dec 9 06:56:07 2018] [ 6417] 1001 6417 1009494 216973 1841 7 522007 0 xmrig-proxy
[Sun Dec 9 06:56:07 2018] [23302] 0 23302 11008 12 22 3 92 -1000 systemd-udevd
[Sun Dec 9 06:56:07 2018] Out of memory: Kill process 6417 (xmrig-proxy) score 952 or sacrifice child
[Sun Dec 9 06:56:07 2018] Killed process 6417 (xmrig-proxy) total-vm:4037976kB, anon-rss:867892kB, file-rss:0kBLooking at that dmesg output it seems very likely that it was xmrig-proxy's fault
May or may not be an issue, but I was running the latest master branch build and noticed I had 0 hash rate on the pool I'm minging on. Did a little bit of digging and noticed the OOM killer killed the proxy. I'm only running the proxy so I'm not too sure if xmr-proxy is the issue or if it was something else.