"freshclam" showed everything up to date, also "freshclam" after deleting *.cld and *.cvd didn't help. There were no error messages in any log when directly starting clamd from command line. "service clamd start" shows some "timed out" message.

Reading database took about 30s on Nov 28th (and before), after the antimalware update on Nov 29th the service continously timed out.

"yum history" shows that clearsdn-antimalware had been updated:



I cannot undo this update because yum cannot download the old version anymore.

I therefore uninstalled everything related to antimalware (gateway-antivirus, clam*, dans*, intrusion*, etc.) and reinstalled step by step. Now everthing is running as before, clamd loads the database again in 30s.

Interestingly the same happed on the other system at the same time, I'll try to repair this one tomorrow.

Hello Nick, that's what I did for now, seems to work, I'll have a look on it.

Thanks, Martin

The clearsdn-antimaware package causes the problem. When I uninstall it clamd reads it's databse very fast, when I install it (which takes some minutes) time for reading database increases.

What does this package include?

Sorry for posting the last reply more than once, I wanted to attach the log but always got "unsupported file format" error and didn't realise the reply was added, please delete the duplicate posts

I uninstalled a bunch of apps: app-file-scan, app-antimalware, app-antiphishing, app-antivirus, app-content-filter,app-mail-antivirus, clamav*, clearsdn-antimalware, clearsdn-antispam, dansguardian*, and web-proxy I think. I also removed all remaining clam* and dansguardian* folders and config files.

Unfortunately the problem is back again, after the update of clearsdn-antimalware today night at 05:15:39.

There have been two updates tonight, clearsdn-antispam at 3:55am and clearsdn-antimalware at 05:15. After clearsdn-antispam update everything was still ok, but after antimalware clamd service continously timed out. top shows clamd running with 100%, but I think this is because systemd tries to start it up after the service startup timed out.

clamd.log from tonight:

"freshclam" showed everything up to date, also "freshclam" after deleting *.cld and *.cvd didn't help. There were no error messages in any log when directly starting clamd from command line. "service clamd start" shows some "timed out" message.

Reading database took about 30s on Nov 28th (and before), after the antimalware update on Nov 29th the service continously timed out.

"yum history" shows that clearsdn-antimalware had been updated:



I cannot undo this update because yum cannot download the old version anymore.

I therefore uninstalled everything related to antimalware (gateway-antivirus, clam*, dans*, intrusion*, etc.) and reinstalled step by step. Now everthing is running as before, clamd loads the database again in 30s.

Interestingly the same happed on the other system at the same time, I'll try to repair this one tomorrow.

Clamd start-up times out

Since Nov 29th clamd does not startup anymore, it takes too long to read the virus database and is therefore terminated by systemd:



In clamd.log I see that the time needed for loading the virus database incresed from 40 seconds on Nov 28th to 1min 40 seconds (when I start clamd from command line).

Systemd timeout is 90s, thats why the service is terminated and does not come up anymore. I deleted and freshly updated the virus databases, but this didn't change anything.

Any ideas what has changed on Nov. 29th causing the problem? I have two systems showing the same behaviour (both are Zotac ZBOX CI323 nano running ClearOS 7.4)

Clamd start-up times out

Since Nov 29th clamd does not startup anymore, it takes too long to read the virus database and is therefore terminated by systemd:



In clamd.log I see that the time needed for loading the virus database incresed from 40 seconds on Nov 28th to 1min 40 seconds (when I start clamd from command line).

Systemd timeout is 90s, thats why the service is terminated and does not come up anymore. I deleted and freshly updated the virus databases, but this didn't change anything.

Any ideas what has changed on Nov. 29th causing the problem? I have two systems showing the same behaviour (both are Zotac ZBOX CI323 nano running ClearOS 7.4)

Clamd start-up times out

Since Nov 29th clamd does not startup anymore, it takes too long to read the virus database and is therefore terminated by systemd:



In clamd.log I see that the time needed for loading the virus database incresed from 40 seconds on Nov 28th to 1min 40 seconds (when I start clamd from command line).

Systemd timeout is 90s, thats why the service is terminated and does not come up anymore. I deleted and freshly updated the virus databases, but this didn't change anything.

Any ideas what has changed on Nov. 29th causing the problem? I have two systems showing the same behaviour (both are Zotac ZBOX CI323 nano running ClearOS 7.4)