privoxy crash - Networking

This is a discussion on privoxy crash - Networking ; 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 *** ======= Backtrace: ========= /lib/i686/libc.so.6[0xb7e126b8] /lib/i686/libc.so.6(malloc+0x85)[0xb7e13cf5] /lib/i686/libc.so.6[0xb7e01edf] /lib/i686/libc.so.6(fopen+0x2c)[0xb7e01fac] /lib/libnss_files.so.2[0xb7d3af53] /lib/libnss_files.so.2(_nss_files_gethostbyname_r+0x37)[0xb7d3ba47] /lib/i686/libc.so.6(gethostbyname_r+0x13a)[0xb7e8d2fa] /usr/sbin/privoxy[0x805ce17] /usr/sbin/privoxy[0x805d1f9] /usr/sbin/privoxy[0x805cac3] /usr/sbin/privoxy[0x805ddeb] ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: privoxy crash

  1. privoxy crash

    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 ***
    ======= Backtrace: =========
    /lib/i686/libc.so.6[0xb7e126b8]
    /lib/i686/libc.so.6(malloc+0x85)[0xb7e13cf5]
    /lib/i686/libc.so.6[0xb7e01edf]
    /lib/i686/libc.so.6(fopen+0x2c)[0xb7e01fac]
    /lib/libnss_files.so.2[0xb7d3af53]
    /lib/libnss_files.so.2(_nss_files_gethostbyname_r+0x37)[0xb7d3ba47]
    /lib/i686/libc.so.6(gethostbyname_r+0x13a)[0xb7e8d2fa]
    /usr/sbin/privoxy[0x805ce17]
    /usr/sbin/privoxy[0x805d1f9]
    /usr/sbin/privoxy[0x805cac3]
    /usr/sbin/privoxy[0x805ddeb]
    /lib/i686/libpthread.so.0[0xb7ee0562]
    /lib/i686/libc.so.6(__clone+0x5e)[0xb7e774de]
    ======= Memory map: ========
    08048000-08072000 r-xp 00000000 03:01 798894 /usr/sbin/privoxy
    08072000-08073000 rw-p 00029000 03:01 798894 /usr/sbin/privoxy
    08073000-08387000 rw-p 08073000 00:00 0 [heap]
    afd06000-afd07000 ---p afd06000 00:00 0
    afd07000-b0507000 rw-p afd07000 00:00 0
    b350d000-b350e000 ---p b350d000 00:00 0
    b350e000-b3d0e000 rw-p b350e000 00:00 0
    b450f000-b4510000 ---p b450f000 00:00 0
    b4510000-b4d10000 rw-p b4510000 00:00 0
    b6d14000-b6d15000 ---p b6d14000 00:00 0
    b6d15000-b7515000 rw-p b6d15000 00:00 0
    b7515000-b7523000 r-xp 00000000 03:01 275985 /lib/libresolv-2.4.so
    b7523000-b7525000 rw-p 0000d000 03:01 275985 /lib/libresolv-2.4.so
    b7525000-b7527000 rw-p b7525000 00:00 0
    b7527000-b752b000 r-xp 00000000 03:01 275952 /lib/libnss_dns-2.4.so
    b752b000-b752d000 rw-p 00003000 03:01 275952 /lib/libnss_dns-2.4.so
    b752d000-b7535000 r-xp 00000000 03:01 275958 /lib/libnss_nis-2.4.so
    b7535000-b7537000 rw-p 00007000 03:01 275958 /lib/libnss_nis-2.4.so
    b7a00000-b7a21000 rw-p b7a00000 00:00 0
    b7a21000-b7b00000 ---p b7a21000 00:00 0
    b7c00000-b7c21000 rw-p b7c00000 00:00 0
    b7c21000-b7d00000 ---p b7c21000 00:00 0
    b7d38000-b7d40000 r-xp 00000000 03:01 275954 /lib/libnss_files-2.4.so
    b7d40000-b7d42000 rw-p 00007000 03:01 275954 /lib/libnss_files-2.4.so
    b7d42000-b7d77000 r--s 00000000 03:01 776204 /var/db/nscd/passwd
    b7d77000-b7dac000 r--s 00000000 03:01 776203 /var/db/nscd/group
    b7dac000-b7dad000 rw-p b7dac000 00:00 0
    b7dad000-b7ed4000 r-xp 00000000 03:01 275459 /lib/i686/libc-2.4.so
    b7ed4000-b7ed5000 r--p 00126000 03:01 275459 /lib/i686/libc-2.4.so
    b7ed5000-b7ed7000 rw-p 00127000 03:01 275459 /lib/i686/libc-2.4.so
    b7ed7000-b7edb000 rw-p b7ed7000 00:00 0
    b7edb000-b7eea000 r-xp 00000000 03:01 275463 /lib/i686/libpthread-2.4.so
    b7eea000-b7eec000 rw-p 0000e000 03:01 275463 /lib/i686/libpthread-2.4.so
    b7eec000-b7eee000 rw-p b7eec000 00:00 0
    b7eee000-b7eef000 r-xp 00000000 03:01 887231 /usr/lib/libpcreposix.so.0.0.0
    b7eef000-b7ef0000 rw-p 00001000 03:01 887231 /usr/lib/libpcreposix.so.0.0.0
    b7ef0000-b7f0c000 r-xp 00000000 03:01 816962 /lib/libpcre.so.0.0.1
    b7f0c000-b7f0d000 rw-p 0001c000 03:01 816962 /lib/libpcre.so.0.0.1
    b7f0d000-b7f1d000 r-xp 00000000 03:01 275948 /lib/libnsl-2.4.so
    b7f1d000-b7f1f000 rw-p 0000f000 03:01 275948 /lib/libnsl-2.4.so
    b7f1f000-b7f21000 rw-p b7f1f000 00:00 0
    b7f33000-b7f3d000 r-xp 00000000 03:01 275478 /lib/libgcc_s-4.1.1.so.1
    b7f3d000-b7f3e000 rw-p 0000a000 03:01 275478 /lib/libgcc_s-4.1.1.so.1
    b7f3e000-b7f41000 rw-p b7f3e000 00:00 0
    b7f41000-b7f59000 r-xp 00000000 03:01 275469 /lib/ld-2.4.so
    b7f59000-b7f5a000 r--p 00017000 03:01 275469 /lib/ld-2.4.so
    b7f5a000-b7f5b000 rw-p 00018000 03:01 275469 /lib/ld-2.4.so
    bfcbb000-bfcd1000 rw-p bfcbb000 00:00 0 [stack]
    ffffe000-fffff000 ---p 00000000 00:00 0 [vdso]




    Thanks....

    --
    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.

  2. Re: privoxy crash

    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.


  3. Re: privoxy crash

    7 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.

+ Reply to Thread