Re: Issue 339 in memcached: Segmentation fault - on replication - freebsd

2013-12-07 Thread memcached

Updates:
Status: Invalid

Comment #1 on issue 339 by dorma...@rydia.net: Segmentation fault - on  
replication - freebsd

http://code.google.com/p/memcached/issues/detail?id=339

The replication patch is unsupported, sorry.

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

--- 
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/groups/opt_out.


Issue 339 in memcached: Segmentation fault - on replication - freebsd

2013-08-23 Thread memcached

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 339 by rabcz...@googlemail.com: Segmentation fault - on  
replication - freebsd

http://code.google.com/p/memcached/issues/detail?id=339

What steps will reproduce the problem?
1. memcached -p 11211 -m 64 -x 127.0.0.1 -vvv -u nobody
2. memcached -p 11222 -m 64 -x 127.0.0.1 -v -u nobody

What is the expected output? What do you see instead?

On master:
replication: start
REP16 OK
16: going from conn_parse_cmd to conn_new_cmd
16: going from conn_new_cmd to conn_waiting
16: going from conn_waiting to conn_read
20 server listening (udp)
20 server listening (udp)
20 server listening (udp)
20 server listening (udp)
21 new auto-negotiating client connection
21: going from conn_new_cmd to conn_waiting
21: going from conn_waiting to conn_read
21: going from conn_read to conn_parse_cmd
21: Client using the ascii protocol
21 get 2e948d53e053a7a36ba02f2c7effaa0e

NOT FOUND 2e948d53e053a7a36ba02f2c7effaa0e
21 END

21: going from conn_parse_cmd to conn_mwrite
21: going from conn_mwrite to conn_new_cmd
21: going from conn_new_cmd to conn_waiting
21: going from conn_waiting to conn_read
21: going from conn_read to conn_parse_cmd
21 set 2e948d53e053a7a36ba02f2c7effaa0e 3 180 1765
21: going from conn_parse_cmd to conn_nread

NOT FOUND 2e948d53e053a7a36ba02f2c7effaa0e

replication: alloc c=1

21 STORED

21: going from conn_nread to conn_write
replication: pop
21: going from conn_write to conn_new_cmd
21: going from conn_new_cmd to conn_waiting
21: going from conn_waiting to conn_read
Segmentation fault

Slave is working well

What version of the product are you using? On what operating system?
libevent-1.4.14b_2, memcached-1.4.15 , freebsd 9.1-p6 , installed from  
ports.





--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

--- 
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/groups/opt_out.