From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 9A0407A4C8 for ; Fri, 7 May 2021 14:50:12 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 878442AD5C for ; Fri, 7 May 2021 14:50:12 +0200 (CEST) Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 671532AD46 for ; Fri, 7 May 2021 14:50:10 +0200 (CEST) Received: by mail-lf1-x132.google.com with SMTP id j10so12539335lfb.12 for ; Fri, 07 May 2021 05:50:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tecnetmza-com-ar.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=/oF04yrYFTz3v3cvbM/GKbF24LpfS3C9cavLK/CHHus=; b=utcMYkt6jkYL6x/T81PxrI78qO6QqvzuEJgg/V+dUEblC2kq8GM2d0ic2bSAHfvjv7 uEmK5k2Bq9GjyX8Mgaw8Bg73DavzT+2dYqne6zPGEUn+J04FOA/5PZ1gVGIL3tnMc9mN rXm2bSV+BHqWjXRVprPxxBdzOrmYNwRePA5n31uIfa96pr1f0TPL0RZ5fGkeeq7wBREp 9iiD3efEYIICWdjmsINxVBF05GTDAQiJ4Z/i/4+X5pzW+tT7kVoDYNK6QaUHfopzXiL3 F9NxeXs3vheSeO8R8hODNe1EUKfCNEbZLQ/NDb/dWaXyMkFJhXlTnXOvtUaQrYMncSW3 xD0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/oF04yrYFTz3v3cvbM/GKbF24LpfS3C9cavLK/CHHus=; b=H9MRQSqQhFT243VHZ7xKk6MPLqOoRyzm0Qp9gimcc1fin/QNiJXOUDGF3jvrsvc5i3 rqQYUk51/u6gld24ZNZyybew6M/exR/5SEr1NZMaTYbKMwfvUhiOgP05tRBjFuq4Z6b5 ymOLSoeTWiMMZdrggu0E6QFtA+REW6AG0X/Hd8snjZANpGYpB01m+HWlOtjVyTxMUR3O a0QtAuBDwbnVi2Stvk0Ffid0euThYax6SgFtuLeBrkb+//kvF3SyQ1RbKktalvPsVxx7 vodRyURB7MuSC/CjY5tDeGdg1n6g52ct9dioKZD7tnzYVzcuiHk59qIinuxVcHZFjMEp 41+g== X-Gm-Message-State: AOAM533lLK53reFTnuAy4xvj9n0Qll6mtr2CNHqL8YN0XsF4+VNScKVM r/ly4Xq91nf4GCVvPZ7xMLnWd6SnRpsCwcecwiR+3pSSgMZp0bQ= X-Google-Smtp-Source: ABdhPJzAmzU8WHa4Zdd0yC22W+CfP5qvlX5ES3ulHPFyIysTCPRsv911M2TnH1dLgdm7cIKl+x15gs8FN2bkJhcypU4= X-Received: by 2002:a05:6512:3e9:: with SMTP id n9mr6264643lfq.207.1620391803133; Fri, 07 May 2021 05:50:03 -0700 (PDT) MIME-Version: 1.0 From: Leandro Roggerone Date: Fri, 7 May 2021 09:49:59 -0300 Message-ID: To: PVE User List X-SPAM-LEVEL: Spam detection results: 1 AWL 0.203 Adjusted score from AWL reputation of From: address DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature HTML_MESSAGE 0.001 HTML included in message RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_SOFTFAIL 0.972 SPF: sender does not match SPF record (softfail) T_REMOTE_IMAGE 0.01 Message contains an external image Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [PVE-User] native container strange cpu usage behaviour X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 May 2021 12:50:12 -0000 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. Libre de virus. www.avast.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>