Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: This socket has been ended by the other party #18

Open
ManuelPU opened this issue Aug 9, 2013 · 0 comments
Open

Error: This socket has been ended by the other party #18

ManuelPU opened this issue Aug 9, 2013 · 0 comments

Comments

@ManuelPU
Copy link

ManuelPU commented Aug 9, 2013

one host , 2 connections 7111 as master 7112 slave

First 7111 as master and 7112 slave
kill 7111 ...

7112 becomes master without slaves

I start again 7111 and after that i will close 7112

It says that 7111 becomes master without slaves
I can enter to redis-cli -p 9999 but after some test of keys * , redis-proxy sends this error:

events.js:72
throw er; // Unhandled 'error' event
^
Error: This socket has been ended by the other party
at Socket.writeAfterFIN as write
at /home/manu/redis-proxy-master/lib/server.js:62:10

wankdanker added a commit to wankdanker/redis-proxy that referenced this issue Sep 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant