Hey,
I'm very sorry it's taken so long for me to respond again. I understand
you're having some trouble, but there is a language barrier and I am
struggling to understand _exactly_ what is happening to you and what you
are expecting.
We keep asking you again and again, what _exactly_ happens to t
I don't see anything towards the end of log which says the server is stopped or
anything like that. I am not sure
what do you mean by memcached server goes offline?. Can you check the status of
memcached port using "netstat -an | grep 11211 on the memcached server? Is it
still listening?
You c
Initialized SASL.
slab class 1: chunk size96 perslab 10922
slab class 2: chunk size 120 perslab8738
slab class 3: chunk size 152 perslab6898
slab class 4: chunk size 192 perslab5461
slab class 5: chunk size 240 perslab4369
slab cl
Can you please share memcached verbose logs?
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to memcached+unsubscr...@googlegroups.com.
For more options, visit h
Hi Wathul,
Your response is greatly appreciated.
Thanks
On Thursday, May 11, 2017 at 1:56:33 PM UTC-7, rajesh pilla wrote:
>
> Yes, message is from application logs.
>
> Yes memcahced is running before starting my application with wrong
> credentials.
> And I start memcahced with -vvv mode (mem
Yes, message is from application logs.
Yes memcahced is running before starting my application with wrong
credentials.
And I start memcahced with -vvv mode (memcached -S -B binary -vvv), but
nothing much helpful in logs.
How is it possible? Is it property control?
Just want to be clear, I want
The message is from your application log and not from memcached. The thing you
want to achieve is absolutely possible.
Have you checked the actual state of the memcached?
You may want to run your memcached demon in verbose(-vvv) mode, that will give
you(us) some more infromation.
--
---
Yo
Thanks Dormando and Watul23 for the response.
I have memcached UP and running with SASL support on port# 11221. And I
have exported both "MEMCACHED_SASL_PWDB" and "SASL_CONF_PATH". When I try
to start my application with wrong username for a negative test-case then
the memcached running on port
Thanks Watul23 for the response.
I have memcached UP and running with SASL support on port# 11221. And I
have exported both "MEMCACHED_SASL_PWDB" and "SASL_CONF_PATH". When I try
to start my application with wrong username for a negative test-case then
the memcached running on port# 11221 is go
Offline means your application which trying to connect to mecached server
getting the "server temporary disabled" as return value? Which is 47 I believe.
If this is the case then its expected behavior, after some consecutive
attempts to connect to server with invalid username/password sever get
Hey,
Can you describe what "going offline" means exactly? is the server
crashing, is the client disconnecting, or etc?
On Tue, 9 May 2017, rajesh pilla wrote:
> Hi Team,
> I am trying to setup Memcached(1.4.36) with SASL support. After the setup,
> when I try to start my application using wrong
Hi Team,
I am trying to setup Memcached(1.4.36) with SASL support. After the setup,
when I try to start my application using wrong username or password that is
not configured in SASL-DB, Memcached running on that specific port is going
offline and throwing authenticate failure error in logs whe
12 matches
Mail list logo
