I believe this is the same bug reported in the python bindings here:
I noticed this with separate erlzmq contexts both binding to the same ipc, where one would fail silently, and then refuse to work. This may have worked in past versions of ZeroMQ somehow, but does not work now. The second attempt should just spit back an error.
Do you have a pull request ;)?
Actually, reading about it more seems to indicate that this is a ZeroMQ bug. I will try to find more references to it, to try and determine when it will be fixed. I was testing with the latest versions of v2 and v3, so it is a problem in their latest code right now.
So, this looks like an issue that is with the underlying zeromq C library, so it really is best fixed there. I believe it is as simple as checking for the existence of the file, but they seem to have ignored the issue on the mailing list. Either way, this shouldn't be an issue with erlzmq2.