Comment #1 on issue 414 by dorma...@rydia.net: memcached 1.4.24 segfaults
https://code.google.com/p/memcached/issues/detail?id=414
crap, I wish I saw this sooner.
What is your items.c:1183?
It looks like:
if (it-prev) {
it-prev-next = it;
}
^ middle line.
I'd love
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 414 by ant...@corp.badoo.com: memcached 1.4.24 segfaults
https://code.google.com/p/memcached/issues/detail?id=414
What steps will reproduce the problem?
1.
SLES 11.3 with slightly patched 3.16 kernel
Linux memcached9 3.16.3
Comment #14 on issue 278 by lgromano...@gmail.com: Memcached 1.4.13
segfaults (error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
Hi,
I'm observing similar segfault on memcached v1.4.15 (memcached 1.4.15-1)
from ArchLinux (stable), unfortunately I don't have
Comment #11 on issue 278 by douglas@apollogrp.edu: Memcached 1.4.13
segfaults (error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
[root@HOST_NAME ~]# memcached -d -u nobody -m 1024 -p 11211 -S -vv
Initialized SASL.
slab class 1: chunk size96
Comment #12 on issue 278 by douglas@apollogrp.edu: Memcached 1.4.13
segfaults (error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
I am running on the same system I built on. There were no SASL libraries
existing when I installed on this box. Here
Comment #13 on issue 278 by dsalli...@gmail.com: Memcached 1.4.13 segfaults
(error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
Thanks for all the info. This is definitely golden path stuff, so
something odd is going on.
Comment #9 on issue 278 by dorma...@rydia.net: Memcached 1.4.13 segfaults
(error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
Dustin? Any clue?
Comment #10 on issue 278 by dsalli...@gmail.com: Memcached 1.4.13 segfaults
(error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
Almost seems like a library problem. Are you running on the same system
you built on? Any weird (non-package) sasl parts
Comment #5 on issue 278 by douglas@apollogrp.edu: Memcached 1.4.13
segfaults (error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
gdb backtrace attached
Comment #6 on issue 278 by douglas@apollogrp.edu: Memcached 1.4.13
segfaults (error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
gdb output attached. i didn't see where the file went so i'll just paste
the file in the comment box:
[root@HOSTNAME
Comment #7 on issue 278 by dsalli...@gmail.com: Memcached 1.4.13 segfaults
(error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
We need the backtrace during a crash, not on a properly functioning server.
Comment #8 on issue 278 by douglas@apollogrp.edu: Memcached 1.4.13
segfaults (error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
I'm new to this GDB thing so sorry about the wrong stack trace. This link
helped me to figure out how to get a core dump
Comment #1 on issue 278 by alexey.s...@hivext.net: Memcached 1.4.13
segfaults (error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
The same for me :(
Comment #2 on issue 278 by i...@hivext.net: Memcached 1.4.13 segfaults
(error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
Guys, can you please tell us where we need search for solution, it's very
important for us. Thanks.
Comment #3 on issue 278 by i...@hivext.net: Memcached 1.4.13 segfaults
(error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
Guys, here is debug with GDB
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7202a700 (LWP 5697
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 278 by douglas@apollogrp.edu: Memcached 1.4.13 segfaults
(error 4) when SASL enabled
http://code.google.com/p/memcached/issues/detail?id=278
What steps will reproduce the problem?
1. Build the memcached code
I was finally able to reproduce the cause on my dev server. The
segfaults were caused by the process exceeding its open file limit. This
explains why only one data center had segfaults (the busier one) and the
other only saw increasing connections to memcached.
On a dev server, running
://brian.moonspot.net/
On 5/6/10 1:09 AM, Brian Moon wrote:
I was finally able to reproduce the cause on my dev server. The
segfaults were caused by the process exceeding its open file limit. This
explains why only one data center had segfaults (the busier one) and the
other only saw increasing
Comment #4 on issue 117 by tacohamers: memcached 1.4.4 segfaults error 6 on
CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit
http://code.google.com/p/memcached/issues/detail?id=117
I feel stupid for running CentOS 5.4 someone tell me WHY?
This bug is resolved by installing
libevent-devel-1.3b-1
Updates:
Status: Invalid
Comment #5 on issue 117 by trond.norbye: memcached 1.4.4 segfaults error 6
on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit
http://code.google.com/p/memcached/issues/detail?id=117
(No comment was entered for this change.)
--
You received this message because you
:57 PM, memcac...@googlecode.com wrote:
Comment #1 on issue 117 by brandon.s.ramirez: memcached 1.4.4 segfaults
error 6 on CentOS 5.4 kernel2.6.18-164.9.1.el5 64bit
http://code.google.com/p/memcached/issues/detail?id=117
This also occurs on RedHat ES5 (which makes sense since CentOS is based
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 117 by tacohamers: memcached 1.4.4 segfaults error 6 on CentOS
5.4 kernel2.6.18-164.9.1.el5 64bit
http://code.google.com/p/memcached/issues/detail?id=117
What steps will reproduce the problem?
1. ./configure --prefix
This seems to have been memory related after all.
When I reduce the memory usage with -m 3000 rather than -m 3200 then the
machines are stable :/
These are running on 32-bit Debian lenny without any 'large mem'
patches, so is the maximum RAM per process simply 3072MB (3 x 1024) ? I
thought each
32-bit systems have a few different options of memory address splitting
based on what distro/kernel/patches you're using.
The ancient approach was 2G userpace 2G kernelspace for a process. Ingo
molnar added a 3G/1G split at some point, so userspace applications can
use 3G of space while
Hi, we've been using 1.2.6 on amd64 for months without a single problem,
but we want to migrate from 2 x 16GB machines to 16 x 4G 32-bit machines
for better survivability.
Unfortunately we're getting a lot of segfaults both with 1.2.6 and
1.2.8 :(
This is the backtrace I get from a 1.2.6-debug
Tried with 1.2.8 with --enable-threads (we've always used this on the
1.2.6 instances, both on amd64 + i386) and got an identical backtrace.
I then recompiled without --enable-threads and got this backtrace:
Starting program: /usr/bin/memcached -m 3200 -p 11211 -u nobody -c 4096
-t 10
[Thread
survivability.
Unfortunately we're getting a lot of segfaults both with 1.2.6 and
1.2.8 :(
This is the backtrace I get from a 1.2.6-debug instance (I have since
started gdb on a 1.2.8-debug instance to get the 'latest and greatest)
Hopefully this will mean something to a dev, because I'm gradually
On May 23, 10:48 am, Gavin Hamill g...@acentral.co.uk wrote:
Hm, it was the memcached-debug one I used. That said, I didn't run with
any -v options. How should I be compiling / running for maximum data?
I was hoping an assertion would've fired somewhere.
Were the backtraces of any use at
On Sat, 2009-05-23 at 12:14 -0700, Dustin wrote:
It's possible, but more info is better. Any chance you can run a
server under valgrind?
Yep sure. I've never used valgrind before and don't want to waste an
opportunity to capture some golden information. Can you provide the
syntax for
On May 23, 12:27 pm, Gavin Hamill g...@acentral.co.uk wrote:
Yep sure. I've never used valgrind before and don't want to waste an
opportunity to capture some golden information. Can you provide the
syntax for optimal valgrind usage?
I haven't used valdgrind in a while (OS X memory
Hi,
yes, setting 'echo 1024 /proc/sys/fs/epoll/max_user_instances'
where 1024 ist something
larger than MaxClients fixed this issue for me (also verified on
Kernel 2.6.28.1).
Ciao,
Werner
file image from memory.
As soon as I deactivate extension=memcache.so from the PHP php.ini
file, Apache is running without any
Problems nor Segfaults. In the next steps I've done the following
- Recompiled the Memcache PHP-API 2.2.4
- Switched the Memcache PHP-API from 2.2.4 to 3.0.2beta
=memcache.so from the PHP php.ini
file, Apache is running without any
Problems nor Segfaults. In the next steps I've done the following
- Recompiled the Memcache PHP-API 2.2.4
- Switched the Memcache PHP-API from 2.2.4 to 3.0.2beta
- Reinstalled Memcached 1.2.6
- Updated libevent from 1.4.5stable
33 matches
Mail list logo
