# TCP output plugin blocking port across configuration reload **URL:** \ **Category:** Logstash\ **Created:** [January 10, 2019, 12:22pm UTC](https://discuss.elastic.co/t/tcp-output-plugin-blocking-port-across-configuration-reload/163732 "2019-01-10T12:22:01Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![vinayakshukre](https://avatars.discourse-cdn.com/v4/letter/v/58f4c7/32.png) [@vinayakshukre](https://discuss.elastic.co/u/vinayakshukre)\ **Post date:** [January 10, 2019, 12:22pm UTC](https://discuss.elastic.co/t/tcp-output-plugin-blocking-port-across-configuration-reload/163732/1 "2019-01-10T12:22:01Z")
Hello Logstash community members, I am relatively new to logstash and want to read data sent by TCP output plugin in my java code. My conf file is shown below. ``` input { tcp { port => 5518 type => "syslogType" } } filter{ grok{ // some grok is here. } } output{ tcp { host => "localhost" port => 5519 mode => "server" codec => "json_lines" } file { path => "/tmp/preview.txt" codec => "json" } } ``` This works fine but I also have a requirement to change the grok written in the conf file without logstash restart. To achieve this I edit conf file on the fly using vi editor. I have **config.reload.automatic: true** and have 2 pipelines defined in pipelines.yml in logstash version 6.5.3 OSS on my Ubuntu machine. When Logstash tries to reload the configuration, I get below error. ``` Jan 10 17:30:57 my-pc logstash[30898]: [2019-01-10T17:30:57,413][INFO][logstash.pipelineaction.reload] Reloading pipeline {"pipeline.id"=>:preview_pipeline} Jan 10 17:31:02 my-pc logstash[30898]: [2019-01-10T17:31:02,493][WARN][org.logstash.execution.ShutdownWatcherExt] {"inflight_count"=>0, "stalling_threads_info"=>{}} Jan 10 17:31:02 my-pc logstash[30898]: [2019-01-10T17:31:02,501][ERROR][org.logstash.execution.ShutdownWatcherExt] The shutdown process appears to be stalled due to busy or blocked plugins. Check the logs for more information. Jan 10 17:31:02 my-pc logstash[30898]: [2019-01-10T17:31:02,802][INFO][logstash.pipeline] Pipeline has terminated {:pipeline_id=>"preview_pipeline", :thread=>"#"} Jan 10 17:31:02 my-pc logstash[30898]: [2019-01-10T17:31:02,925][INFO][logstash.pipeline] Starting pipeline {:pipeline_id=>"preview_pipeline", "pipeline.workers"=>1, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50} Jan 10 17:31:02 my-pc logstash[30898]: [2019-01-10T17:31:02,932][INFO][logstash.outputs.tcp] Starting tcp output listener {:address=>"localhost:5519"} Jan 10 17:31:02 my-pc logstash[30898]: [2019-01-10T17:31:02,936][ERROR][logstash.outputs.tcp] Could not start TCP server: Address in use {:host=>"localhost", :port=>5519} Jan 10 17:31:02 my-pc logstash[30898]: [2019-01-10T17:31:02,944][ERROR][logstash.pipeline] Error registering plugin {:pipeline_id=>"preview_pipeline", :plugin=>"#", :error=>"Address already in use - bind - Address already in use", :thread=>"#"} Jan 10 17:31:02 my-pc logstash[30898]: [2019-01-10T17:31:02,949][ERROR][logstash.pipeline] Pipeline aborted due to error {:pipeline_id=>"preview_pipeline", :exception=>#, :backtrace=>["org/jruby/ext/socket/RubyTCPServer.java:127:in `initialize'", "org/jruby/RubyIO.java:875:in `new'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-tcp-5.0.3/lib/logstash/outputs/tcp.rb:115:in `register'", "org/logstash/config/ir/compiler/OutputStrategyExt.java:102:in `register'", "org/logstash/config/ir/compiler/AbstractOutputDelegatorExt.java:46:in `register'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:242:in `register_plugin'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:253:in `block in register_plugins'", "org/jruby/RubyArray.java:1734:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:253:in `register_plugins'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:594:in `maybe_setup_out_plugins'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:263:in `start_workers'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:200:in `run'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:160:in `block in start'"], :thread=>"#"} Jan 10 17:31:02 my-pc logstash[30898]: [2019-01-10T17:31:02,961][ERROR][logstash.agent] Failed to execute action {:id=>:preview_pipeline, :action_type=>LogStash::ConvergeResult::FailedAction, :message=>"Could not execute action: PipelineAction::Create, action_result: false", :backtrace=>nil} ``` Can someone please help me identify why on reloading configuration logstash does not release the port 5519 which is my output port ? If I stop the logstash service and start it again then everything works fine. I want same to happen with conf reload. Please help. Thanks. ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [January 10, 2019, 3:40pm UTC](https://discuss.elastic.co/t/tcp-output-plugin-blocking-port-across-configuration-reload/163732/2 "2019-01-10T15:40:06Z")
Feels like a bug to me. Looking at the [code](https://github.com/logstash-plugins/logstash-output-tcp/blob/9603fbefee3117ab31da2982d78516fb7059957d/lib/logstash/outputs/tcp.rb#L116), it never closes a server socket. So if it restarts the previous instance is still listening. ---
**Author:** ![vinayakshukre](https://avatars.discourse-cdn.com/v4/letter/v/58f4c7/32.png) [@vinayakshukre](https://discuss.elastic.co/u/vinayakshukre)\ **Post date:** [January 11, 2019, 8:36am UTC](https://discuss.elastic.co/t/tcp-output-plugin-blocking-port-across-configuration-reload/163732/3 "2019-01-11T08:36:44Z")
Thanks for your reply. Good to know that this is bug. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 8, 2019, 8:51am UTC](https://discuss.elastic.co/t/tcp-output-plugin-blocking-port-across-configuration-reload/163732/4 "2019-02-08T08:51:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.