From clamav-users-bounces@lists.clamav.net Mon Apr 7 14:46:28 2008 Return-Path: X-Original-To: list@tad.clamav.net Delivered-To: list@tad.clamav.net X-Virus-Scanned: Debian amavisd-new at tad.clamav.net Received: from tad.clamav.net ([127.0.0.1]) by localhost (tad.clamav.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0HdNHRB7a7De; Mon, 7 Apr 2008 14:46:28 +0200 (CEST) Received: from tad.clamav.net (localhost.localdomain [127.0.0.1]) by tad.clamav.net (Postfix) with ESMTP id 819D216C081; Mon, 7 Apr 2008 14:46:23 +0200 (CEST) X-Original-To: clamav-users@tad.clamav.net Delivered-To: clamav-users@tad.clamav.net X-Virus-Scanned: Debian amavisd-new at tad.clamav.net Received: from tad.clamav.net ([127.0.0.1]) by localhost (tad.clamav.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mEv7dC0jOdYx for ; Mon, 7 Apr 2008 14:46:19 +0200 (CEST) Received: from westnet.com (westnet.com [216.187.52.2]) by tad.clamav.net (Postfix) with ESMTP id 9D7B116C068 for ; Mon, 7 Apr 2008 14:46:19 +0200 (CEST) Received: from westnet.com (localhost [127.0.0.1]) by westnet.com (8.14.0/8.14.0) with ESMTP id m37CkIqc022480 for ; Mon, 7 Apr 2008 08:46:18 -0400 (EDT) Date: Mon, 7 Apr 2008 08:46:18 -0400 (EDT) From: "Christopher X. Candreva" To: ClamAV users ML In-Reply-To: <47F9EE29.9080005@phoenixsoftware.de> Message-ID: References: <47F9EE29.9080005@phoenixsoftware.de> MIME-Version: 1.0 Subject: Re: [Clamav-users] all my ClamAV daemons died last night X-BeenThere: clamav-users@lists.clamav.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: ClamAV users ML List-Id: ClamAV users ML List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: clamav-users-bounces@lists.clamav.net Errors-To: clamav-users-bounces@lists.clamav.net On Mon, 7 Apr 2008, Tilman Schmidt wrote: > I have ClamAV running on several Linux mailservers. All of them stopped > working last night with similar symptoms: In terms of the freshlcam failing, I had the same problem last night. However, I run freshclam on a separate machine from my mail servers. After a successfull update it rsyncs' the databases to my mail servers, so none of my clamd processes noticed the problem. > Simple question: why did that happen? IMHO a failure to update the > signatures, even if it persists for several hours, should not prevent > the continued use of the scan service with the signatures it already Sounds like a bug to me, as freshclam is supposed to prevent this from happening. However, you probably also want a script that monitors you clamd/clamav-milter (or whatever else you use) processes to make sure they keep running, and restart them in case one dies. ========================================================== Chris Candreva -- chris@westnet.com -- (914) 948-3162 WestNet Internet Services of Westchester http://www.westnet.com/ _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html