Next COS version is 6.2. I don't think there will be an upgrade of 5.2 to e.g. 5.3 this late in the game. There is an exception: if the current antispam engine in future were found to have a security hole or bug of some kind, an update (or a patched version) would be releasted in the automatice software update mechanism that provides bug and security fixes inbetween version upgrades.

Peter

Thanks Peter. I'll ignore it for now.
When you say the next COS version will contain the latest version do you mean CleaOS 6.x or will there be another update for ClearOS 5.2 - if so, do you know when and will this be an automatic update or do I have to do this manually?

Best wishes,

Andy

No cause for worry. The message is harmless. All it means is that there is a newer program version available. But the previous one in COS is perfectly good and works without issue. The latest version will be included in the next COS version when it is released.

Peter

Hi,

I see this thread is a year old now - we are using ClearOS 5.2 and currently I am seeing the same error on our systems.

LibClamAv warning

Stopping clamav: [ OK ]
Starting clamav: LibClamAV Warning: ***********************************************************
LibClamAV Warning: *** This version of the ClamAV engine is outdated. ***
LibClamAV Warning: *** DON'T PANIC! Read http://www.clamav.net/support/faq ***
LibClamAV Warning: ***********************************************************

Is there a solution to this - we are paying for AV updates from the ClearSDN services but this error is making me concerned that we will have issues with inbound email unless we disable the filtering.

Many thanks,

Andy

That is odd. I have never had issues on my system. Are both the broken systems COS 5.1? And are they plain vanila?

Peter

I have 2 systems right now, and have had this same problem in the past that once the update started being needed, the spam filter has frozen and they stop passing email unless filtering is disabled. We need a way to keep this up to date, or we need a way to make sure things keep working right regardless. It has been random to some extend, it doesn't happen the day of, and I have other systems that keep working fine.

Dude, don't break it....I would be more apt to be patient and wait for the ClearOS team to include any version upgrade that would include updates to any dependencies as well. It's as Peter said, it works quite well enough for now and the definitions get updated regularly anyway.

Hi Tony & Peter,

Thanks for your responses.
The ClamAV update I refer too, is mentioned in the link "http://www.clamav.net/support/faq"; and I suspect that Tony is right that it will be available with the next ClearOS update.

I just wondered if anyone else noticed this and found a way to update it manually now, because the steps for 'CentOS' are not working for me and the 'Red Hat' steps I didn't try.
I would rather not compile it myself when it will be made available in the near future by the ClearOS team.

Greetings,

John

Yes. Engine updates (I quote):

# service clamd restart

Stopping clamav:                                           [  OK  ]

Starting clamav: LibClamAV Warning: ***********************************************************

LibClamAV Warning: ***  This version of the ClamAV engine is outdated.     ***

LibClamAV Warning: *** DON'T PANIC! Read http://www.clamav.net/support/faq ***

LibClamAV Warning: ***********************************************************

Peter

Peter, John was talking about updates..

I discovered that there is some sort of ClamAV update

John,

Don't worry about it. The next update/upgrade of COS will likely include the update. Meanwhile, ClamAV will do its job without issues.

Peter

@Tony,
John is referring to the message which pops up with a "service clamd restart". Your messages come from periodic signature update and go into /var/log/messages. If you restart clamd you'll see the same.

Happens automatically on my system...

Note the later version on the later date as extracted from my logs...

ar 14 04:29:31 atomii-3 freshclam[2977]: Received signal: wake up  

Mar 14 04:29:31 atomii-3 freshclam[2977]: ClamAV update process started at Sun Mar 14 04:29:31 2010  

Mar 14 04:29:31 atomii-3 freshclam[2977]: main.cld is up to date (version: 52, sigs: 704727, f-level: 44, builder: sven)  

Mar 14 04:29:31 atomii-3 freshclam[2977]: daily.cld is up to date (version: 10572, sigs: 24175, f-level: 44, builder: guitar)  

Mar 14 04:29:31 atomii-3 freshclam[2977]: --------------------------------------  

Mar 14 04:31:49 via-epia clamd[3097]: SelfCheck: Database status OK. 

Apr 11 09:49:27 georgina-3 freshclam[3580]: Received signal: wake up  

Apr 11 09:49:27 georgina-3 freshclam[3580]: ClamAV update process started at Sun Apr 11 09:49:27 2010  

Apr 11 09:49:28 georgina-3 freshclam[3580]: DON'T PANIC! Read http://www.clamav.net/support/faq  

Apr 11 09:49:28 georgina-3 freshclam[3580]: main.cld is up to date (version: 52, sigs: 704727, f-level: 44, builder: sven)  

Apr 11 09:49:28 georgina-3 freshclam[3580]: daily.cld is up to date (version: 10725, sigs: 50658, f-level: 51, builder: mcichosz)  

Apr 11 09:49:28 georgina-3 freshclam[3580]: --------------------------------------  

Apr 11 09:51:07 georgina-3 clamd[3548]: SelfCheck: Database status OK.