Re: privoxy crash

7 <website_has_email@xxxxxxxxxxxxxxxxxxxx> wrote:
Kevin the Drummer wrote:

What do you think might cause the following gibberish from privoxy?

::::::::::::::
temp/privoxy-trouble
::::::::::::::
[root@joseph-privoxy #33] *** glibc detected *** /usr/sbin/privoxy:
[malloc(): memory corruption: 0xb7f3e008 ***

May be a memory problem, or a temporary memory problem,
or if you have not checked the logs, the logs might have grown
to tens of megabytes or more over the years.
Look in the privoxy log directory.
If the log is too big, just rename it and privoxy will grow another one.

Actually, I rotate my logs weekly and expire them monthly.

Thanks for the ideas!

--
PLEASE post a SUMMARY of the answer(s) to your question(s)!
Unless otherwise noted, the statements herein reflect my personal
opinions and not those of any organization with which I may be affiliated.
.

Relevant Pages

  • Re: Array, foreach problem
    ... (I've seen flat text logs that grew by as much as +1GB per day) ... same memory problem again. ... sure you send a mail even if all it says that there is nothing to report. ... For a critical component such as RAID, it's important to have a live monitoring system such as nagios so that you'll never miss out on such things. ...
    (perl.beginners)
  • Re: privoxy crash
    ... May be a memory problem, or a temporary memory problem, ... or if you have not checked the logs, ... Look in the privoxy log directory. ...
    (comp.os.linux.networking)