Mailing List Archive

Hi,

Just comment the line NotifyClamd path-to-clamd.conf in freshclam.conf

[freshclam.conf]
.
.
# NotifyClamd ........


Re

El mié, 26 abr 2023 a las 13:21, Marc (<Marc@f1-outsourcing.eu>) escribió:

>
> I am running freshclam in a build layer in docker to download default
> databases for the docker image. Obviously nothing else is installed at this
> stage.
>
> apk add freshclam --no-cache
> touch /etc/clamav/clamd.conf (added this, otherwise freshclam complained
> about it not existing)
> freshclam
>
> results in this error:
>
> ERROR: NotifyClamd: No communication socket specified in
> /etc/clamav/clamd.conf
> ERROR: Can't send to clamd: Not a socket
>
>
> How do I execute freshclam and do not inform clamd? This used to be the
> default, it is sort of obvious that if the clamd.conf does not exist
> freshclam does not need to do anything.
> _______________________________________________
>
> Manage your clamav-users mailing list subscription / unsubscribe:
> https://lists.clamav.net/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/Cisco-Talos/clamav-documentation
>
> https://docs.clamav.net/#mailing-lists-and-chat
>

It is building now, although I am still getting an error. What I do not get this the design change behind this. Normally I could install only freshclam, and without doing anything download the current databases for the container.
Now I have to create a clamd.conf file[1] and getting all kinds of errors. Either freshclam is part of the clamav-daemon clamav-db clamav packages or not. If it not, there should not be a dependency on file included in an external package. What kind of logics is this. Why even change something that was good ...

etc/clamav # freshclam --stdout
ClamAV update process started at Sun Apr 30 11:05:23 2023
daily database available for download (remote version: 26892)
Time: 0.8s, ETA: 0.0s [========================>] 58.40MiB/58.40MiB
Testing database: '/var/lib/clamav/tmp.2d473bc9f9/clamav-8dd1897da8048bac7afd3c826a555c43.tmp-daily.cvd' ...
Database test passed.
daily.cvd updated (version: 26892, sigs: 2032828, f-level: 90, builder: raynman)
main database available for download (remote version: 62)
Time: 1.6s, ETA: 0.0s [========================>] 162.58MiB/162.58MiB
Testing database: '/var/lib/clamav/tmp.2d473bc9f9/clamav-93d1ad81cac0cfad9b0a2305580caccc.tmp-main.cvd' ...
Database test passed.
main.cvd updated (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr)
bytecode database available for download (remote version: 334)
Time: 0.1s, ETA: 0.0s [========================>] 285.12KiB/285.12KiB
Testing database: '/var/lib/clamav/tmp.2d473bc9f9/clamav-f4998549cecd71d461021e791730d124.tmp-bytecode.cvd' ...
Database test passed.
bytecode.cvd updated (version: 334, sigs: 91, f-level: 90, builder: anvilleg)
ERROR: Missing argument for option at /etc/clamav/clamd.conf:2
ERROR: NotifyClamd: Can't find or parse configuration file /etc/clamav/clamd.conf

[1]
/etc/clamav # cat /etc/clamav/clamd.conf

[freshclam.conf]


>
> Just comment the line NotifyClamd path-to-clamd.conf in freshclam.conf
>
> [freshclam.conf]
> .
> .
> # NotifyClamd ........
>
>
> Re
>
>
> El mié, 26 abr 2023 a las 13:21, Marc (<Marc@f1-outsourcing.eu
> <mailto:Marc@f1-outsourcing.eu> >) escribió:
>
>
>
> I am running freshclam in a build layer in docker to download
> default databases for the docker image. Obviously nothing else is
> installed at this stage.
>
> apk add freshclam --no-cache
> touch /etc/clamav/clamd.conf (added this, otherwise freshclam
> complained about it not existing)
> freshclam
>
> results in this error:
>
> ERROR: NotifyClamd: No communication socket specified in
> /etc/clamav/clamd.conf
> ERROR: Can't send to clamd: Not a socket
>
>
> How do I execute freshclam and do not inform clamd? This used to be
> the default, it is sort of obvious that if the clamd.conf does not exist
> freshclam does not need to do anything.
> _______________________________________________
>
> Manage your clamav-users mailing list subscription / unsubscribe:
> https://lists.clamav.net/mailman/listinfo/clamav-users
>
>
> Help us build a comprehensive ClamAV guide:
> https://github.com/Cisco-Talos/clamav-documentation
>
> https://docs.clamav.net/#mailing-lists-and-chat
>

_______________________________________________

Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation

https://docs.clamav.net/#mailing-lists-and-chat

On 30.04.23 15:56, Marc wrote:
> It is building now, although I am still getting an error. What I do not
> get this the design change behind this. Normally I could install only
> freshclam, and without doing anything download the current databases for
> the container.

> Now I have to create a clamd.conf file[1] and getting all kinds of errors.
> Either freshclam is part of the clamav-daemon clamav-db clamav packages or
> not. If it not, there should not be a dependency on file included in an
> external package. What kind of logics is this. Why even change something
> that was good ...
>
>ERROR: Missing argument for option at /etc/clamav/clamd.conf:2
>ERROR: NotifyClamd: Can't find or parse configuration file /etc/clamav/clamd.conf
>
>[1]
>/etc/clamav # cat /etc/clamav/clamd.conf
>
>[freshclam.conf]

this clamd.conf is malformed. freshclam uses real clamd.conf not just random
file.

you can leave database checking to clamd itself, you don't have to
explicitly notify it. See the clamd docs, option SelfCheck.;

--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
(R)etry, (A)bort, (C)ancer
_______________________________________________

Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation

https://docs.clamav.net/#mailing-lists-and-chat