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. > > export SASL_CONF_PATH=$HOME/saslmemcached/memcached.conf > > export MEMCACHED_SASL_PWDB=$HOME/saslmemcached/memcached-sasl.db > > Initialized SASL. > slab class 1: chunk size 96 perslab 10922 > slab class 2: chunk size 120 perslab 8738 > slab class 3: chunk size 152 perslab 6898 > slab class 4: chunk size 192 perslab 5461 > slab class 5: chunk size 240 perslab 4369 > slab class 6: chunk size 304 perslab 3449 > slab class 7: chunk size 384 perslab 2730 > slab class 8: chunk size 480 perslab 2184 > slab class 9: chunk size 600 perslab 1747 > slab class 10: chunk size 752 perslab 1394 > slab class 11: chunk size 944 perslab 1110 > slab class 12: chunk size 1184 perslab 885 > slab class 13: chunk size 1480 perslab 708 > slab class 14: chunk size 1856 perslab 564 > slab class 15: chunk size 2320 perslab 451 > slab class 16: chunk size 2904 perslab 361 > slab class 17: chunk size 3632 perslab 288 > slab class 18: chunk size 4544 perslab 230 > slab class 19: chunk size 5680 perslab 184 > slab class 20: chunk size 7104 perslab 147 > slab class 21: chunk size 8880 perslab 118 > slab class 22: chunk size 11104 perslab 94 > slab class 23: chunk size 13880 perslab 75 > slab class 24: chunk size 17352 perslab 60 > slab class 25: chunk size 21696 perslab 48 > slab class 26: chunk size 27120 perslab 38 > slab class 27: chunk size 33904 perslab 30 > slab class 28: chunk size 42384 perslab 24 > slab class 29: chunk size 52984 perslab 19 > slab class 30: chunk size 66232 perslab 15 > slab class 31: chunk size 82792 perslab 12 > slab class 32: chunk size 103496 perslab 10 > slab class 33: chunk size 129376 perslab 8 > slab class 34: chunk size 161720 perslab 6 > slab class 35: chunk size 202152 perslab 5 > slab class 36: chunk size 252696 perslab 4 > slab class 37: chunk size 315872 perslab 3 > slab class 38: chunk size 394840 perslab 2 > slab class 39: chunk size 524288 perslab 2 > <46 server listening (binary) > <47 server listening (binary) > <48 send buffer was 129024, now 268435456 > <56 send buffer was 129024, now 268435456 > <48 server listening (udp) > <56 server listening (udp) > <49 server listening (udp) > <57 server listening (udp) > <50 server listening (udp) > <58 server listening (udp) > <51 server listening (udp) > <59 server listening (udp) > <52 server listening (udp) > <60 server listening (udp) > <53 server listening (udp) > <61 server listening (udp) > <54 server listening (udp) > <62 server listening (udp) > <55 server listening (udp) > <63 server listening (udp) > <64 new binary client connection. > 64: going from conn_new_cmd to conn_waiting > 64: going from conn_waiting to conn_read > 64: going from conn_read to conn_parse_cmd > <64 Read binary protocol data: > <64 0x80 0x21 0x00 0x05 > <64 0x00 0x00 0x00 0x00 > <64 0x00 0x00 0x00 0x1f > <64 0x00 0x01 0x2c 0xae > <64 0x00 0x00 0x00 0x00 > <64 0x00 0x00 0x00 0x00 > authenticated() in cmd 0x21 is true > 64: going from conn_parse_cmd to conn_nread > mech: ``PLAIN'' with 26 bytes of data > INFO: User <u...@localhost.socksnet.com> failed to authenticate > SASL (severity 1): unable to open Berkeley db /etc/sasldb2: No such file or > directory > SASL (severity 1): unable to open Berkeley db /etc/sasldb2: No such file or > directory > SASL (severity 2): Password verification failed > sasl result code: -20 > Unknown sasl response: -20 > >64 Writing an error: Auth failure. > >64 Writing bin response: > >64 0x81 0x21 0x00 0x00 > >64 0x00 0x00 0x00 0x20 > >64 0x00 0x00 0x00 0x0d > >64 0x00 0x01 0x2c 0xae > >64 0x00 0x00 0x00 0x00 > >64 0x00 0x00 0x00 0x00 > 64: going from conn_nread to conn_mwrite > 64: going from conn_mwrite to conn_new_cmd > 64: going from conn_new_cmd to conn_waiting > 64: going from conn_waiting to conn_read > 64: going from conn_read to conn_closing > <64 connection closed. > 64: going from conn_closing to conn_closed > <64 new binary client connection. > 64: going from conn_new_cmd to conn_waiting > 64: going from conn_waiting to conn_read > 64: going from conn_read to conn_parse_cmd > <64 Read binary protocol data: > <64 0x80 0x21 0x00 0x05 > <64 0x00 0x00 0x00 0x00 > <64 0x00 0x00 0x00 0x1f > <64 0x00 0x01 0x2c 0xb4 > <64 0x00 0x00 0x00 0x00 > <64 0x00 0x00 0x00 0x00 > authenticated() in cmd 0x21 is true > 64: going from conn_parse_cmd to conn_nread > mech: ``PLAIN'' with 26 bytes of data > INFO: User <u...@localhost.socksnet.com> failed to authenticate > SASL (severity 1): unable to open Berkeley db /etc/sasldb2: No such file or > directory > SASL (severity 1): unable to open Berkeley db /etc/sasldb2: No such file or > directory > SASL (severity 2): Password verification failed > sasl result code: -20 > Unknown sasl response: -20 > > > > On Tue, Apr 25, 2017 at 5:23 PM, dormando <dorma...@rydia.net> wrote: > 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 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/memcached;make;make > install > > > > echo "user@hostname:pass" >memcached-sasl-db > > > > echo "mech_list: plain" >memcached.conf > > > > export MEMCACHED_SASL_PWDB=$HOME/memcached/memcached-sasl-db > > > > export SASL_CONF_PATH=$HOME//memcached/memcached.conf > > > > ./memcached -S -B binary -vvv > > > > > > Can you please provide help me on this issue? > > > > > > Thank you, > > > > > > > > -- > > > > --- > > 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. > > > > > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "memcached" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/memcached/br9gX3NID3A/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > memcached+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > -- > > --- > 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. > > -- --- 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.
