Assertion failed: (msg_->flags | ZMQ_MSG_MASK) == 0xff (zmq.cpp:223)

[ghost]

Going from 2.1.4 to 2.1.6 has been an utter disaster for me. Relatively simplistic TCP communications between processes give me a never-ending stream of:

Assertion failed: (msg_->flags | ZMQ_MSG_MASK) == 0xff (zmq.cpp:223)

and

Assertion failed: rc == 0 (zmq_connecter.cpp:48)

Trying to connect to a server running 2.1.6 from a client running 2.1.4 will also kill the server.

[sustrik]

The first problem is that you are trying to get size of an uninitialised invalid or closed message.

The second problem is a known bug. It's caused by 0mq not being able to resolve the connection string you pass to connect.

[krishnenc]

Hello,

I have been trying the examples for C from the zguide and the first PUB-SUB example (wuclient and wuserver) crashes with the error Assertion failed: (msg_->flags | ZMQ_MSG_MASK) == 0xff (zmq.cpp:223) , but only when the the client and server are on different machines.

The server emits on tcp://*:5556
The client listens on tcp://192.168.1.5:5556

The server crashes when the clients connects.

My setup is server runs on macosx 10.6.7 and client runs on ubuntu 10.10 on a virtualbox guest.
Both are running version 2.1.6 of zeromq

Any ideas?

Thks,
Krishnen

[krishnenc]

I reverted to 2.1.4 and i can confirm that it now works with the same setup.Maybe its an issue on 2.1.6?? Am a newbie to all of this , please let me know if am posting to the wrong channel.
Thks.

[ghost]

I could buy the inability to resolve the name being used to connect if I weren't using 127.0.0.1 on both the binder and the connector. As for why the library is trying to get the size of an invalid or closed message, I can't offer any explanation. My code is not doing anything even close to that level, so unless there's an incompatibility with the Python bindings, I'd have to maintain that this is a bug in 2.1.6.

[hintjens]

I've pushed a fix that should resolve this issue. Can you please take the zeromq2-1 master at http://github.com/zeromq/zeromq2-1 and retest? If you can confirm the fix, I'll include it in the 2.1.7 release.

[trbs]

For me the issue is fixed with the above repository.
Thanks!

[hintjens]

Great, thanks!