couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lasizoillo <lasizoi...@gmail.com>
Subject Re: Cores in a couchdb server
Date Tue, 17 Feb 2009 19:31:58 GMT
2009/2/17 lasizoillo <lasizoillo@gmail.com>:
> Hi
>
> I am running a couchdb (instaled from freebsd ports). I was very happy
> with him, but from some days ago I have some core dumps. No other
> process in this machine is affected from this issue:
>
> Feb 17 17:06:01 fry kernel: pid 14849 (beam), uid 1001: exited on
> signal 11 (core dumped)
> Feb 17 17:07:01 fry kernel: pid 14881 (beam), uid 1001: exited on
> signal 11 (core dumped)
> Feb 17 17:08:02 fry kernel: pid 14913 (beam), uid 1001: exited on
> signal 11 (core dumped)
> Feb 17 17:09:01 fry kernel: pid 14964 (beam), uid 1001: exited on
> signal 11 (core dumped)
> Feb 17 17:10:01 fry kernel: pid 15029 (beam), uid 1001: exited on
> signal 11 (core dumped)
> Feb 17 17:11:02 fry kernel: pid 15096 (beam), uid 1001: exited on
> signal 11 (core dumped)
> Feb 17 17:12:01 fry kernel: pid 15268 (beam), uid 1001: exited on
> signal 11 (core dumped)
> Feb 17 17:13:01 fry kernel: pid 15301 (beam), uid 1001: exited on
> signal 11 (core dumped)
> Feb 17 17:14:01 fry kernel: pid 15341 (beam), uid 1001: exited on
> signal 11 (core dumped)
> Feb 17 17:15:01 fry kernel: pid 15409 (beam), uid 1001: exited on
> signal 11 (core dumped)
>
> Some request generate core dumps, but not all. I couldn't found a
> pattern in bad requests.
>

Yes, I am a bit stupid. The pattern is the core time. A job launched
every minute was making an update that causes the problem.

I must do a reproducible test case of this update. A not controlled
input that raises a core must be an error. Sorry if I don't upload a
test case now, but I need reproduce without sensible data.

Excuse me for the noise.

> My machine is a Freebsd:
>
>  $ uname -a
> FreeBSD fry.o2cworld.com 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Mon
> Dec 15 19:08:33 CET 2008
> root@fry.o2cworld.com:/usr/obj/usr/src/sys/O2C  amd64
>
> The core gives ever the same info:
> # gdb /usr/local/lib/erlang/erts-5.6.5/bin/beam -c beam.core
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "amd64-marcel-freebsd"...(no debugging
> symbols found)...
> Core was generated by `beam'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /lib/libutil.so.7...(no debugging symbols found)...done.
> Loaded symbols for /lib/libutil.so.7
> Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done.
> Loaded symbols for /lib/libm.so.5
> Reading symbols from /lib/libncurses.so.7...(no debugging symbols found)...done.
> Loaded symbols for /lib/libncurses.so.7
> Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done.
> Loaded symbols for /lib/libthr.so.3
> Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done.
> Loaded symbols for /lib/libc.so.7
> Reading symbols from
> /usr/local/lib/erlang/lib/crypto-1.5.3/priv/lib/crypto_drv.so...(no
> debugging symbols found)...done.
> Loaded symbols for /usr/local/lib/erlang/lib/crypto-1.5.3/priv/lib/crypto_drv.so
> Reading symbols from /lib/libcrypto.so.5...(no debugging symbols found)...done.
> Loaded symbols for /lib/libcrypto.so.5
> Reading symbols from
> /usr/local/lib/couchdb/erlang/lib/couch-0.9.0a-incubating/priv/lib/couch_erl_driver.so...(no
> debugging symbols found)...done.
> Loaded symbols for
> /usr/local/lib/couchdb/erlang/lib/couch-0.9.0a-incubating/priv/lib/couch_erl_driver.so
> Reading symbols from /usr/local/lib/libicuuc.so.38...(no debugging
> symbols found)...done.
> Loaded symbols for /usr/local/lib/libicuuc.so.38
> Reading symbols from /usr/local/lib/libicudata.so.38...(no debugging
> symbols found)...done.
> Loaded symbols for /usr/local/lib/libicudata.so.38
> Reading symbols from /usr/local/lib/libicui18n.so.38...(no debugging
> symbols found)...done.
> Loaded symbols for /usr/local/lib/libicui18n.so.38
> Reading symbols from /usr/local/lib/libjs.so...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/local/lib/libjs.so
> Reading symbols from /usr/lib/libstdc++.so.6...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib/libstdc++.so.6
> Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done.
> Loaded symbols for /lib/libgcc_s.so.1
> Reading symbols from /usr/local/lib/libnspr4.so.1...(no debugging
> symbols found)...done.
> Loaded symbols for /usr/local/lib/libnspr4.so.1
> Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done.
> Loaded symbols for /libexec/ld-elf.so.1
> #0  0x00000000004a298e in external_size_1 ()
> [New Thread 0x800f02300 (LWP 100439)]
> [New Thread 0x800f02180 (LWP 100329)]
> (gdb) q
>
>
> I don't know where is the problem: couchdb, beam, freebsd or between
> my chair and my keyboard. Any idea?
>
> Excuse me for my bad english.
>
> Regards,
>
> Javi
>

Mime
View raw message