stdout.log

[INFO] (src/control.rl:207) Setting up control socket in at ipc://run/control
[INFO] (src/handler.c:202) MAX allowing limits.handler_targets=128
[INFO] (src/handler.c:275) Binding handler PUSH socket tcp://127.0.0.1:9997 with identity: test
[INFO] (src/handler.c:297) Binding listener SUB socket tcp://127.0.0.1:9996 subscribed to: test
^C[INFO] (src/mongrel2.c:83) SHUTDOWN REQUESTED: GRACEFUL (SIGINT again to EXIT NOW)
[ERROR] (src/task/net.c:241: errno: Bad file descriptor) Failed calling accept on socket that was ready.
[INFO] (src/mongrel2.c:312) Shutdown requested, goodbye.
[ERROR] (src/handler.c:169: errno: Resource temporarily unavailable) Receive on handler socket failed.
[INFO] (src/mongrel2.c:252) Waiting for connections to die: -1
[INFO] (src/mongrel2.c:261) Removing pid file ./run/mongrel2.pid
[ERROR] (src/log.c:54: errno: Unknown error: 156384765) Failed to receive from the zeromq logging socket.
^C[INFO] (src/mongrel2.c:79) SIGINT CAUGHT AGAIN, ASSUMING MURDER.


# Then I have to `ctrl+z` add `kill -9 %1`

156384765 is ETERM. It means that socket is being accessed after zmq_term was called.

Yo, i also encountered this problem. Were you able to figure out how to fix it?

looks like a mongrel2 issue

It occurs when using mongrel2 and zeromq 2.1.x. Zed is working on making mongrel2 work with the new zeromq stuff though.

The solution is to use zeromq 2.0.x.

Yo, thanks for the feedback. I updated to the latest master branch, and i think it's already fixed in this version.