Mailing List Archive

[clamav-users] clamd@scan.service starting but not running
Hi,


I had to fire-up a CENTOS 7 backup server as the main CENTOS 7 server
crashed and I updated the backup server to the latest CENTOS version 7,
incl Clamav 0.101.4.

The log says, the clam service is starting, but never gets to run
properly. Every systemctl status check I do says, it has restarted...

Any clue, as to what could be wrong? See logs below.


[root@server1 ~]# systemctl start clamd@scan.service

Job for clamd@scan.service failed because a timeout was exceeded. See
"systemctl status clamd@scan.service" and "journalctl -xe" for details.
[root@server1 ~]# journalctl -xe
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit clamd@scan.service has begun starting up.
Oct 13 11:43:55 server1.hartings.se clamd[12087]: Received 0 file
descriptor(s) from systemd.
Oct 13 11:43:55 server1.hartings.se clamd[12087]: clamd daemon 0.101.4
(OS: linux-gnu, ARCH: x86_64, CPU: x86_64)
Oct 13 11:43:55 server1.hartings.se clamd[12087]: Running as user
clamscan (UID 499, GID 498)
Oct 13 11:43:55 server1.hartings.se clamd[12087]: Log file size limited
to 1048576 bytes.
Oct 13 11:43:55 server1.hartings.se clamd[12087]: Reading databases from
/var/lib/clamav
Oct 13 11:43:55 server1.hartings.se clamd[12087]: Not loading PUA
signatures.
Oct 13 11:43:55 server1.hartings.se clamd[12087]: Bytecode: Security
mode set to "TrustSigned".
Oct 13 11:44:01 server1.hartings.se systemd[1]: Created slice User Slice
of root.
-- Subject: Unit user-0.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has finished starting up.
--
-- The start-up result is done.
Oct 13 11:44:01 server1.hartings.se systemd[1]: Started Session 2628 of
user root.
-- Subject: Unit session-2628.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-2628.scope has finished starting up.
--
-- The start-up result is done.
Oct 13 11:44:01 server1.hartings.se CROND[12096]: (root) CMD
(/root/Documents/webcam_copy_script.sh)
Oct 13 11:44:01 server1.hartings.se systemd[1]: Removed slice User Slice
of root.
-- Subject: Unit user-0.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-0.slice has finished shutting down.
[root@server1 ~]# systemctl status clam*
? clamd@scan.service - Generic clamav scanner daemon
   Loaded: loaded (/usr/lib/systemd/system/clamd@scan.service; enabled;
vendor preset: disabled)
   Active: activating (start) since Sun 2019-10-13 11:46:56 CEST; 14s ago
     Docs: man:clamd(8)
           man:clamd.conf(5)
           https://www.clamav.net/documents/
  Control: 12242 (clamd)
   CGroup: /system.slice/system-clamd.slice/clamd@scan.service
           ??12242 /usr/sbin/clamd -c /etc/clamd.d/scan.conf

Oct 13 11:46:56 server1.hartings.se systemd[1]: Starting Generic clamav
scanner daemon...
Oct 13 11:46:56 server1.hartings.se clamd[12242]: Received 0 file
descriptor(s) from systemd.
Oct 13 11:46:56 server1.hartings.se clamd[12242]: clamd daemon 0.101.4
(OS: linux-gnu, ARCH: x86_64, CPU: x86_64)
Oct 13 11:46:56 server1.hartings.se clamd[12242]: Running as user
clamscan (UID 499, GID 498)
Oct 13 11:46:56 server1.hartings.se clamd[12242]: Log file size limited
to 1048576 bytes.
Oct 13 11:46:56 server1.hartings.se clamd[12242]: Reading databases from
/var/lib/clamav
Oct 13 11:46:56 server1.hartings.se clamd[12242]: Not loading PUA
signatures.
Oct 13 11:46:56 server1.hartings.se clamd[12242]: Bytecode: Security
mode set to "TrustSigned".
[root@server1 ~]#


