On Tue, 10 Apr 2007, Dennis Peterson wrote:
; Has the ClamAV backbone died?
;
; Trying host db.us.clamav.net (129.64.99.170)...
; nonblock_connect: connect timing out (30 secs)
; Can't connect to port 80 of host db.us.clamav.net (IP: 129.64.99.170)
; Trying host db.us.clamav.net (199.239.233.95).
Hello Dennis,
> Has the ClamAV backbone died?
no, only some mirrors[*]. Most of our users are still running 0.8x and that
causes big spikes of traffic when we release a new main.cvd .
[snip]
> Trying host db.us.clamav.net (66.111.55.10)...
> nonblock_connect: connect timing out (30 secs)
> Can'
Hi
Has anybody else noticed this.
When running clamd with the ScanArchive config option set to yes, after a
couple of minutes of running cpu usage will look like this:
last pid: 2470; load averages: 6.43, 4.06, 2.71
12:16:16
77
Hello,
this night my clamd-process terminated with an error. The reason was
that freshclam took too long to do its update, so that clamd could not
lock the database. So clamd exited. But this behaviour is very fatal
because the mail system (postfix with amavis) relys on clamd, so if it
is down, th
Same here. :-((
This behavior is terrible!
jacusy wrote:
> Hello,
>
> this night my clamd-process terminated with an error. The reason was
> that freshclam took too long to do its update, so that clamd could not
> lock the database. So clamd exited. But this behaviour is very fatal
> becau
Hello :-)
Same here since 12:45h MESZ.
After some tests this helped me to get all working again:
sudo killall freshclam
sudo rcclamd restart
sudo rc restart
And do NOT forget to comment you freshclam Updtes in cron out.
Hope this quick hack helps...
ISC Handler Marteen told me just a few mi
Alexander Grüner schrieb:
> Hello :-)
>
> Same here since 12:45h MESZ.
>
> After some tests this helped me to get all working again:
>
> sudo killall freshclam
> sudo rcclamd restart
> sudo rc restart
>
> And do NOT forget to comment you freshclam Updtes in cron out.
>
> Hope this quick hack helps.
jacusy wrote:
> Hello,
>
> this night my clamd-process terminated with an error. The reason was
> that freshclam took too long to do its update, so that clamd could not
> lock the database. So clamd exited. But this behaviour is very fatal
> because the mail system (postfix with amavis) relys on c
jacusy wrote:
>> As more users upgrade from 0.8 to 0.9, this problem will disappear with
>> future updates. Version 0.9 only transfers the difference between CVDs
>> instead of the files in full."
>>
> Does this mean that every time they have a new main.cvd, my clamd will
> stop working??? I ca
Hi all
I'm new on the list, is this is a FAQ please tell me so. I'm unsure if
my problem is related to the other one that today is discussed on the
list.
I have several clamav installations. I use it with Postfix on CentOS
(very similar to Red Hat). I use the clamav RPM packages available o
Experienced it a few times after 0.90 was released (end february / first
half march)... Nothing changed in 0.90.1.
The "nice" thing is, freshclam still kept reporting that updates were
fine, after clamd went dead... Luckily, clam was configured as secondary
scanner in amavis, so mail delivery wa
Hi
clamd won't start running
+++ Started at Wed Apr 11 14:03:38 2007
clamd daemon 0.90.1 (OS: linux-gnu, ARCH: i386, CPU: i686)
Log file size limited to 2097152 bytes.
Reading databases from /var/lib/clamav
ERROR: Broken or not a CVD file
it has been since 90.1 was introduced.
Mark
--
Obantec S
I also saw this on two different servers yesterday...about 13 hours ago
actually...didn't catch it until this morningwould really like to
know whats going on.Had this happen two days ago on a different
server as well...
Luigi Iotti wrote:
> Hi all
>
> I'm new on the list, is this is a F
On 4/11/07, Shane Wise <[EMAIL PROTECTED]> wrote:
> I also saw this on two different servers yesterday...about 13 hours ago
> actually...didn't catch it until this morningwould really like to
> know whats going on.Had this happen two days ago on a different
> server as well...
Same here, t
us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
__ Informacisn de NOD32, revisisn 2180 (20070411) __
Este mensaje ha sido analizado con NOD32 antivirus system
http://www.
Hello,
today I had a very serious problem with clam. It crashed while
checking its database - on both of my mailservers! So no mail
was delivered for quite some time.
This is from freshclamd.log:
Received signal: wake up
ClamAV update process started at Wed Apr 11 04:15:54 2007
Connecting via st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well,
Deleting the database directory and restarting freshclam to get the
databases again seems to have fixed the problem on both systems.
This problem may be related to getting incremental updates and not
being able to update the .CVD database prop
On 4/11/07, Brian Morrison <[EMAIL PROTECTED]> wrote:
> I'd say that it is more dangerous to stop mail delivery due to failed
> virus scanning than it is not to scan mail while clamd is unresponsive.
But then the potential for virus infected email to get through is
raised. While I realize that en
On 4/11/07, James Kosin <[EMAIL PROTECTED]> wrote:
> Well,
>
> Deleting the database directory and restarting freshclam to get the
> databases again seems to have fixed the problem on both systems.
>
> This problem may be related to getting incremental updates and not
> being able to update the .CV
>
> As more users upgrade from 0.8 to 0.9, this problem will disappear with
> future updates. Version 0.9 only transfers the difference between CVDs
> instead of the files in full."
>
Which isn't going to happen, at least for me, until 0.9 runs on mac os x
10.3.9.
Right now, it wont compile.
ing and Domains
> Nominet UK Member & IPStag Holder
> CentralNic Accredited Reseller
> ___
> Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
> http://lurker.clamav.net/list/clama
Вы писали 11 квітня 2007 р., 16:26:24:
OS> Hi
OS> clamd won't start running
OS> +++ Started at Wed Apr 11 14:03:38 2007
OS> clamd daemon 0.90.1 (OS: linux-gnu, ARCH: i386, CPU: i686)
OS> Log file size limited to 2097152 bytes.
OS> Reading databases from /var/lib/clamav
OS> ERROR: Broken or not a
Also, if I leave ScanArchive yes and set MaxThreads 1
then it seems to run Ok. Only problem then is that the exim processes
build up waiting for service.
Is there any possibility that the code used by whatever ScanArchive
enables is not thread safe?
> Hi
>
> Has anybody else noticed this.
>
> Whe
Hi,
We had similar problems:
Apr 10 18:50:07 jaguar.misty.com clamd[10009]: [ID 702911 local6.info]
SelfCheck: Database status OK.
Apr 10 19:20:13 jaguar.misty.com clamd[10009]: [ID 702911 local6.info]
SelfCheck: Database status OK.
Apr 10 19:50:41 jaguar.misty.com clamd[10009]: [ID 702911 loca
>
> OS> +++ Started at Wed Apr 11 14:03:38 2007
> OS> clamd daemon 0.90.1 (OS: linux-gnu, ARCH: i386, CPU: i686)
> OS> Log file size limited to 2097152 bytes.
> OS> Reading databases from /var/lib/clamav
> OS> ERROR: Broken or not a CVD file
I had this on 4 different servers that I support.
/va
I am amazed at the number of people here that apparently not using
SOMETHING to monitor clamd. Esp. when the developers include a nice
script to check and restart clamd.
I run three different mail servers and quickly found clamdmon and just a
bit of PERL programming created a means of being notif
At 05:46 AM 4/11/2007, jacusy wrote:
>Hello,
>
>this night my clamd-process terminated with an error. The reason was
>that freshclam took too long to do its update, so that clamd could not
>lock the database. So clamd exited. But this behaviour is very fatal
>because the mail system (postfix with a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luigi Iotti wrote:
> Hi all
>
> I'm new on the list, is this is a FAQ please tell me so. I'm unsure if
> my problem is related to the other one that today is discussed on the
> list.
>
> I have several clamav installations. I use it with Postfix on
[EMAIL PROTECTED] wrote:
> Hi
>
> Has anybody else noticed this.
>
> When running clamd with the ScanArchive config option set to yes, after a
> couple of minutes of running cpu usage will look like this:
>
> last pid: 2470; load averages: 6.43, 4.06, 2.71
>
> Same here, three servers. Had this happen a few weeks ago on one of
> those servers, but I thought it was an isolated incident..
Well, on the opposite end of the spectrum, all four of my OpenBSD
servers running 0.90.1 got the update just fine, and none of them
died. I saw a few complaints in
On 4/11/07, Lyle Giese <[EMAIL PROTECTED]> wrote:
> I am amazed at the number of people here that apparently not using
> SOMETHING to monitor clamd. Esp. when the developers include a nice
> script to check and restart clamd.
I'm not sure it was a matter of not having clamd monitored, I think it
- Original Message -
From: <[EMAIL PROTECTED]>
To: "ClamAV users ML"
Sent: Wednesday, April 11, 2007 3:09 PM
Subject: Re: [Clamav-users] ERROR: Broken or not a CVD file
>
>
>>
>> OS> +++ Started at Wed Apr 11 14:03:38 2007
>> OS> clamd daemon 0.90.1 (OS: linux-gnu, ARCH: i386, CPU: i
Hi!
In my case just restarting clamd wouldn't have worked, because clam
didn't start because of a broken database (or a least one file in
the database directory which doesn't belong there). And because of
that clamscan as backup didn't worked either.
Tom
> -Original Message-
> From: [EMA
jacusy wrote:
> Alexander Grüner schrieb:
>> Hello :-)
>>
>> Same here since 12:45h MESZ.
>>
>> After some tests this helped me to get all working again:
>>
>> sudo killall freshclam
>> sudo rcclamd restart
>> sudo rc restart
>>
>> And do NOT forget to comment you freshclam Updtes in cron out.
>>
>
On Wed, 11 Apr 2007, Brian Morrison wrote:
> I'd say that it is more dangerous to stop mail delivery due to failed
> virus scanning than it is not to scan mail while clamd is unresponsive.
This all depends how much a cleanup of your entire network is going to cost.
==
Luca Gibelli wrote:
> Hello Dennis,
>
>> Has the ClamAV backbone died?
>
> no, only some mirrors[*]. Most of our users are still running 0.8x and that
> causes big spikes of traffic when we release a new main.cvd .
>
> [snip]
>> Trying host db.us.clamav.net (66.111.55.10)...
>> nonblock_connect:
Dennis Peterson wrote:
>
> You need to have better monitoring and notification, and a mail system
> that delivers mail even if there is a fatal error in the AV tool. This
> is hardly a ClamAV problem.
Depends on what your goals are.
For me, a reliable email system does not just mean "mail get
On 4/11/07, John Rudd <[EMAIL PROTECTED]> wrote:
> Depends on what your goals are.
>
> For me, a reliable email system does not just mean "mail gets
> delivered". It also means that "we reliably reject detectable viruses".
> If we're letting viruses through because our pants are down (because
>
Jason Frisvold wrote:
> On 4/11/07, John Rudd <[EMAIL PROTECTED]> wrote:
>> Depends on what your goals are.
>>
>> For me, a reliable email system does not just mean "mail gets
>> delivered". It also means that "we reliably reject detectable viruses".
>> If we're letting viruses through because o
John Rudd wrote:
> Dennis Peterson wrote:
>
>> You need to have better monitoring and notification, and a mail system
>> that delivers mail even if there is a fatal error in the AV tool. This
>> is hardly a ClamAV problem.
>
> Depends on what your goals are.
>
> For me, a reliable email system
I can verify this worked for me as well. Wipe the database, let
freshclam update again, restart the clamd process and everything was
running smooth again.
Thanks,
Michael
James Kosin wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Well,
>
> Deleting the database directory and res
> I corrected this problem on my servers by removing the MSRBL databases
> from the system. CPU usage immediately dropped to normal values.
>
> dp
> ___
Thanks. But I don't beleive I make use of MSRBL. Don't see anything like
that in the clamd.conf file
Noel Jones schrieb:
> Make sure your amavisd.conf defines clamscan as a secondary
> scanner. If clamd is unavailable then amavsid-new will continue to
> process mail using clamscan to check for viruses. When using
> clamscan, system load will increase and throughput will decrease, but
> mail
[EMAIL PROTECTED] wrote:
>> I corrected this problem on my servers by removing the MSRBL databases
>> from the system. CPU usage immediately dropped to normal values.
>>
>> dp
>> ___
>
> Thanks. But I don't beleive I make use of MSRBL. Don't see anything
At 10:42 AM 4/11/2007, jacusy wrote:
> > Yes, clamd and the whole clamav structure should be more resistant to
> > failure. Your choices are to either work with it as is, or wait
> > until clamav is more mature.
> >
>It should not be too hard to rewrite freshclam so it downloads the
>update to a t
Hello jacusy,
> this night my clamd-process terminated with an error. The reason was
> that freshclam took too long to do its update, so that clamd could not
> lock the database. So clamd exited. But this behaviour is very fatal
> because the mail system (postfix with amavis) relys on clamd, so i
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of
> [EMAIL PROTECTED]
> > OS> +++ Started at Wed Apr 11 14:03:38 2007
> > OS> clamd daemon 0.90.1 (OS: linux-gnu, ARCH: i386, CPU: i686)
> > OS> Log file size limited to 2097152 bytes.
> > OS> Reading databases from /var/lib/clamav
> >
>From: [EMAIL PROTECTED] on behalf of Luca Gibelli
>Hello jacusy,
>> this night my clamd-process terminated with an error. The reason was
>> that freshclam took too long to do its update, so that clamd could not
>> lock the database. So clamd exited. But this behaviour is very fatal
>> because the
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Michael Brown
> Sent: Wednesday, April 11, 2007 5:30 PM
> To: ClamAV users ML
> I can verify this worked for me as well. Wipe the database, let
> freshclam update again, restart the clamd process and everything was
> running smooth ag
McDonald, Dan wrote:
>> From: [EMAIL PROTECTED] on behalf of Luca Gibelli
>> Hello jacusy,
>
>>> this night my clamd-process terminated with an error. The reason was
>>> that freshclam took too long to do its update, so that clamd could not
>>> lock the database. So clamd exited. But this behaviou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 11, 2007 at 02:24:52PM -0400, Jim Maul wrote:
>However, it is illogical that clamd would die completely due to issues
>with a recently downloaded definition file. Why can it not just roll
>back to the old, previously working, definition
> I found this file too when I was investigating the problem I talk about in
> my post "Clamav suddenly died on several boxes". I found the the '*.cvd'
> file is created by a daily cron script, /etc/cron.daily/freshclam, which
> issues the command
> /bin/touch -a /var/lib/clamav/*.cvd
Thanks. I a
Ok same thing occured now again. What to do now to solve this problem??
The main.inc seems to be up to date, but the daily.inc should be
updated And this update busts my clamd-process. And if I start it
now, i guess it will be busted one hour later again.
(The problem here is not a corrupted
Last for today: I guess the german update server is down / overloaded. I
changed to austrian, and freshclam worked in seconds.
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi @ll,
since yesterday i have problems with update mirror
db.de.clamav.net is this a known problem, should i change the mirror?
some grep from mail log
pr 11 23:53:40 postmailer freshclam[28032]: Trying host db.de.clamav.net
(194.77.146.139)...
Apr
Robert Schetterer schrieb:
> Hi @ll,
> since yesterday i have problems with update mirror
> db.de.clamav.net is this a known problem, should i change the mirror?
Form me db.at.clamav.net worked fine, and .de. did not at all.
___
Help us build a comprehens
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jacusy schrieb:
> Robert Schetterer schrieb:
>> Hi @ll,
>> since yesterday i have problems with update mirror
>> db.de.clamav.net is this a known problem, should i change the mirror?
> Form me db.at.clamav.net worked fine, and .de. did not at all.
> __
Dennis Peterson wrote:
> John Rudd wrote:
>> Dennis Peterson wrote:
>>
>>> You need to have better monitoring and notification, and a mail system
>>> that delivers mail even if there is a fatal error in the AV tool. This
>>> is hardly a ClamAV problem.
>> Depends on what your goals are.
>>
>> For
Hi, I just did a yum update clamav for my server, and it went OK during
the update, but in attepting to start the service, I see errors which
appear to be somewhat false in that the /etc/clamd.conf file is present,
and has the proper permissions (I checked them against my
non-broken/non-updated
Please help me any one for my problem
Actually i have problem when i was trying to upgrade clamav from 0.887 to
0.90 version
Following is my setup
1, Solaris Sparc server Enterprise Edition,
2. O/S Solaris 8 with complete patches,
3. Amavisd, spamassin, Clamav and postfix,
As per the inst
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Todd Lyons
> Sent: Wednesday, April 11, 2007 8:52 PM
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Wed, Apr 11, 2007 at 02:24:52PM -0400, Jim Maul wrote:
>
> >However, it is illogical that clamd would die completely due to
Luigi Iotti wrote:
>>
>> Notification is a part of the solution IMHO. If clamd recognizes that
>> it's not able to load the new ones because the update process is still
>> occurring, then it should continue running *AND* notify the sysadmin
>> that it's running in what should be considered a degr
62 matches
Mail list logo
