1

Topic: Error on Debian 9

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):  Latest
- Linux/BSD distribution name and version: Debian 9
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): PGSQL 9
- 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.
========================================================
*************************************************************************
* iRedMail-0.9.8 installation and configuration complete.
*************************************************************************

< Question > Would you like to use firewall rules provided by iRedMail?
< Question > File: /etc/default/iptables, with SSHD port: 22. [Y|n]y
[ INFO ] Copy firewall sample rules: /etc/default/iptables.
< Question > Restart firewall now (with SSHD port 22)? [y|N]y
[ INFO ] Restarting firewall ...
[ INFO ] Updating ClamAV database (freshclam), please wait ...
ERROR: /var/log/clamav/freshclam.log is locked by another process
ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).

================================================================================
in /var/log/clamav/freshclam.log:

Sat Oct 27 13:37:07 2018 -> --------------------------------------
Sat Oct 27 13:37:07 2018 -> freshclam daemon 0.100.2 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64)
Sat Oct 27 13:37:07 2018 -> ClamAV update process started at Sat Oct 27 13:37:07 2018
Sat Oct 27 13:37:08 2018 -> Downloading main.cvd [100%]
Sat Oct 27 13:37:17 2018 -> main.cvd updated (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
Sat Oct 27 13:37:18 2018 -> Downloading daily.cvd [100%]
Sat Oct 27 13:37:24 2018 -> daily.cvd updated (version: 25069, sigs: 2134628, f-level: 63, builder: raynman)
Sat Oct 27 13:37:24 2018 -> Downloading bytecode.cvd [100%]
Sat Oct 27 13:37:26 2018 -> bytecode.cvd updated (version: 327, sigs: 91, f-level: 63, builder: neo)
Sat Oct 27 13:37:29 2018 -> Database updated (6700968 signatures) from db.local.clamav.net (IP: 104.16.187.138)
Sat Oct 27 13:37:29 2018 -> WARNING: Clamd was NOT notified: Can't connect to clamd through /var/run/clamav/clamd.ctl: No such file or directory
Sat Oct 27 13:37:29 2018 -> --------------------------------------

----

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

2

Re: Error on Debian 9

Did not use any third party packages in this installation.

3

Re: Error on Debian 9

gao wrote:

Sat Oct 27 13:37:29 2018 -> WARNING: Clamd was NOT notified: Can't connect to clamd through /var/run/clamav/clamd.ctl: No such file or directory

This is a known "issue", during iRedMail installation, clamav-daemon service is not running (and it can NOT start due to no clamav virus signature database). So after iRedMail calls 'freshclam' command to update signature database, freshclam tries to notify clamav-daemon process, but obviously it will fail.

After iRedMail installation, iRedMail installer pints a message to remind you to reboot server to bring up all services (note: this is only required after installation).

4

Re: Error on Debian 9

ZhangHuangbin wrote:
gao wrote:

Sat Oct 27 13:37:29 2018 -> WARNING: Clamd was NOT notified: Can't connect to clamd through /var/run/clamav/clamd.ctl: No such file or directory

This is a known "issue", during iRedMail installation, clamav-daemon service is not running (and it can NOT start due to no clamav virus signature database). So after iRedMail calls 'freshclam' command to update signature database, freshclam tries to notify clamav-daemon process, but obviously it will fail.

After iRedMail installation, iRedMail installer pints a message to remind you to reboot server to bring up all services (note: this is only required after installation).

Thank you. Does that mean no action is required? I can just boot up the server and it wont cause an issue?

5

Re: Error on Debian 9

No action required.