Le Fri 2/02/2007, Stephen Gran disait
> This one time, at band camp, Erwan David said:
> > At freshclam I get the following error message :
> > Starting ClamAV virus database updater: freshclamERROR: Problem with
> > internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).
> > failed!
> >
> > freshclam runs, but no login happens.
> >
> > If I run freshclam by hand I get the following trace :
> >
> > open("/var/log/clamav/freshclam.log", O_WRONLY|O_APPEND|O_CREAT, 0666) = 3
> > fstat64(3, {st_mode=S_IFREG|0640, st_size=19490, ...}) = 0
> > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> > 0xb7f31000
> > fstat64(3, {st_mode=S_IFREG|0640, st_size=19490, ...}) = 0
> > _llseek(3, 19490, [19490], SEEK_SET) = 0
> > umask(022) = 037
> > fcntl64(3, F_SETLK, {type=F_WRLCK, whence=SEEK_SET, start=0, len=0}) = -1
> > EAGAIN (Resource temporarily unavailable)
> > write(2, "ERROR: Problem with internal log"..., 85) = 85
> > exit_group(62) = ?
>
> This is freshclam trying to lock the logfile and failing. It sounds to
> me like you may have another instance of freshclam already running.
> Kill off the old one and try again.
Thanks, it works. Now the question is why the upgrade process did not
kill the former instance. This appeared with upgrade today.
--
Erwan David
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
