Clamd daemon not detected when running as a service.

[Pramod Daya]

Thanks – I tried that, and confirmed that I can connect to the port 3310 on all local IP address (localhost and public IP,  just in case:)

However, MailScanner just cannot see that clamd daemon when it’s started as a service :

Feb  5 18:22:55 mailgate5 MailScanner[24404]: MailScanner Email Processor version 5.0.3 starting...
Feb  5 18:22:55 mailgate5 MailScanner[24404]: Reading configuration file /etc/MailScanner/MailScanner.conf
Feb  5 18:22:55 mailgate5 MailScanner[24404]: Reading configuration file /etc/MailScanner/conf.d/README
Feb  5 18:22:55 mailgate5 MailScanner[24404]: Read 1714 hostnames from the phishing whitelist
Feb  5 18:22:55 mailgate5 MailScanner[24404]: Read 4686 hostnames from the phishing blacklists
Feb  5 18:22:55 mailgate5 MailScanner[24404]: Using SpamAssassin results cache
Feb  5 18:22:55 mailgate5 MailScanner[24404]: Connected to SpamAssassin cache database
Feb  5 18:22:57 mailgate5 MailScanner[24404]: Auto: Found virus scanners: sophos clamav
Feb  5 18:22:57 mailgate5 MailScanner[24404]: Connected to Processing Attempts Database
Feb  5 18:22:57 mailgate5 MailScanner[24404]: Found 1 messages in the Processing Attempts Database
Feb  5 18:22:57 mailgate5 MailScanner[24404]: Using locktype = flock



___________________________________________________
Pramod Daya (CEO)
M.Sc. Computer Science (U. of Oregon)
Unit 5, Melomed Office Park
Punters Way, Kenilworth
Cape Town, South Africa 7708
www.mindspring.co.za<http://www.mindspring.co.za/>
            [cid:image003.png at 01D5DC4D.D42ED850]
Work:  +27 21 657 1780
Fax:  +27 21 671 7599
  Cell:  +27 83 675 0367
pramod at mindspring.co.za


From: MailScanner <mailscanner-bounces+pramod=mindspring.co.za at lists.mailscanner.info> On Behalf Of Valentin Laskov
Sent: Tuesday, 04 February 2020 13:35
To: mailscanner at lists.mailscanner.info
Subject: Re: Clamd daemon not detected when running as a service.


Hello,

in

/etc/systemd/system/clamd at .service<mailto:/etc/systemd/system/clamd at .service>

add "TimeoutStartSec=360" like below if 360 seconds are anough for clamd to load signatures and open sockets at startup

[Service]
Type = forking
ExecStart = /usr/sbin/clamd -c /etc/clamd.d/%i.conf
TimeoutStartSec=360
Restart = on-failure

На 04.02.2020 в 08:25, Pramod Daya via MailScanner написа:
Hi Folks,

Clamd (101.4-1)  running as a service does not get detected by MailScanner (5.0.3-7)   After starting the service (on Centos 7) It takes quite a long time for clamd to become operational (up to a couple of minutes)  before you can connect to the socket (I have it configured on port 3310).

If I then restart MailScanner, then clamd is not detected, and Mailscanner uses clamav, which of course overloads the server.   If I start clamd from the command line, then Mailscanner detects clamd, and all is well.

Any/all advice would be very welcome.  I know that the config file is being read, because I change other parameters, like enabling debugging, and it gets interpreted.

Thank you,





--

Поздрави!



Валентин Ласков

Системен администратор

"Феста Холдинг" АД

бул. "Вл. Варненчик" 48

9000 гр. Варна

тел.:   +359 52 669137

GSM: +359 888 669137

Fax:   +359 52 669110
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mailscanner.info/pipermail/mailscanner/attachments/20200205/fb280910/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 5989 bytes
Desc: image003.png
URL: <http://lists.mailscanner.info/pipermail/mailscanner/attachments/20200205/fb280910/attachment.png>