1

Topic: Help with amavisd, stop responding

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version 2022082201 (Backend: pgsql, Date: 2022-09-10 17:58:40) iRedMail Easy:
- Deployed with iRedMail Easy or the downloadable installer? easy
- Linux/BSD distribution name and version: ubuntu 22.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PSQL
- Web server (Apache or Nginx): Nignx
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hi, in the last two days, im getting stuck with several messages on queue, around same time, both days. I checked the postqueue this problem:
4Mpr9Z50Y6z1y76       4352 Fri Oct 14 15:37:22 homsens263@xxxxx.tech
                   (connect to 127.0.0.1[127.0.0.1]:10026: Connection refused)
                                               yannick@xxxxx.tech

It seems, from what i searched online problem is related to the amavisd service, i tried to find this service as service amavisd status but it returns that the service unit doesnt exist. I dont know how the easy version runs the service.

Today i tried to telnet the above port (10026) it was returning error, i rebooted the service and the amavisd worked again and the queue sent all mails.

Someone had similar issues and can help me find what can be the issue? Or at least where i can try to find more information about, like logs? Im pretty new to linux mailing

----

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

2

Re: Help with amavisd, stop responding

the service is called amavisd-new

how much ram do you have?

3

Re: Help with amavisd, stop responding

- The service name is "amavis" on Debian/Ubuntu (and "amavisd" on CentOS).
- iRedMail requires at least 4 GB memory for low traffic production server.

4

Re: Help with amavisd, stop responding

Hi thanks for your reply. Since its a preproduction server, i was doing regular reboots because i didint have the time to check.

Im going into production and this problem is happening several times.
This server have less than 20 mail accounts, and it have 4gb of RAM, but i cant still pin what is causing the issue. Sometimes, it keeps several days without issues, sometimes i have the issue several times on same day, and the only thing that solves the issue, at least temporarily is rebooting the server.

Is there any log or log file where i can find the reason its crashing or stopping to work?

5

Re: Help with amavisd, stop responding

I got the log for the service, the following is reported:

○ amavis.service - Interface between MTA and virus scanner/content filters
     Loaded: loaded (/lib/systemd/system/amavis.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Mon 2022-11-28 16:43:48 UTC; 8min ago
       Docs:
    Process: 672 ExecStartPre=/usr/bin/find /var/lib/amavis -maxdepth 1 -name amavis-* -type d -exec rm -rf {} ; (code=exited, status=0/SUCCESS)
    Process: 805 ExecStartPre=/usr/bin/find /var/lib/amavis/tmp -maxdepth 1 -name amavis-* -type d -exec rm -rf {} ; (code=exited, status=0/SUCCESS)
    Process: 833 ExecStart=/usr/sbin/amavisd-new foreground (code=exited, status=0/SUCCESS)
   Main PID: 833 (code=exited, status=0/SUCCESS)
        CPU: 4.105s

Nov 28 16:35:29 server amavis[833]: No ext program for   .lrz, tried: lrzip -q -k -d -o -, lrzcat -q -k
Nov 28 16:35:29 server amavis[833]: No ext program for   .zoo, tried: zoo, unzoo
Nov 28 16:35:29 server amavis[833]: No decoder for       .F
Nov 28 16:35:29 server amavis[833]: No decoder for       .lrz
Nov 28 16:35:29 server amavis[833]: No decoder for       .zoo
Nov 28 16:35:29 server amavis[833]: Using primary internal av scanner code for clamav-socket
Nov 28 16:35:48 server amavis[833]: [69B blob data]
Nov 28 16:43:48 server amavis[833]: (00833-01) (!)Requesting process rundown, task exceeded allowed time during waiting for input from client
Nov 28 16:43:48 server systemd[1]: amavis.service: Deactivated successfully.
Nov 28 16:43:48 server systemd[1]: amavis.service: Consumed 4.105s CPU time.

6

Re: Help with amavisd, stop responding

When the issue happens, is ClamAV service running?

7

Re: Help with amavisd, stop responding

ZhangHuangbin wrote:

When the issue happens, is ClamAV service running?

On the last week, i didnt have any problems. How can i check if the clamav service is running?

The only correlation i found out was a series of messages to the postmaster/admin account not being delivered and on the queue. Since i manually removed all those messages it didnt stopped.

8

Re: Help with amavisd, stop responding

renato.sabo wrote:

How can i check if the clamav service is running?

Try:

service clamav-daemon status
service amavis status

9

Re: Help with amavisd, stop responding

both are up and running, and this time for more than a week now.

10

Re: Help with amavisd, stop responding

Since this server has 4GB memory, please try to REDUCE concurrently processed emails to one message by following this tutorial, to prevent ClamAV crash:
https://docs.iredmail.org/concurrent.processing.html