From: Denis PUGNERE <d.pugnere@ipnl.in2p3.fr>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] native container strange cpu usage behaviour
Date: Fri, 7 May 2021 15:32:42 +0200 (CEST) [thread overview]
Message-ID: <1812088100.247408784.1620394362636.JavaMail.zimbra@ipnl.in2p3.fr> (raw)
In-Reply-To: <CALt2oz7aZs=n53_SmhtepT4DerfV8TgVz9DGatfesEpLknGOnw@mail.gmail.com>
Buenos dias Leandeo,
May be look at I/O errors, bad sectors on storage generate I/O wait on CPU without any processor activity.
or another source : NFS server not responding.
Cheers,
Denis
----- Le 7 Mai 21, à 14:49, Leandro Roggerone leandro@tecnetmza.com.ar a écrit :
> Hi guys.
> I was running unbound dns on native proxmox container.
> It is being monitored by librenms.
> After some time running without any problem following happened.
> First begin receiving snmp notifications regarding "high cpu/core
> temperature"
> (temperature was ok when checking at proxmox cli using sensor command)
> Then I noticed that cpu is at %100 all time on lnms cpu graphs.
> SO...
> I take out dns queries , stoped unbound and rebooted container , then after
> reboot, I have following top output.
>
> top - 12:46:02 up 52 min, 1 user, load average:* 7.93, *5.49, 5.60
> Tasks: 15 total, 1 running, 14 sleeping, 0 stopped, 0 zombie
> %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si,
> 0.0 st
> KiB Mem : 8388608 total, 8141576 free, 39164 used, 207868 buff/cache
> KiB Swap: 8388604 total, 8388604 free, 0 used. 8349444 avail Mem
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 1 root 20 0 43316 5052 3912 S 0.0 0.1 0:00.13 systemd
> 39 root 20 0 39092 6660 6372 S 0.0 0.1 0:00.03
> systemd-journal
> 51 root 20 0 41536 3132 2740 S 0.0 0.0 0:00.01
> systemd-udevd
> 57 dbus 20 0 58136 4200 3720 S 0.0 0.1 0:00.01
> dbus-daemon
> 58 root 20 0 26392 2928 2656 S 0.0 0.0 0:00.01
> systemd-logind
> 65 root 20 0 6524 1712 1588 S 0.0 0.0 0:00.00 agetty
> 68 root 20 0 6524 1640 1520 S 0.0 0.0 0:00.00 agetty
> 69 root 20 0 6524 1612 1488 S 0.0 0.0 0:00.00 agetty
> 70 root 20 0 22708 2636 2012 S 0.0 0.0 0:00.00 crond
> 273 root 20 0 112932 7688 6656 S 0.0 0.1 0:00.01 sshd
> 275 root 20 0 218560 4996 4180 S 0.0 0.1 0:00.16 rsyslogd
> 276 root 20 0 124696 15860 10952 S 0.0 0.2 0:01.47 snmpd
> 291 root 20 0 155340 10596 9240 S 0.0 0.1 0:00.18 sshd
> 293 root 20 0 11944 3072 2596 S 0.0 0.0 0:00.06 bash
> 490 root 20 0 56216 3944 3352 R 0.0 0.0 0:00.00 top
>
>
> So ... Question is , why load average is so high if there is no processes
> consuming cpu.
> Any idea / feedback about this?
> Thanks.
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> Libre
> de virus. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2021-05-07 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 12:49 Leandro Roggerone
2021-05-07 13:32 ` Denis PUGNERE [this message]
2021-05-07 15:32 ` Leandro Roggerone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1812088100.247408784.1620394362636.JavaMail.zimbra@ipnl.in2p3.fr \
--to=d.pugnere@ipnl.in2p3.fr \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox