Closed cmosguy closed 9 years ago
Does this happen every time you send or when terminating the program (for example CTRL+C)?
Hi @mkoppanen, thanks for getting back to me.
This is happening when i am running my script from a command line tool called tinker . I have not tried it from a script or anything like that, just from this interactive shell. I am assuming the same results if I use it from the script.
Is there a way to debug this? What is going on behind the scenes with zmq to result this error do you think?
Thanks
It's not ZMQ's fault in this case, it's most likely something that the mentioned utility does. Is it forking at any point?
@Majeh and @mkoppanen looks like you guys are right. It isn't ZMQ, it is the stupid tinker system I am using that is screwing things up. I should have tested this with an isolated test in a script. Thanks for your help!
@mkoppanen I have the same problem when using ZMQ with Swoole (which seems to fork php processes) ... Is this extension compatible with such a use case?
Not to turn this into stackoverflow, but for future folks finding themselves here, you may seek to reorganize your code to bind
or connect
AFTER your fork occurs.
Moving my $rep->connect("ipc://" . self::ZQM_SOCKET_PATH);
to a function call after I forked has solved the problem.
yeah, I figured that as well, but I think, that that's just a workaround, isn't it?
I am not sure what I could possibly be doing wrong here. I am implementing a simple zmq message into my ratchet websocket framework.
I am getting the error message:
Not sure what I am doing wrong here. Here is the server code:
Then when i am trying to send the message or update for the request I have the following:
I don't understand how to debug this and what is going on with the handling of the ZMQ messages. Can someone please advise how I could fix this issue?
Thanks!