Oh, I means I have found from where this was comming!

I had before on one container a hacker and I have down this container
(blocking customer) and I have forgot
to set the onboot=no and yesterday I have restart the host, but this is
interessting - and 999 is only a clone from
280 for analysis and this was start yesterday too (bad, why the
onboot=no was not set)!
Their must been something in the containers that can overload the host,
but in cron I have never found and for
the 280 the nettraffic was blocked via firewall completly.

oom-killer - so interessting for

root@ns315405:/var/log$ grep 'oom-killer' syslog.1
Mar  4 22:57:01 ns315405 kernel: 309960 (rrdtool) invoked oom-killer in
ub 280 generation 0 gfp 0x200d2
Mar  4 22:57:01 ns315405 kernel: oom-killer in ub 280 generation 0 ends:
task died
Mar  4 22:57:01 ns315405 kernel: 310006 (mysqld) invoked oom-killer in
ub 280 generation 1 gfp 0x200d2
Mar  4 22:57:01 ns315405 kernel: oom-killer in ub 280 generation 1 ends:
task died
Mar  4 23:20:17 ns315405 kernel: 660490 (rrdtool) invoked oom-killer in
ub 280 generation 2 gfp 0x200d2
Mar  4 23:20:17 ns315405 kernel: oom-killer in ub 280 generation 2 ends:
task died
Mar  4 23:22:26 ns315405 kernel: 754772 (setuidgid) invoked oom-killer
in ub 999 generation 0 gfp 0x200d2
Mar  4 23:22:26 ns315405 kernel: oom-killer in ub 999 generation 0 ends:
task died
Mar  4 23:24:09 ns315405 kernel: 824151 (run) invoked oom-killer in ub
999 generation 1 gfp 0x200d2
Mar  4 23:24:09 ns315405 kernel: oom-killer in ub 999 generation 1 ends:
task died
Mar  4 23:31:12 ns315405 kernel: 250036 (bash) invoked oom-killer in ub
280 generation 3 gfp 0x200d2
Mar  4 23:31:12 ns315405 kernel: oom-killer in ub 280 generation 3 ends:
task died
Mar  4 23:37:11 ns315405 kernel: 529499 (vzctl) invoked oom-killer in ub
280 generation 4 gfp 0x8000d0
Mar  4 23:37:11 ns315405 kernel: oom-killer in ub 280 generation 4 ends:
task died
Mar  4 23:37:41 ns315405 kernel: 549149 (bash) invoked oom-killer in ub
280 generation 5 gfp 0x200d2
Mar  4 23:37:41 ns315405 kernel: oom-killer in ub 280 generation 5 ends:
task died
Mar  4 23:47:32 ns315405 kernel: 945094 (bash) invoked oom-killer in ub
999 generation 3 gfp 0x200d2
Mar  4 23:47:32 ns315405 kernel: oom-killer in ub 999 generation 3 ends:
task died
Mar  4 23:54:21 ns315405 kernel: 59703 (rrdtool) invoked oom-killer in
ub 999 generation 4 gfp 0x200d2
Mar  4 23:54:21 ns315405 kernel: oom-killer in ub 999 generation 4 ends:
task died
Mar  4 23:55:01 ns315405 kernel: 72463 (rrdtool) invoked oom-killer in
ub 999 generation 5 gfp 0x200d2
Mar  4 23:55:01 ns315405 kernel: oom-killer in ub 999 generation 5 ends:
task died
Mar  5 00:00:01 ns315405 kernel: 116102 (sgrep) invoked oom-killer in ub
280 generation 12 gfp 0x200d2
Mar  5 00:00:01 ns315405 kernel: oom-killer in ub 280 generation 12
ends: task died
Mar  5 00:00:01 ns315405 kernel: 116667 (sh) invoked oom-killer in ub
999 generation 8 gfp 0x200d2
Mar  5 00:00:01 ns315405 kernel: oom-killer in ub 999 generation 8 ends:
task died
Mar  5 00:00:01 ns315405 kernel: 116838 (ps) invoked oom-killer in ub
999 generation 9 gfp 0x200d2
Mar  5 00:00:01 ns315405 kernel: oom-killer in ub 999 generation 9 ends:
task died
root@ns315405:/var/log$


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Reply via email to