Symptom
- Sometimes a mantis server appears to still be running in a tmux session, the connections/channels/queue/bindings all still appear in AMQP. Messages sent receive no response (I should check but am not sure if they are ack'd or just build up in the queue).
- When the server is sent a
ctrl+c it appears to exit cleanly, messages about being processed by signal handler and deallocating buffers all print, but the AMQP connection is still present and so the queue and bindings also remain, preventing restart until they are manually force closed.
Reproducing
I'm not certain what actually triggers this state. I've noticed it when I try to talk to a server which has been running for "a long time." This is using the test digitizer (though I'm not sure if that matters) and a build of commit b830fed (the 3.0.0 tag I believe). I've usually disconnected and reconnected the tmux session also, though I just tested and that alone does not cause this to recur.
Symptom
ctrl+cit appears to exit cleanly, messages about being processed by signal handler and deallocating buffers all print, but the AMQP connection is still present and so the queue and bindings also remain, preventing restart until they are manually force closed.Reproducing
I'm not certain what actually triggers this state. I've noticed it when I try to talk to a server which has been running for "a long time." This is using the test digitizer (though I'm not sure if that matters) and a build of commit b830fed (the 3.0.0 tag I believe). I've usually disconnected and reconnected the tmux session also, though I just tested and that alone does not cause this to recur.