Mailing List Archive

[clamav-users] problem with clamav upgrade
Hello!

On a centos7 I did a yum update today and new version of clamav
was installed.

ps aux |grep clam
amavis 6683 0.0 20.9 1016312 814072 ? Ssl 15:14 0:00 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf

# freshclam
Wed Dec 11 15:52:45 2019 -> ClamAV update process started at Wed Dec 11 15:52:45 2019
Wed Dec 11 15:52:45 2019 -> ^Your ClamAV installation is OUTDATED!
Wed Dec 11 15:52:45 2019 -> ^Local version: 0.101.5 Recommended version: 0.102.1
Wed Dec 11 15:52:45 2019 -> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
Wed Dec 11 15:52:45 2019 -> main.cld is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
Wed Dec 11 15:52:45 2019 -> daily.cld is up to date (version: 25660, sigs: 2043646, f-level: 63, builder: raynman)
Wed Dec 11 15:52:45 2019 -> bytecode.cld is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg)

This happens after a reboot after having tried to get it working without reboot,

What is going wrong here? Should clamd be running after amavis is started?

Andreas

_______________________________________________

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] problem with clamav upgrade [ In reply to ]
On 11.12.19 15:57, ratatouille via clamav-users wrote:
>On a centos7 I did a yum update today and new version of clamav
>was installed.
>
>ps aux |grep clam
>amavis 6683 0.0 20.9 1016312 814072 ? Ssl 15:14 0:00 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf
>
># freshclam
>Wed Dec 11 15:52:45 2019 -> ClamAV update process started at Wed Dec 11 15:52:45 2019
>Wed Dec 11 15:52:45 2019 -> ^Your ClamAV installation is OUTDATED!
>Wed Dec 11 15:52:45 2019 -> ^Local version: 0.101.5 Recommended version: 0.102.1
>Wed Dec 11 15:52:45 2019 -> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
>Wed Dec 11 15:52:45 2019 -> main.cld is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
>Wed Dec 11 15:52:45 2019 -> daily.cld is up to date (version: 25660, sigs: 2043646, f-level: 63, builder: raynman)
>Wed Dec 11 15:52:45 2019 -> bytecode.cld is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg)
>
>This happens after a reboot after having tried to get it working without reboot,
>
>What is going wrong here? Should clamd be running after amavis is started?

nothing it wrong here. Just CentOS 7 does not have the newest clamav version
installed. It's not always easy to install newest software on system that is
5 years old and supposed to be supported for another 5 years...

--
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.
M$ Win's are shit, do not use it !

_______________________________________________

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] problem with clamav upgrade [ In reply to ]
On 11/12/2019 16:57, ratatouille via clamav-users wrote:
> Hello!
>
> On a centos7 I did a yum update today and new version of clamav
> was installed.
>
> ps aux |grep clam
> amavis 6683 0.0 20.9 1016312 814072 ? Ssl 15:14 0:00 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf
>
> # freshclam
> Wed Dec 11 15:52:45 2019 -> ClamAV update process started at Wed Dec 11 15:52:45 2019
> Wed Dec 11 15:52:45 2019 -> ^Your ClamAV installation is OUTDATED!
> Wed Dec 11 15:52:45 2019 -> ^Local version: 0.101.5 Recommended version: 0.102.1
> Wed Dec 11 15:52:45 2019 -> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
> Wed Dec 11 15:52:45 2019 -> main.cld is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
> Wed Dec 11 15:52:45 2019 -> daily.cld is up to date (version: 25660, sigs: 2043646, f-level: 63, builder: raynman)
> Wed Dec 11 15:52:45 2019 -> bytecode.cld is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg)
>
> This happens after a reboot after having tried to get it working without reboot,
>
> What is going wrong here? Should clamd be running after amavis is started?
>
>

If you mean "Your ClamAV installation is OUTDATED!", then 0.101 is the
max version CentOS 7 supports out of the box.

They don't do major version upgrades during their product lifetimes.

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] problem with clamav upgrade [ In reply to ]
Hi there,

On Wed, 11 Dec 2019, ratatouille via clamav-users wrote:

