I have no script OnUpdateExecute script and got the lock problem
today, right after a completly buggy freshclam run. Watch the logs:
Received signal: wake up
ClamAV update process started at Tue Feb 27 07:31:00 2007
main.cvd is up to date (version: 42, sigs: 83951, f-level: 10, builder:
t
Dennis Peterson wrote:
Tomasz Kojm wrote:
On Mon, 26 Feb 2007 23:41:39 -0800
Dennis Peterson <[EMAIL PROTECTED]> wrote:
Wolf, Brian wrote:
Brian wrote:
both freshclam and clamd 0.90 have been dying with
"Can't lock database directory" every time a new version of
signatures comes out.
I
Tomasz Kojm wrote:
On Mon, 26 Feb 2007 23:41:39 -0800
Dennis Peterson <[EMAIL PROTECTED]> wrote:
Wolf, Brian wrote:
Brian wrote:
both freshclam and clamd 0.90 have been dying with
"Can't lock database directory" every time a new
version of signatures comes out.
It looks like my problem
On Mon, 26 Feb 2007 23:41:39 -0800
Dennis Peterson <[EMAIL PROTECTED]> wrote:
> Wolf, Brian wrote:
> > Brian wrote:
> >
> >> both freshclam and clamd 0.90 have been dying with
> >> "Can't lock database directory" every time a new
> >> version of signatures comes out.
> >
> >
> > It looks lik
Wolf, Brian wrote:
Brian wrote:
both freshclam and clamd 0.90 have been dying with
"Can't lock database directory" every time a new
version of signatures comes out.
It looks like my problem was caused by having freshclam run
a script after an update using the OnUpdateExecute line in
fre
Brian wrote:
> both freshclam and clamd 0.90 have been dying with
> "Can't lock database directory" every time a new
> version of signatures comes out.
It looks like my problem was caused by having freshclam run
a script after an update using the OnUpdateExecute line in
freshclam.conf. The
> I haven't seen a stale .dbLock file, but both freshclam and clamd 0.90
have been dying with "Can't lock database > directory" every
time a new version of signatures comes out. This is on a RedHat
Advanced Server 4 system. I have > pasted portions of the logs
below. Freshclam runs
On Thu, 22 Feb 2007 11:52:08 -0500, aCaB <[EMAIL PROTECTED]> wrote:
Paul Griffith wrote:
Greetings,
Has anyone encountered the following problem:
Somehow there was a stale .dbLock file in the database directory, and
the log file was full of
'ERROR: Can't lock database directory: /cs/local/sh
Paul Griffith wrote:
> Has anyone encountered the following problem:
>
> Somehow there was a stale .dbLock file in the database directory, and
the
> log file was full of
> 'ERROR: Can't lock database directory: /cs/local/share/clamav' I did a
strace and saw the freashclam was trying to create a
Paul Griffith wrote:
> Greetings,
>
> Has anyone encountered the following problem:
>
> Somehow there was a stale .dbLock file in the database directory, and
> the log file was full of
> 'ERROR: Can't lock database directory: /cs/local/share/clamav'
> I did a strace and saw the freashclam was tr
Greetings,
Has anyone encountered the following problem:
Somehow there was a stale .dbLock file in the database directory, and the
log file was full of
'ERROR: Can't lock database directory: /cs/local/share/clamav'
I did a strace and saw the freashclam was trying to create a new .dbLock
fil
11 matches
Mail list logo
