1 (edited by Almotzo 2021-01-15 02:42:38)

Topic: High CPU Load from Logwatch

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.3.2
- Deployed with iRedMail Easy or the downloadable installer? installer
- Linux/BSD distribution name and version: Debian 9.13
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): Maria DB
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? No
====

PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
11894 root      20   0  226272 202140   3808 R 100.0  1.6 853:18.34 logwatch
17790 root      20   0  233184 208536   3956 R 100.0  1.7   3720:05 logwatch
27175 root      20   0  226272 202180   3836 R  99.7  1.6   2282:32 logwatch

The process starts daily and runs indefinitely and causes 50% CPU load while idling. If I end the process with kill it will be sent by email


/etc/cron.daily/00logwatch:
/etc/cron.daily/00logwatch: line 7: 10528 Killed                  /usr/sbin/logwatch --output mail
run-parts: /etc/cron.daily/00logwatch exited with return code 137


But I cannot determine what the process is not getting done.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: High CPU Load from Logwatch

Maybe you have some very large log file(s) under /var/log/?

3

Re: High CPU Load from Logwatch

I don't know where from But / var / log / samba /
256 kb but 19359 files

That could have been the problem.

Samba was never installed, to be sure I did apt-get remove samba again and nothing was found. And there is also no running Samba process