> On a centos7 I did a yum update today and new version of clamav
> was installed.
>
> ps aux |grep clam
> amavis 6683 0.0 20.9 1016312 814072 ? Ssl 15:14 0:00 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf
>
> # freshclam
> Wed Dec 11 15:52:45 2019 -> ClamAV update process started at Wed Dec 11 15:52:45 2019
> Wed Dec 11 15:52:45 2019 -> ^Your ClamAV installation is OUTDATED!
> Wed Dec 11 15:52:45 2019 -> ^Local version: 0.101.5 Recommended version: 0.102.1

Did you not just tell me in another thread (failed to write to") that
you compiled ClamAV from source? In that case, why would you want to
allow 'yum update' to install an older version of ClamAV?

> What is going wrong here? Should clamd be running after amavis is started?

I know nothing about Amavis, nor about its possible uses with clamd,
but I am a little surprised that any clamd configuration file should
be called 'amavisd.conf'. That seems to me to be very confusing.

If you intend to use clamd routinely, I would expect it to be started
at boot by one of the boot scripts designed for that purpose. There
are several different approaches to this, you need to find out which
approach is used in your system and make sure that it is working.

--

73,
Ged.

_______________________________________________

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] problem with clamav upgrade [ In reply to ]
Matus UHLAR - fantomas <uhlar@fantomas.sk> schrieb am 11.12.19 um 16:02:59 Uhr:

> >On a centos7 I did a yum update today and new version of clamav
> >was installed.
> >
> >ps aux |grep clam
> >amavis 6683 0.0 20.9 1016312 814072 ? Ssl 15:14 0:00 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf
> >
> ># freshclam
> >Wed Dec 11 15:52:45 2019 -> ClamAV update process started at Wed Dec 11 15:52:45 2019
> >Wed Dec 11 15:52:45 2019 -> ^Your ClamAV installation is OUTDATED!
> >Wed Dec 11 15:52:45 2019 -> ^Local version: 0.101.5 Recommended version: 0.102.1
> >Wed Dec 11 15:52:45 2019 -> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
> >Wed Dec 11 15:52:45 2019 -> main.cld is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
> >Wed Dec 11 15:52:45 2019 -> daily.cld is up to date (version: 25660, sigs: 2043646, f-level: 63, builder: raynman)
> >Wed Dec 11 15:52:45 2019 -> bytecode.cld is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg)
> >
> >This happens after a reboot after having tried to get it working without reboot,
> >
> >What is going wrong here? Should clamd be running after amavis is started?
>
> nothing it wrong here. Just CentOS 7 does not have the newest clamav version
> installed. It's not always easy to install newest software on system that is
> 5 years old and supposed to be supported for another 5 years...

Ok, thank you!

One more question. If amavis starts clamd (does it?), shouldn't I see a clamd-process
when I grep for it beside of amavis ?

Andreas

_______________________________________________

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] problem with clamav upgrade [ In reply to ]
On 11/12/2019 17:24, ratatouille via clamav-users wrote:
> Matus UHLAR - fantomas <uhlar@fantomas.sk> schrieb am 11.12.19 um 16:02:59 Uhr:
>
>>> On a centos7 I did a yum update today and new version of clamav
>>> was installed.
>>>
>>> ps aux |grep clam
>>> amavis 6683 0.0 20.9 1016312 814072 ? Ssl 15:14 0:00 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf
>>>
>>> # freshclam
>>> Wed Dec 11 15:52:45 2019 -> ClamAV update process started at Wed Dec 11 15:52:45 2019
>>> Wed Dec 11 15:52:45 2019 -> ^Your ClamAV installation is OUTDATED!
>>> Wed Dec 11 15:52:45 2019 -> ^Local version: 0.101.5 Recommended version: 0.102.1
>>> Wed Dec 11 15:52:45 2019 -> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
>>> Wed Dec 11 15:52:45 2019 -> main.cld is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
>>> Wed Dec 11 15:52:45 2019 -> daily.cld is up to date (version: 25660, sigs: 2043646, f-level: 63, builder: raynman)
>>> Wed Dec 11 15:52:45 2019 -> bytecode.cld is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg)
>>>
>>> This happens after a reboot after having tried to get it working without reboot,
>>>
>>> What is going wrong here? Should clamd be running after amavis is started?
>> nothing it wrong here. Just CentOS 7 does not have the newest clamav version
>> installed. It's not always easy to install newest software on system that is
>> 5 years old and supposed to be supported for another 5 years...
> Ok, thank you!
>
> One more question. If amavis starts clamd (does it?), shouldn't I see a clamd-process
> when I grep for it beside of amavis ?

