Comment #14 on issue 231 by dsalli...@gmail.com: SASL authentication not
working on reboot
http://code.google.com/p/memcached/issues/detail?id=231
Is this still an issue? It sounds like there was a permissions issue on
this particular installation.
--
You received this message because th
Comment #13 on issue 231 by luke.biddell: SASL authentication not working
on reboot
http://code.google.com/p/memcached/issues/detail?id=231
In Opscode Chef speak, this is what I did:
file "/etc/sasldb2" do
mode "0640"
owner "root"
group node[:memcached][:group]
notifies :restart, re
Comment #12 on issue 231 by luke.biddell: SASL authentication not working
on reboot
http://code.google.com/p/memcached/issues/detail?id=231
Yes - changing the group of /etc/sasldb2 (to be the group of the user
memcached is running as) works fine.
--
You received this message because this
Comment #11 on issue 231 by dorma...@rydia.net: SASL authentication not
working on reboot
http://code.google.com/p/memcached/issues/detail?id=231
did it that fix it?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may ad
Comment #10 on issue 231 by luke.biddell: SASL authentication not working
on reboot
http://code.google.com/p/memcached/issues/detail?id=231
We're seeing this here on centos 6.3. Same symptoms. On boot it's broken
but fine after a sudo service restart.
I'm just going to try fiddling with t
Updates:
Owner: dsalli...@gmail.com
Comment #9 on issue 231 by dorma...@rydia.net: SASL authentication not
working on reboot
http://code.google.com/p/memcached/issues/detail?id=231
Dustin: can you give this a quick look and see if it's worth leaving open?
Thanks!
Comment #8 on issue 231 by dorma...@rydia.net: SASL authentication not
working on reboot
http://code.google.com/p/memcached/issues/detail?id=231
I have no idea what's going on here; is it possible your systems are
actually starting memcached in different ways when doing it from boot than
Comment #7 on issue 231 by esoteric...@gmail.com: SASL authentication not
working on reboot
http://code.google.com/p/memcached/issues/detail?id=231
Another note: in the workaround of changing the group of /etc/sasldb2, the
group must be the primary group for the Memcached user (i.e. the one
Comment #6 on issue 231 by nelson.p...@gmail.com: SASL authentication not
working on reboot
http://code.google.com/p/memcached/issues/detail?id=231
I've had the same issue on Amazon 32bit standard Linux image (Centos). Let
me know if you would like any logs
Comment #5 on issue 231 by esoteric...@gmail.com: SASL authentication not
working on reboot
http://code.google.com/p/memcached/issues/detail?id=231
I thought about that, but SELinux is not enabled:
/etc/selinux/config:
# This file controls the state of SELinux on the system.
# SELINUX= can
Comment #4 on issue 231 by dsalli...@gmail.com: SASL authentication not
working on reboot
http://code.google.com/p/memcached/issues/detail?id=231
Sounds like you're using selinux and have a profile set up oddly.
Comment #3 on issue 231 by esoteric...@gmail.com: SASL authentication not
working on reboot
http://code.google.com/p/memcached/issues/detail?id=231
No, saslauthd is not running in either scenario. It's not configured to
start on boot and it's never started.
Comment #2 on issue 231 by dorma...@rydia.net: SASL authentication not
working on reboot
http://code.google.com/p/memcached/issues/detail?id=231
Is there some SASL service you have running which could be starting after
memcached?
Comment #1 on issue 231 by esoteric...@gmail.com: SASL authentication not
working on reboot
http://code.google.com/p/memcached/issues/detail?id=231
I tried with Memcached 1.4.6 and 1.4.9.
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 231 by esoteric...@gmail.com: SASL authentication not working on
reboot
http://code.google.com/p/memcached/issues/detail?id=231
What steps will reproduce the problem?
1. Update RPM spec with SASL enabled (configure option
15 matches
Mail list logo
