2019 kl. 22:58 skrev dormando :
> example?
>
> On Mon, 9 Dec 2019, David Karlsen wrote:
>
> > OK, found it, apparently -e needs to be followed by path w/o any
> whitespace
> >
> > man. 9. des. 2019 kl. 21:54 skrev dormando :
>
example?
On Mon, 9 Dec 2019, David Karlsen wrote:
> OK, found it, apparently -e needs to be followed by path w/o any whitespace
>
> man. 9. des. 2019 kl. 21:54 skrev dormando :
> I'm not sure offhand. From my perspective I'd triple check what the
> path/file it's
- should not the file be created dynamically if it
> does not exist?
>
> fredag 6. desember 2019 23.51.38 UTC+1 skrev Dormando følgende:
> It's going to use some caps (opening files, mmap'ing them, shared
> memory,
> etc). I don't know what maps to which specific
It's going to use some caps (opening files, mmap'ing them, shared memory,
etc). I don't know what maps to which specific thing.
That error looks like an omission on my part..
mmap_fd = open(file, O_RDWR|O_CREAT, S_IRWXU);
if (ftruncate(mmap_fd, limit) != 0) {
perror("ftruncate
If you succeed you should share with the class :)
On Sun, 1 Dec 2019, David Karlsen wrote:
> Thank you - that explains it well. I'll look around if I can create a
> "durable" tmpfs in k8s via a storageclass :)
>
> søn. 1. des. 2019 kl. 04:25 skrev dormando :
>
an "equivalent" to writing the file at shutdown by moving the file
after shutdown :)
On Sun, 1 Dec 2019, David Karlsen wrote:
> Won’t the cache be written to file at shutdown and not contionously while
> running?
>
> søn. 1. des. 2019 kl. 03:58 skrev dormando :
> Hey,
>
ms". You'd need to have the right
system and memory and etc.
-Dormando
On Sat, 30 Nov 2019, David Karlsen wrote:
> Reading https://github.com/memcached/memcached/wiki/WarmRestart it is a bit
> unclear to me if the mount *has* to be tmpfs backed, or it can be a normal
> fileyst
It's fine. Just make sure you actually have enough RAM to handle it.
On Fri, 8 Nov 2019, Ramesh wrote:
> Thanks, how about the performance if increased to 512MB?
>
> On Friday, November 8, 2019 at 2:45:22 PM UTC-5, Dormando wrote:
> default is 1MB. You can increase that to 1
default is 1MB. You can increase that to 1G via the -I start argument.
On Fri, 8 Nov 2019, Ramesh wrote:
> Hello,
>
> I can breakdown what is the limit on the size of the value per key? I see
> Redis has limitation of 512MB or how about Memcached?
> Thanks
> Ramesh
>
> On Wednesday, November 6,
part of the codebase. If any of you have
production systems where you can run a memcached build non-live
(debug/development or ideally "shadowing" production traffic), I'd
appreciate you trying it out ahead of me merging it.
Thanks!
-dormando
--
---
You received this message b
Trying an experiment: https://discord.gg/8yVxuJY (this link won't work
forever).
The freenode IRC channel has been dying slowly. I hate slack's
multi-server interface and their profit model makes public/OSS chats
awful.
--
---
You received this message because you are subscribed to the Google
r numbers at 99 th percentile.
>
> However, my throughput numbers seems to be wrong. I hit a throughput
> kneepoint at 500K ops/sec while yours is around ~6000K.
> Order of magnitude difference. Can you please comment on it. :)
>
> thanks
> --Pradeep
>
> On Mon, Oc
arking numbers are heavily dependent on the setup and
> other things. But Is my numbers are faithful enough to be quoted for
> memcached single server numbers? In other words, are these numbers are way
> off from a typical memcached performance numbers?
>
> thanks
> --Pradeep
>
>
&
memaslap at all, so I can't attest to it. I use
https://github.com/memcached/mc-crusher with the external latency sampling
util it comes with. it's not as easy to use though.
On Mon, 7 Oct 2019, Pradeep Fernando wrote:
> Hi Dormando,
> That is great insight.!.
> However, it did not solve th
Hi,
First as an aside; 1/1 get/set ratio is unusual for mc. The gets scale a
lot better than sets. If you get into testing more "realistic" perf
numbers make sure to increase the get rate.
You're probably just running into CPU scaling. OS's come with a "battery
saver" or "ondemand" performance
That all depends on your SASL backend service; you should be able to
connect it to whatever you want.
However actually doing that can be complicated. You'll have to find
tutorials online, since it isn't memcached specific.
On Tue, 1 Oct 2019, Jiuming Shao wrote:
> Hi there,
> I have a quick
>
>
> That is a really nice idea - I'll definitely have to explore it. An
> effective hot cache like this may reduce or eliminate the need for mitigating
> specific keys. We could
> incorporate size into it so that larger values get a higher weighting.
>
First one's free :) I found some other
ata
> from the local cache. Using mget in either of the ways we talked about
> before would work for this
> scenario, but having the "fetch if cas does not match" flag would avoid the
> second round trip in the case that the value changes.
> Cheers,
> John
>
> On Su
wrote:
> Hi dormando,Sorry for the delayed response. I finally got a chance to read
> through https://github.com/memcached/memcached/pull/484 . It sounds great.
>
> In my case, I was thinking about using a local cache to mitigate the network
> impact of hot keys rather t
https://github.com/memcached/memcached/wiki/ReleaseNotes1518
enjoy
--
---
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.
Hey,
Check this out: https://github.com/memcached/memcached/pull/484
You can't quite do this with the way metaget is now, though it's feasible
to add some "value if cas match on mget" flag. I'd have to think it
through first.
For local caches though, unless your object is huge, simply waiting
It can be depending on how you use it; you need to discuss this with your
compliance officer.
On Fri, 6 Sep 2019, 'Jeganath James' via memcached wrote:
> Is Memcached HIPAA eligible/Compliant service. We have frequent asks from
> customers on similar lines. Any help is much appreciated.
>
> The
r capacity
reasons.
Should be in the mainline soon. I'm pushing to get it complete.
-Dormando
On Tue, 3 Sep 2019, Pradeep Fernando wrote:
> Hi Dormando,
> Thanks for the post!. I want to run the same benchmark/configuration for one
> of my workloads.
> In the post, you mentioned,
in the details frequently, would
be happy to hear from.
thanks,
-Dormando
--
---
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...@google
Yo,
In general we don't recommend using timestamps for short TTL's. They were
really meant for dates far off in the future (months, where the accuracy
wouldn't matter too much). There're zero use cases for TIMESTAMP + TTL
where ttl is short. simply stop adding time() to it, or run it through a
you're sure it was a clean compile after the NEED_ALIGN change?
Any idea what the most recent version to build/pass tests is?
I'm not sure how to fix this without access to HPPA hardware. It could
take ages to back and forth about it :(
On Sun, 28 Jul 2019, mike hosken wrote:
> Still fails log
Smells like NEED_ALIGN isn't getting set...
after configure, but before make:
edit config.h:
/* Machine need alignment */
/* #undef NEED_ALIGN */
^ change this to:
#define NEED_ALIGN 1
... then run make and make test?
On Sat, 27 Jul 2019, Mike Hosken wrote:
>
> Hi,
>
>
>
> The output files
looks like it actually built I guess.
I've never had an hppa machine. I do build test on ARM, but that's about
it for non-x86 CPU's lately.
after configure and make, what's the output of:
$ prove t/00-startup.t
If that passes, try:
$ prove t/*.t
.. and see which of those fails.
On Sat, 27
What does "make clean ; make" look like in that directory?
make isn't doing anything, is there even a memcached binary in the
directory?
On Fri, 26 Jul 2019, mike hosken wrote:
> Hi
> I have been trying to build memcached on debian hppa linux
>
> it fails to build in debian see log here
>
>
https://github.com/memcached/memcached/wiki/ReleaseNotes1515
--
---
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.
To view
https://github.com/memcached/memcached/pull/489
only user/pass in case users should be useful roles in the future, but for
now they're just blind tokens; everyone gets the same access.
need to decide on the SET method or switching to a GET command, else the
rest are small TODO items.
I'd like
flatbuffers are unrelated to protocol, and are definitely not backwards
compatible with ascii :p
On Thu, 9 May 2019, Roberto Spadim wrote:
> maybe could be used something like flatbuffers?
>
> Em qui, 9 de mai de 2019 às 20:15, dormando escreveu:
> To that end, I think SAS
more steps]
... extra roundtrip in the protocol but this could be solved with
mget/mset.
On Thu, 9 May 2019, dormando wrote:
> Indeed we would. SASL is actually a text based protocol, as it's used in
> SMTP and similar. That shouldn't be too bad.
>
> On Thu, 9 May 2019, Om Kale wrot
Indeed we would. SASL is actually a text based protocol, as it's used in
SMTP and similar. That shouldn't be too bad.
On Thu, 9 May 2019, Om Kale wrote:
> Hey Dormando,As of now only binary protocol supports SASL.
> Correct me if I am wrong but to ensure compatibility wit
Yo,
Any of you out there really _like_ the binary protocol? Aside from the
features it gives (CAS everywhere, pipelining, etc).
just thinkin' through some things.
Thanks,
-Dormando
--
---
You received this message because you are subscribed to the Google Groups
"memcached&q
A smallish patch with some significant feature change:
https://github.com/memcached/memcached/pull/484
1) all of the potential fetch modes (do/don't bump LRU, etc)
2) currently hidden metadata (TTL remaining, last access time, etc)
3) human-readable (or easily script-readable) dump of all
https://memcached.org/blog/persistent-memory/
did some extensive testing with the new persistent memory modules from
intel. If you can get them, they're pretty good. A lot less work to use
than I was expecting.
--
---
You received this message because you are subscribed to the Google Groups
https://github.com/memcached/memcached/wiki/ReleaseNotes1513
enjoy.
--
---
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.
Anyone want to take a look at/spin with this?
https://github.com/memcached/memcached/pull/440
no clients actually support TLS/SSL yet; you'd have to use an
stunnel/socat wrapper or modify a client.
curious to hear any feedback about usability/features/etc.
Thanks!
--
---
You received this
der.
>
> On Tue, Apr 9, 2019 at 2:49 PM dormando wrote:
> >
> > That's not a protocol error. What client/language/etc are you using?
> >
> > On Tue, 9 Apr 2019, abliskov...@fusionbox.com wrote:
> >
> > > Hi,
> > >
> > > We are fre
That's not a protocol error. What client/language/etc are you using?
On Tue, 9 Apr 2019, abliskov...@fusionbox.com wrote:
> Hi,
>
> We are frequently getting the error "operation now in progress" when
> attempting to delete keys from memcached, but I can find little
> documentation about how to
y "Buckets", that the memcached server
has some general idea of what to do with. In theory bucket A could be
extstore and bucket B could be different storage code, rather than simply
a different data path/device.
-Dormando
--
---
You received this message because you are subscribed to
ng the memory as-is.
On Wed, 27 Mar 2019, Jerome Kieffer wrote:
> Hi Dormado,
>
> Thanks for your prompt feed-back.
>
> On Tue, 26 Mar 2019 11:06:10 -0700 (PDT)
> dormando wrote:
>
> > Seems like this is a borderline use case, but it might still work for you.
>
> From
Seems like this is a borderline use case, but it might still work for you.
How did you verify you found the cause? Can you share snapshots from
"stats items" and "stats slabs" output after your test was run?
Memory isn't evenly distributed; it's assigned where objects actually
exist. so either
rfaces too. Questions like this
help me figure out which direction to go :)
On Fri, 22 Mar 2019, 'Nikhil' via memcached wrote:
> Got it. Thank you Dormando and Daniel for your prompt responses.
> Dormando, yes I am debugging a corner case, where I deleted an unused feature
> that queried
There's no way to retrieve the metadata back from an item aside from the
client flags as part of a normal command.
What people typically do is embed the original TTL into the object you've
stored. that way the application can read it or any other metadata you
want to make decisions with.
Though
, 20 Mar 2019, Eranda Rajapakshe wrote:
> Thanks a lot, Dormando!
> I'm using KETAMA_HASH at the client side, didn't go for CRC_HASH as per the
> Java Doc it says CRC_HASH can be slower in performance (and
> we are only having Java client, so no need to support for multiple
> plat
You don't need to worry about the server one at all. They don't need to
match up either; on the server side it's just for the hash table. The
default is fine. I only left jenkins in as a "just in case", too.
I don't think it matters that much for clients either. There're very few
buckets involved
> https://github.com/memcached/memcached/wiki/SASLHowto
> and https://github.com/memcached/memcached/wiki/SASLAuthProtocol
> Please let me know when you have time to take a closer look.
>
> Cheers!
> Jiuming
>
> dormando 于2019年3月18日周一 下午4:10写道：
> Hey,
>
>
Hey,
Can look more closely later, but a few quick things that might help:
1) stick to memcached/memcached on github - that's an old couchbase fork
you linked to. If you're using couchbase you need to talk to them instead.
2) in the t/ dir there're some unit tests for SASL which might help you
nly useful in measuring relative latency of changes in
the daemon vs scalability/throughput.
Just uploaded some fixes and an updated README file. pretty sure I'm the
only regular user of the thing so please ask away if anything is
weird/confusing.
have fun,
-Dormando
On Sun, 17 Mar 2019, 'Eamonn Nugent' via
m, 100m, etc) and re-running uniform
random benchmarks since fairness will affect the bucket depth and thus
latency.
Sorry if that's a pain in the ass, but this thing is quite widely used and
there aren't really beta testers :) Have to be thorough these days.
-Dormando
On Sun, 17 Mar 2019, 'Eamonn N
out which to use. It's also
heavily x86 optimized so we might have to default something else for ARM.
Sorry, not debated on the list, just in my own head :) It's not quite as
straightforward as just dropping it in. If you're willing to get all the
conditions tested go nuts! :)
-Dormando
On Sat, 16
: https://memcached.org/blog - gets
semi-regular updates about memcached internals, test benchmarks, and so
on. I'll link new posts to the ML going forward as well.
have fun,
-Dormando
--
---
You received this message because you are subscribed to the Google Groups
"memcached&q
You can use ssh port forwarding (-R/-L/etc), but that's going to be pretty
slow.
you'll find a better answer by looking up ways to network qemu guests with
the host. there're better guides and that's outside the scope of this
mailing list, I think. You should be able to just forward the memcached
bandwidth to ship uncompressed data to clients.
On Sun, 4 Nov 2018, Pradeep Sivakumar wrote:
> Thanks for the quick response. I have unlined my answers below:
>
> > On Nov 4, 2018, at 11:50 AM, dormando wrote:
> >
> > Not entirely clear on what you're doing. Are you modify
Not entirely clear on what you're doing. Are you modifying memcached
itself to do internal compression?
Some clients autocompress after threshholds. there's no internal
compression.
On Sun, 4 Nov 2018, Pradeep Sivakumar wrote:
> I am writing an internal compression routine that will compress
Check the stats on the daemon to see if it's rejected any client
connections?
That can happen if you're out of local ports, if the server's hit the
connection limit, etc.
On Fri, 2 Nov 2018, capoluc01 wrote:
> I sometimes get 0 Ops/sec in memtiers json output if run against memcached.
> Here
Version 1.2.8 is too old and is not supported, sorry! Newer versions do
not have that problem.
On Mon, 15 Oct 2018, huan ling wrote:
> Does the event_queue_remove problem resolved？
> My SUSE linux server with libevent 1.4 and memcached 1.2.8 have this problem
> too
>
> 在 2010年2月23日星期二
the event we hit this
> problem again.
Thanks! Appreciate your patience.
> -jj
>
> On Sat, Oct 13, 2018 at 10:07 AM dormando wrote:
> Sounds like the daemon hardlocked. Some of your start arguments
> are fairly
> aggressive (ext_item_size and -n especially
; I do have the results from "stats", "stats slabs", "stats items" and "stats
> conns" from 17:10 the previous evening. That doesn't show any obvious
> errors/problems slowly building up, waiting for some event to trigger a
> massive failure. But it
, stats items, stats slabs, and importantly "stats
conns" - you will probably have to redact some of the output.
3) were you still able to connect to and run commands on those daemons
while they had a mass of CLOSE_WAIT?
Thanks,
-Dormando
On Fri, 12 Oct 2018, jjo...@smugmug.com wrote:
>
Hey,
Sadly there isn't much I can do about such an old version, there're too
many bugs fixed since then. :/
Why can't you upgrade it? anything we can do to help there?
On Fri, 12 Oct 2018, Vlad Lobanov wrote:
> Hi,
>
> I use memcached 1.4.5 and have a question about two stats: bytes and
>
ght this is the Normal
> ~ # memcached -V
> memcached 1.5.6
>
>
> Am Mi., 22. Aug. 2018 um 00:19 Uhr schrieb dormando :
> can you just use normal memcached with it instead?
>
> if you want to extend onto disk, there's extstore:
> https://mem
can you just use normal memcached with it instead?
if you want to extend onto disk, there's extstore:
https://memcached.org/blog/extstore-cloud/
On Wed, 22 Aug 2018, Werner Naseweis wrote:
> Only nextcloud.
>
> Am Mi., 22. Aug. 2018 um 00:02 Uhr schrieb dormando :
> memc
memcachedb isn't supported software AFAIK. what're you using it for?
On Tue, 21 Aug 2018, Werner Naseweis wrote:
> [memcachedb] [Tue Aug 21 23:38:28 2018] "checkpoint thread: a txn_checkpoint
> is done"
> [memcachedb] [Tue Aug 21 23:38:29 2018] "memp_trickle thread: writing 0 dirty
> pages"
>
e
>
> On Thu, Aug 2, 2018 at 4:27 PM, dormando wrote:
> Why are you trying to do this? That's generally a bad sign, the
> replication is for redundancy. if you're just trying to confirm it
> works,
> you can do a brute force search for the key
>
>
Why are you trying to do this? That's generally a bad sign, the
replication is for redundancy. if you're just trying to confirm it works,
you can do a brute force search for the key
On Thu, 2 Aug 2018, Om Kale wrote:
> Hi All,I have enabled replication (using --NUMBER_OF_REPLICAS) and ketama
>
https://github.com/memcached/memcached/wiki/Hardware
On Wed, 1 Aug 2018, server requirements wrote:
> What are the server requirements of Memcached?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "memcached" group.
> To unsubscribe from this group
If you use memcached in production currently, I'd appreciate your taking a
couple minutes to answer this survey:
https://goo.gl/forms/37zynfK0PbUfTf1I3
thanks!
-Dormando
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubs
Hey,
You should talk with the authors of the application, since that depends on
how they implemented their cache. ie; if they call flush_all, or can't add
a namespace prefix to the cache keys, the instances cannot be shared.
On Mon, 9 Jul 2018, Pablo Ortiz wrote:
> Hello,
> I have an
!
-Dormando
--
---
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 https://groups.google.com/d/optout.
What kind of things do you find interesting?
There're a number of open issues right now which could use some work or
research; ones marked "help wanted" tend to be on the easier side.
There're some odd platform test failures that're likely race conditions in
extstore tests. I've fixed a few but
Thanks for these! Are you just cleaning up a few things, or are you
working on anything else? Just out of curiosity :)
On Mon, 18 Jun 2018, Vadim Pushtaev wrote:
> Hello.
>
> It's me running the test suite again :).
>
> `t/whitespace.t` fails for me because I have `.swo` and `.swp` files
'you can modify libmemcached to use OpenSSL
> directly', you mean setting up the socket connections in client to support
> SSL/TLS, corect?
Yes.
>
> Thanks and Regards,Om Kale
>
>
> On Mon, May 7, 2018 at 1:11 PM, dormando <dorma...@rydia.net> wrote:
> hmm. I gue
m some sort of certificate based
> authentication.One more question I had was, would the use of stunnel need any
> code change with memached codebase?
>
> Thanks and Regards,Om Kale
>
>
> On Mon, May 7, 2018 at 12:40 PM, dormando <dorma...@rydia.net> wrote:
>
stunnel. that might just make your life easier in both
directions, it's fairly simple.
On Mon, 7 May 2018, Om Kale wrote:
> Hi Dormando and Trond,I think I will first try Dormando's suggestion of
> stunnel before delving into changing the memcached code itself. I haven't read
> much about st
Hey,
Sorry, missed this earlier.
https://github.com/memcached/mc-crusher is the benchmark utility I use to
validate releases. There's a complete README but it might be a little
confusing to get going.
There're a number of examples in the conf/ directory. Let me know if any
concept is confusing
> On Fri, May 4, 2018 at 10:46 PM dormando <dorma...@rydia.net> wrote:
>
> The closest would be SCRAM-SHA-256/512 mechanism, but the RFC for that
> states "in combination with TLS" up front, and I'd be wary of using it
> over the internet as well.
>
ve to deal with a single certificate and you can block while
connecting/running commands.
On Fri, 4 May 2018, dormando wrote:
> Hey,
>
> On Fri, 4 May 2018, Om Kale wrote:
>
> > Hey Dormando and Trond,Thanks a lot for all of your inputs.
> > Let me give you guys a quick s
Hey,
On Fri, 4 May 2018, Om Kale wrote:
> Hey Dormando and Trond,Thanks a lot for all of your inputs.
> Let me give you guys a quick summary of what I am planning to do and the
> issues I am facing:
> I need memcached server with encryption and authentication support on
> w
You need the server to be on any OS? I thought it was a router thing you
were embedding.
What exactly are you doing, if you can share?
On Wed, 2 May 2018, Om Kale wrote:
> Hey Dormando,Yes you are right. I agree with you. I have gotten everything
> working with Ubuntu since Day 1
file to work the way you want it to.
On Wed, 2 May 2018, Om Kale wrote:
> Hi Dormando,Thanks for your reply. Yes, that works. Also, one more thing that
> I was
> curious to know or rather want to add to memcached.
> Is there anyway I can go ahead and modify memcached itself to sup
ding problem. It did help a lot.
> In fact, the precedence did help to find the better solution. Thanks once
> again.
>
> Cheers
>
> On Thursday, 26 April 2018 11:43:21 UTC+5:30, Dormando wrote:
> You're way way over thinking this.
>
> I originally gave two e
t; from another process tries to add and set simultaneously, will this lock
> happens at the
> memcached server or at the individual clients?
>
> On Thursday, 26 April 2018 09:26:30 UTC+5:30, Dormando wrote:
> Memcached is internally atomic on key operations. If you add and set at
e time
> thread 2 comes for the set operation, how 'set' lock and 'add' lock is
> handled here?
>
>
> On Thursday, 26 April 2018 06:58:27 UTC+5:30, Dormando wrote:
> Hey,
>
> ADD sets an item *only if it doesn't currently exist*.
>
> If you want thread
you for the reply.
> Can this add be used always, I mean during an update as well?
> What could be the potential disadvantage of this?
> So if two thread does an update using add, still lock hold well in this
> sceanrio?
>
> Thanks,
> Sachin
>
>
> On Wednesday, 25 April 2018
Hey,
Two short answers:
1) thread 1 uses 'add' instead of 'set'
2) thread 2 uses 'set'.
via add, a thread recaching an object can't overwrite one already there.
https://github.com/memcached/memcached/wiki/ProgrammingTricks#avoiding-stampeding-herd
for related issues. using an advisory lock
Well, being extremely thorough; read from file on startup and then use
online commands for modifications is perfectly doable too (and how some
things work) but I feel like that will be hard for people to use.
On Tue, 17 Apr 2018, dormando wrote:
> Right; I'm saying there needs to be a mechan
emcached server.
> Thanks,
> John
>
> On Mon, Apr 16, 2018 at 10:57 AM dormando <dorma...@rydia.net> wrote:
> Hey,
>
> Thanks for the feedback! That should be doable. I'm used to this being a
> pain with TLS ticket rotation/etc anyway. This'll probabl
oh; you might need to `sudo ldconfig` before that works, too
On Tue, 17 Apr 2018, Om Kale wrote:
> Hey Dormando,
> I was trying to play around with memcached sasl a bit more on Ubuntu.
> I tried to use the cyrus sasl libraries.
> However, when I try to run the memcached ser
Did you recompile memcached on there or copy the binary?
On Tue, 17 Apr 2018, Om Kale wrote:
> Hey Dormando,
> I was trying to play around with memcached sasl a bit more on Ubuntu.
> I tried to use the cyrus sasl libraries.
> However, when I try to run the memcached server it gives t
Hey,
Thanks for the feedback! That should be doable. I'm used to this being a
pain with TLS ticket rotation/etc anyway. This'll probably end up
requiring a reload mechanism but shouldn't be too messy, I guess?
On Mon, 16 Apr 2018, John Reilly wrote:
> Hi dormando,I would love to see this cha
nticated() in cmd 0x21 is true
> mech: ``PLAIN'' with 26 bytes of data
> INFO: User <testuser@OKALE-M-33H5> failed to authenticate
> SASL (severity 2): Password verification failed
> sasl result code: -20
> Unknown sasl response: -20
> >19 Writing an error: Auth failure
Hey Dormando,
> No the saslpasswd2 command didn't give me any output. I will use strace to
> check for errors.
> Additionally, are you using an Ubuntu machine (If yes, how did you install
> sasl on your machine and did you make any changes to it inorder to make it
> work). I am asking t
a few
years distro's can start shipping with default or randomized auth tokens.
Open to feedback. Thanks!
-Dormando
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop receiving emails from
not
writing the file; it worked fine for me immediately.
how did you install sasl on your machine? or did it come with it?
On Tue, 10 Apr 2018, Om Kale wrote:
> Hi Dormando,
> I finally figured it out the issue from the above thread itself.
> The small change in steps as shown below w
Hey,
What is the exact output from saslpasswd2 when you run it?
On Tue, 10 Apr 2018, Om Kale wrote:
> Hi Dormando,
> Thanks for your guidance. Meanwhile, reading through the memcached email
> chain, I see someone else also observed something similar but there was no
> solution.
via the sasldb_path: line.
On Tue, 10 Apr 2018, Om Kale wrote:
> Hi Dormando,
> Thanks for the help. I tried the steps you mentioned but end up getting
> similar error. However, the error is slightly different this time.
> Why is it still pointing to '/tmp/memcached-sasl-db' when the SA
yes and yes.
mkdir sasl
cd sasl
then created memcached.conf
I did not create memcached-sasl-pwdb manually. saslpasswd2 made that for
me after I passed the -f argument.
On Tue, 10 Apr 2018, Om Kale wrote:
> Hi Dormando,
> Thanks for the update. I will try this out now. But before this I h
101 - 200 of 993 matches
Mail list logo
