Hi, as mentioned previously we have a number of servers where the freshclam
run is failing with result code 137. I just wanted to check if anyone has
seen this and was it a lack of memory causing the failure? We're
interpreting this as a kill -9 from the OS (there is no other facility on
these boxe
We've updated the cron script to capture the result code and finding that
where we are getting the failures, it's consistently 137. I would guess
this is an OOM situation, but does anyone know if there are other reasons
we might be getting a 137 from a freshclam run?
Thanks!
David
On Wed, Jun 21
I've tried to duplicate this a few time since we started seeing it on a
test instance, but no luck. But we have lots of instances each day in
production that are having an error. I've just proposed changing the cron
script to capture the result code to log it, as it's not one of the
documented code
Yes, there were no new temp dirs left after the successful run. I'm
wondering if it's a time of day network issue, or perhaps a mirror? I've
seen some complaints about a mirror IP that is also in our logs. Don't know.
David
On Tue, Jun 20, 2017 at 6:25 PM, Steven Morgan
wrote:
> David,
>
> Than
David,
Thanks, so when you say freshclam "completed successfully" you mean there
were no temp files left?
Steve
On Tue, Jun 20, 2017 at 11:21 AM, David Pullman
wrote:
> Steve,
>
> Yes, we run freshclam and then clamscan once each day at 00:03 UTC. There
> were many days of tmp directories. We
Steve,
Yes, we run freshclam and then clamscan once each day at 00:03 UTC. There
were many days of tmp directories. We ran the freshclam utility by hand
yesterday, on the instance the logs are from, at about 22:00 UTC, and it
completed the download. The subsequent update at 00:03 this morning
comp
David,
So freshclam runs every day at ~00:03:00, and to confirm, the temp
directories/files are left for each of these runs?
Which version of ClamAV are you using?
Steve
On Tue, Jun 20, 2017 at 7:51 AM, David Pullman
wrote:
> Hi Steve,
>
> I've gathered some logs from one of the servers that
Hi Steve,
I've gathered some logs from one of the servers that had a bunch of the
clamor-nn.tmp directories over a number of days. I've aggregated
seven days of them below (we rotate the log daily). We run freshclam from
cron each day.
Please let me know if there's any suggestion on how I
Hi,
Any temporary files left by "normal" ClamAV processing is considered to be
a bug. Temporary files may be left if a ClamAV component terminates
ungracefully. Do you have any other logs or know of any other events from
June 3 that may provide additional info about these files left in the temp
di
Hi,
We're seeing cases on some servers where tmp directories are possibly being
left behind in /var/lib/clamav. The following is one example, there are
some where more than one tmp dir is occurring.
Is this a sign of a failure to clean up after a download? Is there
something I can check in logs o
10 matches
Mail list logo