From your post:

amavis 6683 0.0 20.9 1016312 814072 ? Ssl 15:14 0:00 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf

That is the very clamd started on your system.

See 'systemctl status clamd@amavisd' (iirc). Or clamd@amavis. I stopped using amavisd a while ago so not 100% sure any more. :)

If you're using Amavisd, then amavisd supplies its own config file to clamd - what you can see in the ps output you posted.

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] problem with clamav upgrade [ In reply to ]
"G.W. Haywood via clamav-users" <clamav-users@lists.clamav.net> schrieb am 11.12.19 um 15:23:43 Uhr:

> > On a centos7 I did a yum update today and new version of clamav
> > was installed.
> >
> > ps aux |grep clam
> > amavis 6683 0.0 20.9 1016312 814072 ? Ssl 15:14 0:00 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf
> >
> > # freshclam
> > Wed Dec 11 15:52:45 2019 -> ClamAV update process started at Wed Dec 11 15:52:45 2019
> > Wed Dec 11 15:52:45 2019 -> ^Your ClamAV installation is OUTDATED!
> > Wed Dec 11 15:52:45 2019 -> ^Local version: 0.101.5 Recommended version: 0.102.1
>
> Did you not just tell me in another thread (failed to write to") that
> you compiled ClamAV from source? In that case, why would you want to
> allow 'yum update' to install an older version of ClamAV?

That was on another server running an a bit outdated openSUSE-OS.

> > What is going wrong here? Should clamd be running after amavis is started?
>
> I know nothing about Amavis, nor about its possible uses with clamd,
> but I am a little surprised that any clamd configuration file should
> be called 'amavisd.conf'. That seems to me to be very confusing.

On Centos7

cat /etc/clamd.d/amavisd.conf

# Use system logger.
LogSyslog yes

# Specify the type of syslog messages - please refer to 'man syslog'
# for facility names.
LogFacility LOG_MAIL

# This option allows you to save a process identifier of the listening
# daemon (main thread).
PidFile /var/run/clamd.amavisd/clamd.pid

# Remove stale socket after unclean shutdown.
# Default: disabled
FixStaleSocket yes

# Run as a selected user (clamd must be started by root).
User amavis

# Path to a local socket file the daemon will listen on.
LocalSocket /var/run/clamd.amavisd/clamd.sock

> If you intend to use clamd routinely, I would expect it to be started
> at boot by one of the boot scripts designed for that purpose. There
> are several different approaches to this, you need to find out which
> approach is used in your system and make sure that it is working.

My understanding is amavisd is looking for clamd.sock

['ClamAV-clamd',
\&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamd.amavisd/clamd.sock"],
qr/\bOK$/m, qr/\bFOUND$/m,
qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ]

# systemctl list-unit-files | grep clam
clamd@.service disabled

# systemctl start clamd@.service
Failed to start clamd@.service: Unit name clamd@.service is missing the instance name.
See system logs and 'systemctl status clamd@.service' for details.

# ll /var/run/clamd.amavisd
-rw-rw-r-- 1 amavis amavis 5 11. Dez 15:14 clamd.pid
srw-rw-rw- 1 amavis amavis 0 11. Dez 15:14 clamd.sock

I am not looking through this clamav-stuff.

Andreas

_______________________________________________

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] problem with clamav upgrade [ In reply to ]
On 11.12.2019 17:45, ratatouille via clamav-users wrote:
> My understanding is amavisd is looking for clamd.sock
> ['ClamAV-clamd',
> \&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamd.amavisd/clamd.sock"],
> qr/\bOK$/m, qr/\bFOUND$/m,
> qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ]
>
> # systemctl list-unit-files | grep clam
> clamd@.service disabled
>
> # systemctl start clamd@.service
> Failed to start clamd@.service: Unit name clamd@.service is missing the instance name.
> See system logs and 'systemctl status clamd@.service' for details.
>

try 'clamd@amavisd' service

