Code: Select all
LOCAL: Could not create socket directory: /var/run/clamd.socket: Permission denied
Jan 29 19:16:38 clamd[7374]: ERROR: LOCAL: Could not create socket directory: /var/run/clamd.socket: Permission denied
Jan 29 19:16:38 clamd[7374]: ERROR: LOCAL: Socket file /var/run/clamd.socket/clamd.sock could not be bound: No such file or directory
Jan 29 19:16:38 clamd[7374]: LOCAL: Socket file /var/run/clamd.socket/clamd.sock could not be bound: No such file or directory
Code: Select all
postfix/master[23237]: warning: process /usr/libexec/postfix/pickup pid 20458 exit status 127
Jan 29 10:21:19 IT1MAILGW1 postfix/master[23237]: warning: /usr/libexec/postfix/pickup: bad command startup -- throttling
Could I disable virus scanning that messages are delivered. (As a temporary solution!).
Uptated subject due to further examination of problem
Problems have been identified after a reboot of the EFa VM:
Code: Select all
[ERROR] mysqld: Can't create/write to file '/run/mariadb/mariadb.pid' (Errcode: 2 "No such file or directory")
2020-01-29 11:49:54 140330304825088 [ERROR] Can't start server: can't create PID file: No such file or directory
Code: Select all
[suexec:notice] [pid 1571:tid 140156932184256] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Jan 29 11:49:52.571676 2020] [cgid:error] [pid 1647:tid 140156932184256] (2)No such file or directory: AH01243: Couldn't bind unix domain socket /run/httpd/cgisock.1571
[Wed Jan 29 11:49:52.572863 2020] [core:error] [pid 1571:tid 140156932184256] (2)No such file or directory: AH00099: could not create /run/httpd/httpd.pid
[Wed Jan 29 11:49:52.572893 2020] [core:error] [pid 1571:tid 140156932184256] AH00100: httpd: could not log pid to file /run/httpd/httpd.pid
clamd@scan claims still not be able to create
Code: Select all
/var/run/clamd.socket: Permission denied
Code: Select all
clamscan:mtagroup
As an emergency solution I have switched to my old eFA 3.0.26 VM which is now serving our organisation.
However, there are still e-mails stuck in the quarantine of the eFa 4.01. VM, which I believe they have not been delivered yet.
Any advise how to find the root cause of this problem and how to solve it would be appreciated.