1

Topic: amavis is always stopped

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version: 1.6.1
- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version: 22.04 ubuntu
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? no
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

hey guys
amavis service is always stop for me, after duration of time amavis service stop
log:
Jan  2 14:53:35 mail amavis[382319]: (382319-20) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: No such file or directory
Jan  2 14:53:36 mail amavis[382319]: (382319-20) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: No such file or directory
Jan  2 14:53:36 mail amavis[382319]: (382319-20) (!)clamav-socket: All attempts (1) failed connecting to /var/run/clamav/clamd.ctl, retrying (2)
Jan  2 14:53:42 mail amavis[382319]: (382319-20) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: No such file or directory
Jan  2 14:53:42 mail amavis[382319]: (382319-20) (!)clamav-socket av-scanner FAILED: run_av error: Too many retries to talk to /var/run/clamav/clamd.ctl (All attempts (1) failed connecting to /var/run/clamav/clamd.ctl) at (eval 127) line 659.\n
Jan  2 14:53:42 mail amavis[382319]: (382319-20) (!)WARN: all primary virus scanners failed, considering backups
Jan  2 14:53:42 mail amavis[382319]: (382319-20) (!!)AV: ALL VIRUS SCANNERS FAILED


how can i fix?

----

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

2

Re: amavis is always stopped

clamav is not running, you should check the reasons for it

3

Re: amavis is always stopped

Check your memory on the server.  Probably ran out of memory and crashed.  Turning off performance metrics on mysql if not needed will help free up memory.