_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
Re: [clamav-users] clamd@scan.service starting but not running [ In reply to ]
On 13.10.2019 12:55, Ralf Hartings wrote:
> Hi,
>
>
> I had to fire-up a CENTOS 7 backup server as the main CENTOS 7 server
> crashed and I updated the backup server to the latest CENTOS version
> 7, incl Clamav 0.101.4.
>
> The log says, the clam service is starting, but never gets to run
> properly. Every systemctl status check I do says, it has restarted...
>
> Any clue, as to what could be wrong? See logs below.
>
>
> [root@server1 ~]# systemctl start clamd@scan.service
>
> Job for clamd@scan.service failed because a timeout was exceeded. See
> "systemctl status clamd@scan.service" and "journalctl -xe" for details.
> [root@server1 ~]# journalctl -xe
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Add to /usr/lib/systemd/system/clamd@.service

[Service]
TimeoutSec=600

sudo systemctl daemon-reload
sudo systemctl restart clamd@scan

Good luck,
Reio

_______________________________________________

clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
Re: [clamav-users] clamd@scan.service starting but not running [ In reply to ]
Hi!

Many thanks Reio! That did the trick!

It needed almost about a minut to get started (I know it's a slow backup
machine), but it runs now!
It complains though about

"Failed to get properties: Unit name clamd@.service is missing the
instance name.", see below.

Nothing to worry about I guess, as it seems to be running properly, but
strange.

[root@server1 system]# systemctl status clamd*
? clamd@scan.service - Generic clamav scanner daemon
   Loaded: loaded (/usr/lib/systemd/system/clamd@scan.service; enabled;
vendor preset: disabled)
   Active: *active (running)* since Sun 2019-10-13 12:49:48 CEST; 25s ago
     Docs: man:clamd(8)
           man:clamd.conf(5)
           https://www.clamav.net/documents/
  Process: 17973 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf
(code=exited, status=0/SUCCESS)
 Main PID: 18232 (clamd)
   CGroup: /system.slice/system-clamd.slice/clamd@scan.service
           ??18232 /usr/sbin/clamd -c /etc/clamd.d/scan.conf

Oct 13 12:49:45 server1.hartings.se clamd[18232]: ELF support enabled.
Oct 13 12:49:45 server1.hartings.se clamd[18232]: Mail files support
enabled.
Oct 13 12:49:45 server1.hartings.se clamd[18232]: OLE2 support enabled.
Oct 13 12:49:45 server1.hartings.se clamd[18232]: PDF support enabled.
Oct 13 12:49:45 server1.hartings.se clamd[18232]: SWF support enabled.
Oct 13 12:49:45 server1.hartings.se clamd[18232]: HTML support enabled.
Oct 13 12:49:45 server1.hartings.se clamd[18232]: XMLDOCS support enabled.
Oct 13 12:49:45 server1.hartings.se clamd[18232]: HWP3 support enabled.
Oct 13 12:49:45 server1.hartings.se clamd[18232]: Self checking every
600 seconds.
Oct 13 12:49:48 server1.hartings.se systemd[1]: Started Generic clamav
scanner daemon.
Failed to get properties: Unit name clamd@.service is missing the
instance name.
[root@server1 system]#


Den 2019-10-13 kl. 12:36, skrev Reio Remma via clamav-users:
> On 13.10.2019 12:55, Ralf Hartings wrote:
>> Hi,
>>
>>
>> I had to fire-up a CENTOS 7 backup server as the main CENTOS 7 server
>> crashed and I updated the backup server to the latest CENTOS version
>> 7, incl Clamav 0.101.4.
>>
>> The log says, the clam service is starting, but never gets to run
>> properly. Every systemctl status check I do says, it has restarted...
>>
>> Any clue, as to what could be wrong? See logs below.
>>
>>
>> [root@server1 ~]# systemctl start clamd@scan.service
>>
>> Job for clamd@scan.service failed because a timeout was exceeded. See
>> "systemctl status clamd@scan.service" and "journalctl -xe" for details.
>> [root@server1 ~]# journalctl -xe
>> -- Defined-By: systemd
>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
> Add to /usr/lib/systemd/system/clamd@.service
>
> [Service]
> TimeoutSec=600
>
> sudo systemctl daemon-reload
> sudo systemctl restart clamd@scan
>
> Good luck,
> Reio
>
> _______________________________________________
>
> clamav-users mailing list
> clamav-users@lists.clamav.net
> https://lists.clamav.net/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml