[opensuse] I can't start clamd
Hi, I can not start clamd. I then used zypper up, then tried again. No go. The clamd goes into 100% CPU while it tries to start. Legolas:~ # time rcclamd start Job for clamd.service failed because a timeout was exceeded. See "systemctl status clamd.service" and "journalctl -xe" for details. real 1m30.201s user 0m0.032s sys 0m0.032s Legolas:~ # main log: <3.6> 2019-05-09 14:40:01 Legolas systemd 1 - - Starting Clamav antivirus Deamon... <3.4> 2019-05-09 14:41:31 Legolas systemd 1 - - clamd.service: Start operation timed out. Terminating. <3.3> 2019-05-09 14:41:32 Legolas systemd 1 - - Failed to start Clamav antivirus Deamon. <3.5> 2019-05-09 14:41:32 Legolas systemd 1 - - clamd.service: Unit entered failed state. <3.4> 2019-05-09 14:41:32 Legolas systemd 1 - - clamd.service: Failed with result 'timeout'. main log: <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Received 0 file descriptor(s) from systemd. <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - clamd daemon 0.101.2 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64) <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Running as user vscan (UID 65, GID 459) <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Log file size limited to 1048576 bytes. <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Reading databases from /var/lib/clamav <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Not loading PUA signatures. <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Bytecode: Security mode set to "TrustSigned". <2.6> 2019-05-09 14:40:59 Legolas postfix 4602 - - timeout after END-OF-MESSAGE from localhost[127.0.0.1] <2.6> 2019-05-09 14:40:59 Legolas postfix 4602 - - disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 commands=4 Legolas:~ # systemctl status clamd.service ● clamd.service - Clamav antivirus Deamon Loaded: loaded (/usr/lib/systemd/system/clamd.service; enabled; vendor preset: disabled) Active: failed (Result: timeout) since Thu 2019-05-09 14:41:32 CEST; 6min ago Process: 5596 ExecStart=/usr/sbin/clamd (code=killed, signal=TERM) May 09 14:40:02 Legolas.valinor clamd[5596]: clamd daemon 0.101.2 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64) May 09 14:40:02 Legolas.valinor clamd[5596]: Running as user vscan (UID 65, GID 459) May 09 14:40:02 Legolas.valinor clamd[5596]: Log file size limited to 1048576 bytes. May 09 14:40:02 Legolas.valinor clamd[5596]: Reading databases from /var/lib/clamav May 09 14:40:02 Legolas.valinor clamd[5596]: Not loading PUA signatures. May 09 14:40:02 Legolas.valinor clamd[5596]: Bytecode: Security mode set to "TrustSigned". May 09 14:41:31 Legolas.valinor systemd[1]: clamd.service: Start operation timed out. Terminating. May 09 14:41:32 Legolas.valinor systemd[1]: Failed to start Clamav antivirus Deamon. May 09 14:41:32 Legolas.valinor systemd[1]: clamd.service: Unit entered failed state. May 09 14:41:32 Legolas.valinor systemd[1]: clamd.service: Failed with result 'timeout'. Legolas:~ # journal: May 09 14:41:31 Legolas.valinor systemd[1]: clamd.service: Start operation timed out. Terminating. May 09 14:41:32 Legolas.valinor systemd[1]: Failed to start Clamav antivirus Deamon. -- Subject: Unit clamd.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit clamd.service has failed. -- -- The result is failed. May 09 14:41:32 Legolas.valinor systemd[1]: clamd.service: Unit entered failed state. May 09 14:41:32 Legolas.valinor systemd[1]: clamd.service: Failed with result 'timeout'. System is 15.0, as per signature. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
Hi Carlos, Do you have the freshclam service running also? That is needed to update the clam database and if I recall correctly I think clamd does chew up the CPU while waiting for it's database if it is not available. Marc.. On 5/9/19 5:51 AM, Carlos E. R. wrote:
Hi,
I can not start clamd. I then used zypper up, then tried again. No go. The clamd goes into 100% CPU while it tries to start.
Legolas:~ # time rcclamd start Job for clamd.service failed because a timeout was exceeded. See "systemctl status clamd.service" and "journalctl -xe" for details.
real 1m30.201s user 0m0.032s sys 0m0.032s Legolas:~ #
main log:
<3.6> 2019-05-09 14:40:01 Legolas systemd 1 - - Starting Clamav antivirus Deamon... <3.4> 2019-05-09 14:41:31 Legolas systemd 1 - - clamd.service: Start operation timed out. Terminating. <3.3> 2019-05-09 14:41:32 Legolas systemd 1 - - Failed to start Clamav antivirus Deamon. <3.5> 2019-05-09 14:41:32 Legolas systemd 1 - - clamd.service: Unit entered failed state. <3.4> 2019-05-09 14:41:32 Legolas systemd 1 - - clamd.service: Failed with result 'timeout'.
main log:
<2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Received 0 file descriptor(s) from systemd. <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - clamd daemon 0.101.2 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64) <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Running as user vscan (UID 65, GID 459) <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Log file size limited to 1048576 bytes. <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Reading databases from /var/lib/clamav <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Not loading PUA signatures. <2.6> 2019-05-09 14:40:02 Legolas clamd 5596 - - Bytecode: Security mode set to "TrustSigned". <2.6> 2019-05-09 14:40:59 Legolas postfix 4602 - - timeout after END-OF-MESSAGE from localhost[127.0.0.1] <2.6> 2019-05-09 14:40:59 Legolas postfix 4602 - - disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 commands=4
Legolas:~ # systemctl status clamd.service ● clamd.service - Clamav antivirus Deamon Loaded: loaded (/usr/lib/systemd/system/clamd.service; enabled; vendor preset: disabled) Active: failed (Result: timeout) since Thu 2019-05-09 14:41:32 CEST; 6min ago Process: 5596 ExecStart=/usr/sbin/clamd (code=killed, signal=TERM)
May 09 14:40:02 Legolas.valinor clamd[5596]: clamd daemon 0.101.2 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64) May 09 14:40:02 Legolas.valinor clamd[5596]: Running as user vscan (UID 65, GID 459) May 09 14:40:02 Legolas.valinor clamd[5596]: Log file size limited to 1048576 bytes. May 09 14:40:02 Legolas.valinor clamd[5596]: Reading databases from /var/lib/clamav May 09 14:40:02 Legolas.valinor clamd[5596]: Not loading PUA signatures. May 09 14:40:02 Legolas.valinor clamd[5596]: Bytecode: Security mode set to "TrustSigned". May 09 14:41:31 Legolas.valinor systemd[1]: clamd.service: Start operation timed out. Terminating. May 09 14:41:32 Legolas.valinor systemd[1]: Failed to start Clamav antivirus Deamon. May 09 14:41:32 Legolas.valinor systemd[1]: clamd.service: Unit entered failed state. May 09 14:41:32 Legolas.valinor systemd[1]: clamd.service: Failed with result 'timeout'. Legolas:~ #
journal:
May 09 14:41:31 Legolas.valinor systemd[1]: clamd.service: Start operation timed out. Terminating. May 09 14:41:32 Legolas.valinor systemd[1]: Failed to start Clamav antivirus Deamon. -- Subject: Unit clamd.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- <b>Computers: the final frontier. These are the voyages of the user Marc.<br> His mission: to explore strange new hardware. To seek out new software and new applications.<br> To boldly go where no Marc has gone before!<br></b> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/05/2019 19.17, Marc Chamberlin wrote:
Hi Carlos, Do you have the freshclam service running also? That is needed to update the clam database and if I recall correctly I think clamd does chew up the CPU while waiting for it's database if it is not available.
Yes, it must be running. At least it should. The problem here is that clamd on start goes full CPU and gets killed by systemd after a minute and a half because it did not report back finished startup. So this must be related to people reporting clamd or freshclam going full cpu for long time. A hack would be perhaps to tell systemd to wait way much longer, as much as it takes. I will power up the laptop again and perhaps run freshclam manually. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/05/2019 19.22, Carlos E. R. wrote:
On 09/05/2019 19.17, Marc Chamberlin wrote:
Hi Carlos, Do you have the freshclam service running also? That is needed to update the clam database and if I recall correctly I think clamd does chew up the CPU while waiting for it's database if it is not available.
Yes, it must be running. At least it should.
The problem here is that clamd on start goes full CPU and gets killed by systemd after a minute and a half because it did not report back finished startup.
So this must be related to people reporting clamd or freshclam going full cpu for long time.
A hack would be perhaps to tell systemd to wait way much longer, as much as it takes.
I will power up the laptop again and perhaps run freshclam manually.
It updated just before the time it failed: May 09 14:19:01 Legolas.valinor freshclam[1383]: main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr) May 09 14:19:01 Legolas.valinor freshclam[1383]: daily.cld is up to date (version: 25444, sigs: 1566720, f-level: 63, builder: raynman) May 09 14:19:01 Legolas.valinor freshclam[1383]: bytecode.cld is up to date (version: 328, sigs: 94, f-level: 63, builder: neo) Manual update refuses, says it is up to date. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 9 mei 2019 19:22:00 CEST schreef Carlos E. R.:
On 09/05/2019 19.17, Marc Chamberlin wrote:
Hi Carlos, Do you have the freshclam service running also? That is needed to update the clam database and if I recall correctly I think clamd does chew up the CPU while waiting for it's database if it is not available.
Yes, it must be running. At least it should.
The problem here is that clamd on start goes full CPU and gets killed by systemd after a minute and a half because it did not report back finished startup.
So this must be related to people reporting clamd or freshclam going full cpu for long time.
A hack would be perhaps to tell systemd to wait way much longer, as much as it takes.
Depending on the type of system the default timeout for a systemd job of 90 seconds might be to short. On a small system I use, I enter the line TimeoutStartSec=600s after [Service] in clamd.service. I copy /usr/lib/systemd/system/clamd.service to /etc/systemd/system/ and make the insertion there. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/05/2019 12.45, Freek de Kruijf wrote:
Op donderdag 9 mei 2019 19:22:00 CEST schreef Carlos E. R.:
A hack would be perhaps to tell systemd to wait way much longer, as much as it takes.
Depending on the type of system the default timeout for a systemd job of 90 seconds might be to short. On a small system I use, I enter the line
TimeoutStartSec=600s
after [Service] in clamd.service. I copy /usr/lib/systemd/system/clamd.service to /etc/systemd/system/ and make the insertion there.
Ah, you change that for this service only. I did for all. I would create directory "/etc/systemd/system/clamd.service.d", and in there the drop-in file "override.conf" with the modifications. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/05/2019 14.51, Carlos E. R. wrote:
Hi,
I can not start clamd. I then used zypper up, then tried again. No go. The clamd goes into 100% CPU while it tries to start.
Legolas:~ # time rcclamd start Job for clamd.service failed because a timeout was exceeded. See "systemctl status clamd.service" and "journalctl -xe" for details.
real 1m30.201s user 0m0.032s sys 0m0.032s Legolas:~ #
Edit /etc/systemd/system.conf DefaultTimeoutStartSec=3600s DefaultTimeoutStopSec=3600s (default is 90) systemctl daemon-reload Legolas:~ # time systemctl start clamd.service real 1m32,196s user 0m0,000s sys 0m0,018s Legolas:~ # Now I set back the timeout to 100 seconds. 3600 was a brutal hack. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/09/2019 01:28 PM, Carlos E. R. wrote:
Now I set back the timeout to 100 seconds. 3600 was a brutal hack.
Did you figure out what required the hack? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/05/2019 02.48, David C. Rankin wrote:
On 05/09/2019 01:28 PM, Carlos E. R. wrote:
Now I set back the timeout to 100 seconds. 3600 was a brutal hack.
Did you figure out what required the hack?
As I said, "rcclamd start" was taking more than 30 seconds to complete, so systemd killed it. Figuring that maybe it needed an hour, I told systemd to wait up to an hour. Turned out that it just needed 32 seconds. It is not freshclam problem, it is "clamd start" problem. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/09/2019 07:51 AM, Carlos E. R. wrote:
Hi,
I can not start clamd. I then used zypper up, then tried again. No go. The clamd goes into 100% CPU while it tries to start.
https://bugzilla.opensuse.org/show_bug.cgi?id=1133465 ?? -- David C. Rankin, J.D.,P.E.
On Thu, 9 May 2019 19:35:03 -0500 David C. Rankin wrote:
On 05/09/2019 07:51 AM, Carlos E. R. wrote:
Hi,
I can not start clamd. I then used zypper up, then tried again. No go. The clamd goes into 100% CPU while it tries to start.
https://bugzilla.opensuse.org/show_bug.cgi?id=1133465
??
"Workaround: To solve the problem, # ctrl+c hung process # rm /var/lib/clamav/daily.cvd # freshclam see: https://lists.gt.net/clamav/users/74966 " -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/05/2019 02.56, Carl Hartung wrote:
On Thu, 9 May 2019 19:35:03 -0500 David C. Rankin wrote:
On 05/09/2019 07:51 AM, Carlos E. R. wrote:
Hi,
I can not start clamd. I then used zypper up, then tried again. No go. The clamd goes into 100% CPU while it tries to start.
No, it was not freshclam which hung in my case.
??
"Workaround:
To solve the problem,
# ctrl+c hung process
It is a daemon. You can kill PID it. Or killall name
# rm /var/lib/clamav/daily.cvd # freshclam
next time :-)
Too long thread... I see several people with the same problem. But in my case, freshclam had run and apparently finished before, this was about starting the clamd process. Different thing. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Carl Hartung -
Carlos E. R. -
Carlos E. R. -
David C. Rankin -
Freek de Kruijf -
Marc Chamberlin