Memcached crashing on FreeBSD
evan.martin at gmail.com
Fri Apr 8 21:12:28 PDT 2005
You can get backtraces from core files, too.
ulimit -c unlimited
then run memcached until it crashes, then
gdb /path/to/memcached /path/to/core/file
then run the "bt" command and send it to the list.
On Apr 8, 2005 1:36 PM, Brad Fitzpatrick <brad at danga.com> wrote:
> Could you run a debug build and run gdb in screen, then run your runner
> script in another window, waiting to start it up once the other one
> I guess it wouldn't start up until the crashed one (still alive in gdb)
> closes its listening socket on port 11211. Is there a gdb command to
> make a program close all its sockets on crash?
> Or in gdb just type "run <args>" and then once it starts, immediately type
> "bt<enter>" so it'll backgrace on crash. In another window, run a script
> to every second check if memcached isn't responding, and if not, kill gdb
> (it already did its backtrace presumably) and then run your normal runner.
> I'm down for other suggestions, though.
> On Fri, 8 Apr 2005, Jason Coene wrote:
> > Hello,
> > I'm using memcached in a fairly high traffic environment (but then again,
> > who among us aren't!). I have the memcached server running on FreeBSD
> > 5.2-RELEASE and 5.3-RELEASE machines, and every day or two the service
> > suddenly crashes (on both machines). There are no hardware issues with
> > either machine.
> > >From dmesg:
> > pid 2408 (memcached), uid 70: exited on signal 6
> > pid 4872 (memcached), uid 70: exited on signal 6
> > pid 9778 (memcached), uid 70: exited on signal 6
> > pid 15861 (memcached), uid 70: exited on signal 6
> > pid 24009 (memcached), uid 70: exited on signal 6
> > pid 28084 (memcached), uid 70: exited on signal 6
> > pid 33100 (memcached), uid 70: exited on signal 6
> > pid 45761 (memcached), uid 70: exited on signal 6
> > pid 58788 (memcached), uid 70: exited on signal 6
> > Libevent 0.9 built with:
> > ./configure --prefix=/usr/local/
> > Memcached 1.1.11 built with:
> > ./configure --prefix=/usr/local/ --with-libevent=/usr/local/
> > Memcached is run inside of a restart script (this has been happening for a
> > while, just tracking it down now) with commands:
> > screen -A -m -d -S "Memcached 11211" /usr/local/bin/memcachedrun -u
> > memcached -p 11211 -m 1024 -c 1024
> > "memcachedrun" is just an infinite loop calling /usr/local/bin/memcached $*
> > I've searched but couldn't find any known issues, has anyone had similar
> > problems? Is there something I can do to debug the issue?
> > Thanks,
> > Jason
More information about the memcached