CanBeClosed
Mizuno replaced by FTW so this issue should be solved now.

Alternately, instead of removing the 'trap' method, could be easier instead to wrap 'trap' (with method aliasing) and have it ignore all calls that come from mizuno (inspect 'caller' to see where we are being invoked from)

Thinking a bit about this, I'm not totally sure how to proceed. Some options:

• monkeypatch the webserver (doesn't look trivial: https://github.com/matadon/mizuno/blob/master/lib/mizuno/http_server.rb#L72

• Replace Kernel::trap with a dummy function that does nothing, so mizuno cannot trap SIGINT.

• use another webserver (seems less awesome)

• fork mizuno (not a pleasant option)

• send patches to disable the SIGINT stuff which someone probably wants to keep

I think the best option is probably to replace 'trap' with a bogus method, making it so only logstash can capture SIGINT.

This is mainly due to a misfeature in the webserver logstash uses. It steals SIGINT handling so logstash cannot use it.

It's on my todo list to fix it. In the meantime, SIGTERM will work. I'll fix this soon 🙂

heya,

I can confirm I appear to have this issue as well.

I start logstash with:

[victorhooi@myhost Downloads]$ sudo java -jar logstash-1.1.0beta3-monolithic.jar agent -f mylogstash.conf – web --backend elasticsearch:///?local

(I need to use sudo in order to read /var/log/*.log).

Then, when I use Ctrl-C to kill it, it simply prints out:

2011-10-05 00:46:45.318:INFO::stopped o.e.j.s.ServletContextHandler{/,null}

and I need to manually kill the terminal to kill it.

Cheers,
Victor