_______________________________________________

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] problem with clamav upgrade [ In reply to ]
Reio Remma via clamav-users <clamav-users@lists.clamav.net> schrieb am 11.12.19 um 18:51:37 Uhr:

> On 11.12.2019 17:45, ratatouille via clamav-users wrote:
> > My understanding is amavisd is looking for clamd.sock
> > ['ClamAV-clamd',
> > \&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamd.amavisd/clamd.sock"],
> > qr/\bOK$/m, qr/\bFOUND$/m,
> > qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ]
> >
> > # systemctl list-unit-files | grep clam
> > clamd@.service disabled
> >
> > # systemctl start clamd@.service
> > Failed to start clamd@.service: Unit name clamd@.service is missing the instance name.
> > See system logs and 'systemctl status clamd@.service' for details.
> >
>
> try 'clamd@amavisd' service

Yes, thisone shows clamd is running

# systemctl status clamd@amavisd
? clamd@amavisd.service - clamd scanner (amavisd) daemon
Loaded: loaded (/usr/lib/systemd/system/clamd@.service; disabled; vendor preset: disabled)
Active: active (running) since Mi 2019-12-11 15:14:34 CET; 3h 20min ago
Docs: man:clamd(8)
man:clamd.conf(5)
https://www.clamav.net/documents/
Process: 1271 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/%i.conf (code=exited, status=0/SUCCESS)
Main PID: 6683 (clamd)
CGroup: /system.slice/system-clamd.slice/clamd@amavisd.service
??6683 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf


(code=exited, status=0/SUCCESS) ?

Andreas

_______________________________________________

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] problem with clamav upgrade [ In reply to ]
Hi there,

On Wed, 11 Dec 2019, ratatouille via clamav-users wrote:
> "G.W. Haywood via clamav-users" <clamav-users@lists.clamav.net> schrieb am 11.12.19 um 15:23:43 Uhr:
>
>> Did you not just tell me in another thread (failed to write to") that
>> you compiled ClamAV from source? In that case, why would you want to
>> allow 'yum update' to install an older version of ClamAV?
>
> That was on another server running an a bit outdated openSUSE-OS.

Ah, I see. In that case...

> # Path to a local socket file the daemon will listen on.
> LocalSocket /var/run/clamd.amavisd/clamd.sock

...why not change this to listen instead on a TCP socket, and use the
single (and up to date) clamd instance on your OpenSUSE server to scan
for your other servers? Of course depending on how many there are you
might need more than one machine running a clamd process, but normally
you won't need a clamd running on every machine.

Be aware that when clamd listens to a TCP socket, it provides no way
to prevent connections to the socket from devices which you might not
want to connect to it. You have to do that stuff yourself.

> I am not looking through this clamav-stuff.

I'm afraid I don't understand what you mean by that.

--

73,
Ged.

_______________________________________________

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] problem with clamav upgrade [ In reply to ]
> On 11. Dec 2019, at 21:16, G.W. Haywood via clamav-users <clamav-users@lists.clamav.net> wrote:
>
> ?Hi there,
>
>> On Wed, 11 Dec 2019, ratatouille via clamav-users wrote:
>> "G.W. Haywood via clamav-users" <clamav-users@lists.clamav.net> schrieb am 11.12.19 um 15:23:43 Uhr:
>>
>>> Did you not just tell me in another thread (failed to write to") that
>>> you compiled ClamAV from source? In that case, why would you want to
>>> allow 'yum update' to install an older version of ClamAV?
>>
>> That was on another server running an a bit outdated openSUSE-OS.
>
> Ah, I see. In that case...
>
>> # Path to a local socket file the daemon will listen on.
>> LocalSocket /var/run/clamd.amavisd/clamd.sock
>
> ...why not change this to listen instead on a TCP socket, and use the
> single (and up to date) clamd instance on your OpenSUSE server to scan
> for your other servers? Of course depending on how many there are you
> might need more than one machine running a clamd process, but normally
> you won't need a clamd running on every machine.
>
> Be aware that when clamd listens to a TCP socket, it provides no way
> to prevent connections to the socket from devices which you might not
> want to connect to it. You have to do that stuff yourself.

Unfortunately amavisd only supports scanning via socket.



_______________________________________________

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