Log for OwO

#0: Load 7.3% Clock 3067mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz #1: Load 4.8% Clock 3100mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz #2: Load 1.4% Clock 3113mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz #3: Load 7.0% Clock 3009mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz

58.7gb / 59.0gb

#0: Load 4.7% Clock 3185mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz #1: Load 6.1% Clock 3187mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz #2: Load 0.9% Clock 1540mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz #3: Load 4.6% Clock 2673mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz

昨天我伺服器出警告了
CPU一直居高不下（tor只會spike）

然後發現是 kern.log跟journal log爆炸

去iptables看結果不知道為什麼log有4個分別在每個entry
systemd-journald用了一半的CPU嚇死我了

#0: Load 3.5% Clock 2853mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz #1: Load 4.0% Clock 2921mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz #2: Load 0.5% Clock 3299mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz #3: Load 3.5% Clock 2487mhz Model Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz