[pgpool-general: 1179] 3.2.1 segfaults at startup on Fedora17

Lonni J Friedman netllama at gmail.com
Tue Nov 13 08:58:29 JST 2012


I'm in the process of migrating from Fedora16 to Fedora17 (all
x86_64).  One of the last services that need to be migrated is pgpool.
 I've been successfully building & running version 3.2.1 on Fedora16
for a few months.  However, after rebuilding 3.2.1 on Fedora17, it
segfaults immediately after starting.  Here's a backtrace from the
segfault:

##########
[root at cuda-farm-ljf0 pgpool-II]# gdb /usr/bin/pgpool
GNU gdb (GDB) Fedora (7.4.50.20120120-50.fc17)
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/pgpool...Reading symbols from
/usr/lib/debug/usr/bin/pgpool.debug...done.
done.
(gdb) run -f /etc/pgpool-II/pgpool.conf -n
Starting program: /usr/bin/pgpool -f /etc/pgpool-II/pgpool.conf -n
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
2012-11-12 14:49:58 LOG:   pid 11164: wd_chk_sticky:
ifup[/sbin/ifconfig] doesn't have sticky bit
[New Thread 0x7ffff7354700 (LWP 11167)]
[New Thread 0x7ffff6b53700 (LWP 11168)]
Detaching after fork from child process 11170.
Detaching after fork from child process 11172.
[New Thread 0x7ffff6352700 (LWP 11171)]
Detaching after fork from child process 11173.
[Thread 0x7ffff6b53700 (LWP 11168) exited]
[Thread 0x7ffff6352700 (LWP 11171) exited]
[Thread 0x7ffff7354700 (LWP 11167) exited]

Program received signal SIGSEGV, Segmentation fault.
0x0000003afca08d40 in pthread_detach () from /lib64/libpthread.so.0
Missing separate debuginfos, use: debuginfo-install
audit-libs-2.2.1-1.fc17.x86_64 cyrus-sasl-lib-2.1.23-31.fc17.x86_64
glibc-2.15-57.fc17.x86_64 keyutils-libs-1.5.5-2.fc17.x86_64
krb5-libs-1.10.2-6.fc17.x86_64 libcom_err-1.42.3-2.fc17.x86_64
libgcc-4.7.2-2.fc17.x86_64 libmemcached-1.0.4-1.fc17.x86_64
libselinux-2.1.10-3.fc17.x86_64 libstdc++-4.7.2-2.fc17.x86_64
nspr-4.9.2-1.fc17.x86_64 nss-3.13.5-1.fc17.x86_64
nss-softokn-freebl-3.13.5-1.fc17.x86_64 nss-util-3.13.5-1.fc17.x86_64
openldap-2.4.32-3.fc17.x86_64 openssl-1.0.0j-2.fc17.x86_64
pam-1.1.5-7.fc17.x86_64 postgresql-libs-9.1.6-1.fc17.x86_64
zlib-1.2.5-7.fc17.x86_64
(gdb) bt
#0  0x0000003afca08d40 in pthread_detach () from /lib64/libpthread.so.0
#1  0x000000000047afbe in wd_is_upper_ok (server_list=<optimized out>)
at wd_ping.c:114
#2  0x0000000000478dad in wd_init () at wd_init.c:75
#3  0x0000000000477fd7 in wd_main (fork_wait_time=1) at watchdog.c:118
#4  0x00000000004069da in main (argc=<optimized out>, argv=<optimized
out>) at main.c:642
(gdb)
##########


Note if I use the 3.2.1 build from Fedora16 on Fedora17, it runs ok,
so this is something specific to building on Fedora17.  I'm not using
any non-default environment build variables.  My configure line is as
follows (this is from the RPM spec file that I'm using to handle the
build & packaging):
--with-memcached=/usr/include/libmemcached
--with-pgsql-includedir=%{_includedir}/pgsql
--with-pgsql=%{_libdir}/pgsql --disable-static --with-pam
--disable-rpath --sysconfdir=%{_sysconfdir}/%{short_name}/

Is this a known bug?

thanks


More information about the pgpool-general mailing list