[Date Prev][Date Next] [Chronological] [Thread] [Top]

openldap 2.1.30 SIGPIPE?

Hey.  So, we're trying to avoid going to 2.2.

After attaching to slapd with gdb, we appear to get one or more SIGPIPEs, which end up crashing the server after somewhere around 24-48 hours of heavy use:

(gdb) c
Continuing.
[New Thread -1810891856 (LWP 31973)]
[New Thread -1829766224 (LWP 32036)]
[New Thread -1850737744 (LWP 32122)]
[New Thread -1865417808 (LWP 32166)]
[New Thread -1882195024 (LWP 32167)]
[New Thread -1886393424 (LWP 32168)]
[New Thread -1898984528 (LWP 32169)]
[New Thread -1903182928 (LWP 32170)]
[New Thread -1915774032 (LWP 32171)]
[New Thread -1919972432 (LWP 32172)]
[New Thread -1932563536 (LWP 32173)]
[New Thread -1936761936 (LWP 32174)]
[New Thread -1949353040 (LWP 32176)]
[New Thread -1953551440 (LWP 32177)]


Program received signal SIGPIPE, Broken pipe.
[Switching to Thread -1771504720 (LWP 31494)]
0xb75ebc32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb)
Continuing.

Program received signal SIGPIPE, Broken pipe.
[Switching to Thread -1767306320 (LWP 31491)]
0xb75ebc32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) bt
#0  0xb75ebc32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
Error accessing memory address 0x96a8d240: No such process.
(gdb) thr apply all bt
Cannot find new threads: generic error


I'm not an experienced "gdb" user, so let me know what to do if there's some way of getting the backtrace to provide information.

I looked for SIGPIPE in the archives, but most of the issues related to client-side problems. Does this symptom suggest any possible remedies?

Thanks very much!
John
--
           John Borwick
       Systems Administrator
      Wake Forest University | web  http://www.wfu.edu/~borwicjh
      Winston-Salem, NC, USA | GPG key ID               56D60872

Attachment: signature.asc
Description: OpenPGP digital signature