Hey,
That's still missing some information. How is the daemon itself
exiting/crashing/etc? I need at least a small hint to go on.
thanks,
-Dormando
On Tue, 25 Apr 2017, seenivasan g wrote:
> Hello Dormando,
> Thanks for the response.
>
> Note: We are running memcached on non-root user account.
Hello Dormando,
Thanks for the response.
Note: We are running memcached on non-root user account.
export SASL_CONF_PATH=$HOME/saslmemcached/memcached.conf
export MEMCACHED_SASL_PWDB=$HOME/saslmemcached/memcached-sasl.db
Initialized SASL.
slab class 1: chunk size96 perslab 10922
slab
Hey,
Can you provide any information on the crash itself? Any segfault lines in
dmesg, prints/abort lines from the daemon, or ideally a backtrace from a
core file?
thanks,
-Dormando
On Tue, 25 Apr 2017, Jack2498 wrote:
> Hello Team,
> I have followed these steps to compile & Instances working f
Hello Team,
I have followed these steps to compile & Instances working fine but it was
going down when our application trying to connect our sasl memcached
instances with wrong credentials.
tar -xvf memcached-1.4.36.tar.gz
cd memcached-1.4.36
./configure --enable-sasl-pwdb --prefix=$HOME/mem
Cool.
Yeah this agrees; zero outofmemory errors on all classes. Think I'm
missing a counter for chunked items still, in cases of "late" allocation
errors. Given the amount of memory free I can't see why that would happen
though.
Hopefully you're able to find the real error. Another thing I need t
And, I guess forgetting to attach the files I promise is a sign of
dinosaurness. Here they are.
On Tuesday, April 25, 2017 at 5:08:01 PM UTC-4, Min-Zhong "John" Lu wrote:
>
> Hello,
>
> Thanks for the response! So the slab automover is not the culprit.
>
> As for the exact server error: unfor
Hello,
Thanks for the response! So the slab automover is not the culprit.
As for the exact server error: unfortunately I don't have that for now as I
use libmemcached (plus pylibmc for that matter). With that said, I do have
used the plain telnet protocol when doing "further get requests" (as i
Hey!
Unfortunately you've summoned a dinosaur, as I am old now :P
My main question; do you have the exact server error returned by
memcached? If it is "SERVER_ERROR object too large for cache" - that error
has nothing to do with memory allocation, and is just reflecting that the
item attempted to
