I've looked through the archives and found a couple of references,
mostly to the double free message below.  Suggestions have included
disabling nsrauth for a client and modifying environment variable
MALLOC_CHECK_  to prevent nsrexecd from being killed immediately (both
from 2 years ago).  I'm having an issue where I am receiving one of
these messages at different nsrexecd core dumps.

*** glibc detected *** double free or corruption (fasttop):
0x0000002a987ffc30 ***
*** glibc detected *** corrupted double-linked list: 0x00000037e6c316b8
***

I am running v7.3.3 Networker - 64-bit on RHEL4 ES Update 6 x86_64.  If
I restart Networker and the group in question everything is fine for a
while which can be a day, a few days, a week, ... and then it happens
again. I have a separate smaller system running the 32-bit OS and
Networker and it does not have this issue.

Has anyone else worked this issue to a happy conclusion?  Is going to
the 32-bit Networker a viable option?  I don't have the luxury of a test
system, so, any solution needs to have good track record.


Patti Clark
Sr. Unix System Administrator - RHCT, GSEC
Office of Scientific and Technical Information



To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER