Hey! I have a case where I run two logstash instances on the same system. In v5.0.0-alpha4, when the second one starts, it complains that the port 9600 is already taken. How about trying 9601? :smiley: -ave

Logstash http.port auto-increment?

warkolm (Mark Walkom) August 6, 2016, 4:48am 2

Topic		Replies	Views
Address already in use - Logstash tried to bind to port range 9600..9700, but all the ports are already in use Logstash	3	3054	April 11, 2017
Logstash tried to bind to port range 9600..9700, but all the ports are already in use. You can specify a new port by launching logstash with the --http.port option Logstash	1	888	April 4, 2020
Already used ports Logstash	2	520	October 12, 2018
Logstash restart error? Logstash	4	1266	July 6, 2017
Unable to run this command bin/logstash -e "input { http { port => 9200 } } output { stdout { codec => rubydebug} } Logstash	3	430	June 26, 2019