Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: ClamAV: users

$ sudo freshclam ERROR: Problem with internal logger.

 

 

ClamAV users RSS feed   Index | Next | Previous | View Threaded


support at obantec

Jun 4, 2006, 2:28 AM

Post #1 of 5 (8343 views)
Permalink
$ sudo freshclam ERROR: Problem with internal logger.

Hi

I have just started seeing this error and have been running clamav for 6 or
more months.
i did upgrade to 88.2 recently and i now see

ERROR: Problem with internal logger.

i have check my freshclam.log permissions although i have not changed the
ownership or permissions.

also been thru google which suggested the above.

Mark
--
Obantec Support
www.obantec.net
0845 458 3121
WebHosting and Domains
Nominet UK Member & IPStag Holder
CentralNic Accredited Reseller

_______________________________________________
http://lurker.clamav.net/list/clamav-users.html


chris at westnet

Jun 4, 2006, 6:50 AM

Post #2 of 5 (7929 views)
Permalink
Re: $ sudo freshclam ERROR: Problem with internal logger. [In reply to]

On Sun, 4 Jun 2006, Obantec Support wrote:

> I have just started seeing this error and have been running clamav for 6 or
> more months.
> i did upgrade to 88.2 recently and i now see
>
> ERROR: Problem with internal logger.

Means another copy of freshclam was already running.


==========================================================
Chris Candreva -- chris[at]westnet.com -- (914) 967-7816
WestNet Internet Services of Westchester
http://www.westnet.com/
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html


oacheson at acheson

Jun 4, 2006, 11:32 AM

Post #3 of 5 (7855 views)
Permalink
Re: $ sudo freshclam ERROR: Problem with internal logger. [In reply to]

On Sun, Jun 04, 2006 at 10:28:24AM +0100, Obantec Support wrote:
> Hi
>
> I have just started seeing this error and have been running clamav for 6 or
> more months.
> i did upgrade to 88.2 recently and i now see
>
> ERROR: Problem with internal logger.
>

I got the same error message starting at about 6:30am this morning (eastern
US). Repeated each time cron ran freshclam until I noticed it this afternoon.
Similarly, no problems in log file with permissions (writeable by
user clamav, as it has been since installation over a year ago).

My solution: I rolled the logs and ran freshclam manually. It wrote
successfully to the new, empty log file. I presume freshclam under cron will
do likewise.

I assume the issue was cosmic rays, or migrating birds or the like.

Ollie



> i have check my freshclam.log permissions although i have not changed the
> ownership or permissions.
>
> also been thru google which suggested the above.
>
> Mark
> --
> Obantec Support
> www.obantec.net
> 0845 458 3121
> WebHosting and Domains
> Nominet UK Member & IPStag Holder
> CentralNic Accredited Reseller
>
> _______________________________________________
> http://lurker.clamav.net/list/clamav-users.html

--
|---------------------------|
| Ollie Acheson |
| Morristown, NJ |
|---------------------------|

_______________________________________________
http://lurker.clamav.net/list/clamav-users.html


oacheson at acheson

Jun 4, 2006, 11:41 AM

Post #4 of 5 (7827 views)
Permalink
Re: $ sudo freshclam ERROR: Problem with internal logger. [In reply to]

On Sun, Jun 04, 2006 at 02:32:04PM -0400, Ollie Acheson wrote:
> On Sun, Jun 04, 2006 at 10:28:24AM +0100, Obantec Support wrote:
> > Hi
> >
> > I have just started seeing this error and have been running clamav for 6 or
> > more months.
> > i did upgrade to 88.2 recently and i now see
> >
> > ERROR: Problem with internal logger.
> >
>
> I got the same error message starting at about 6:30am this morning (eastern
> US). Repeated each time cron ran freshclam until I noticed it this afternoon.
> Similarly, no problems in log file with permissions (writeable by
> user clamav, as it has been since installation over a year ago).
>
> My solution: I rolled the logs and ran freshclam manually. It wrote
> successfully to the new, empty log file. I presume freshclam under cron will
> do likewise.
>
> I assume the issue was cosmic rays, or migrating birds or the like.
>
> Ollie
>

As the other poster noted, this related to a hung freshclam process which
dated from 6:30 this morning. The log from that time only showed the main.cvd
line, but not the daily.cvd one.

Ollie

>
>
> > i have check my freshclam.log permissions although i have not changed the
> > ownership or permissions.
> >
> > also been thru google which suggested the above.
> >
> > Mark
> > --
> > Obantec Support
> > www.obantec.net
> > 0845 458 3121
> > WebHosting and Domains
> > Nominet UK Member & IPStag Holder
> > CentralNic Accredited Reseller
> >
> > _______________________________________________
> > http://lurker.clamav.net/list/clamav-users.html
>
> --
> |---------------------------|
> | Ollie Acheson |
> | Morristown, NJ |
> |---------------------------|
>
> _______________________________________________
> http://lurker.clamav.net/list/clamav-users.html

--
|---------------------------|
| Ollie Acheson |
| Morristown, NJ |
|---------------------------|

_______________________________________________
http://lurker.clamav.net/list/clamav-users.html


support at obantec

Jun 4, 2006, 11:47 AM

Post #5 of 5 (7811 views)
Permalink
Re: Re: $ sudo freshclam ERROR: Problem with internallogger. [In reply to]

----- Original Message -----
From: "Ollie Acheson" <oacheson[at]acheson.org>
To: "ClamAV users ML" <clamav-users[at]lists.clamav.net>
Sent: Sunday, June 04, 2006 7:32 PM
Subject: [Clamav-users] Re: $ sudo freshclam ERROR: Problem with
internallogger.


> On Sun, Jun 04, 2006 at 10:28:24AM +0100, Obantec Support wrote:
> > Hi
> >
> > I have just started seeing this error and have been running clamav for 6
or
> > more months.
> > i did upgrade to 88.2 recently and i now see
> >
> > ERROR: Problem with internal logger.
> >
>
> I got the same error message starting at about 6:30am this morning
(eastern
> US). Repeated each time cron ran freshclam until I noticed it this
afternoon.
> Similarly, no problems in log file with permissions (writeable by
> user clamav, as it has been since installation over a year ago).
>
> My solution: I rolled the logs and ran freshclam manually. It wrote
> successfully to the new, empty log file. I presume freshclam under cron
will
> do likewise.
>
> I assume the issue was cosmic rays, or migrating birds or the like.
>
> Ollie
>
>
>
> > i have check my freshclam.log permissions although i have not changed
the
> > ownership or permissions.
> >
> > also been thru google which suggested the above.
> >
> > Mark
> > --
> > Obantec Support
> > www.obantec.net
> > 0845 458 3121
> > WebHosting and Domains
> > Nominet UK Member & IPStag Holder
> > CentralNic Accredited Reseller
> >
> > _______________________________________________
> > http://lurker.clamav.net/list/clamav-users.html
>
> --
> |---------------------------|
> | Ollie Acheson |
> | Morristown, NJ |
> |---------------------------|
>
> _______________________________________________
> http://lurker.clamav.net/list/clamav-users.html
>
>
>
> --

Hi

my freshclam.log is still being updated so i don't know what's going on but
will let cron run as normal and see tomorrows log. (last update 19:12 BST)

ClamAV update process started at Sun Jun 4 19:12:59 2006
main.cvd is up to date (version: 38, sigs: 51206, f-level: 7, builder:
tkojm)
daily.cvd is up to date (version: 1512, sigs: 7208, f-level: 8, builder:
arnaud)

Mark

_______________________________________________
http://lurker.clamav.net/list/clamav-users.html

ClamAV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.