# Logstash does not output to elasticsearch, only "Flushing buffer at interval" in log

**URL:** https://discuss.elastic.co/t/logstash-does-not-output-to-elasticsearch-only-flushing-buffer-at-interval-in-log/41345
**Category:** Logstash
**Created:** [February 10, 2016, 3:46am UTC](https://discuss.elastic.co/t/logstash-does-not-output-to-elasticsearch-only-flushing-buffer-at-interval-in-log/41345 "2016-02-10T03:46:56Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![s0mb00n](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@s0mb00n](https://discuss.elastic.co/u/s0mb00n)
#### Post date: [February 10, 2016, 3:46am UTC](https://discuss.elastic.co/t/logstash-does-not-output-to-elasticsearch-only-flushing-buffer-at-interval-in-log/41345/1 "2016-02-10T03:46:56Z")

</div>

My logstash setup stopped outputting to Elasticsearch earlier today. When I run with `--debug` option, I don't see any error but only mostly the lines like the following:

```auto
{:timestamp=>"2016-02-10T03:29:43.431000+0000", :message=>"Flushing buffer at interval", :instance=>"#<LogStash::Outputs::ElasticSearch::Buffer:0x184f3551 @operations_mutex=#<Mutex:0x1688d828>, @max_size=500, @operations_lock=#<Java::JavaUtilConcurrentLocks::ReentrantLock:0x12b75e21>, @submit_proc=#<Proc:0x36b18009@/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.2.0-java/lib/logstash/outputs/elasticsearch/common.rb:55>, @logger=#<Cabin::Channel:0x66a8476f @metrics=#<Cabin::Metrics:0x4e464bcd @metrics_lock=#<Mutex:0x379a2d5c>, @metrics={}, @channel=#<Cabin::Channel:0x66a8476f ...>>, @subscriber_lock=#<Mutex:0xd11426e>, @level=:debug, @subscribers={12590=>#<Cabin::Outputs::IO:0x5542c156 @io=#<File:/data/debug.log>, @lock=#<Mutex:0x33d4f66f>>}, @data={}>, @last_flush=2016-02-10 03:29:42 +0000, @flush_interval=1, @stopping=#<Concurrent::AtomicBoolean:0x34d1c049>, @buffer=[], @flush_thread=#<Thread:0x2a150350 run>>", :interval=>1, :level=>:info, :file=>"logstash/outputs/elasticsearch/buffer.rb", :line=>"90", :method=>"interval_flush"}
{:timestamp=>"2016-02-10T03:29:44.433000+0000", :message=>"Flushing buffer at interval", :instance=>"#<LogStash::Outputs::ElasticSearch::Buffer:0x184f3551 @operations_mutex=#<Mutex:0x1688d828>, @max_size=500, @operations_lock=#<Java::JavaUtilConcurrentLocks::ReentrantLock:0x12b75e21>, @submit_proc=#<Proc:0x36b18009@/opt/logstash/vendor/bundle/jruby/1.9/gems/logstash-output-elasticsearch-2.2.0-java/lib/logstash/outputs/elasticsearch/common.rb:55>, @logger=#<Cabin::Channel:0x66a8476f @metrics=#<Cabin::Metrics:0x4e464bcd @metrics_lock=#<Mutex:0x379a2d5c>, @metrics={}, @channel=#<Cabin::Channel:0x66a8476f ...>>, @subscriber_lock=#<Mutex:0xd11426e>, @level=:debug, @subscribers={12590=>#<Cabin::Outputs::IO:0x5542c156 @io=#<File:/data/debug.log>, @lock=#<Mutex:0x33d4f66f>>}, @data={}>, @last_flush=2016-02-10 03:29:43 +0000, @flush_interval=1, @stopping=#<Concurrent::AtomicBoolean:0x34d1c049>, @buffer=[], @flush_thread=#<Thread:0x2a150350 run>>", :interval=>1, :level=>:info, :file=>"logstash/outputs/elasticsearch/buffer.rb", :line=>"90", :method=>"interval_flush"}

```

I confirm that Elasticsearch cluster that my logstash setup is talking to is up and running with `green` status and that there are no logstash-forwarder error in any of the machines that piped logs to my logstash setup.

Any help in how to debug and fix this issue would be greatly appreciated.

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [February 10, 2016, 6:02am UTC](https://discuss.elastic.co/t/logstash-does-not-output-to-elasticsearch-only-flushing-buffer-at-interval-in-log/41345/2 "2016-02-10T06:02:28Z")

</div>

It'd help if you provided your config 🙂

---

<div class="post-metadata">

### Author: ![s0mb00n](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@s0mb00n](https://discuss.elastic.co/u/s0mb00n)
#### Post date: [February 10, 2016, 5:52pm UTC](https://discuss.elastic.co/t/logstash-does-not-output-to-elasticsearch-only-flushing-buffer-at-interval-in-log/41345/3 "2016-02-10T17:52:46Z")

</div>

Thanks @warkolm. It turned out to be an underlying networking issue on my logstash host. After I reboot the machine, logstash is back up and operational. I guess I should have tried rebooting first 🙂. Thanks again.

---

<div class="post-metadata">

### Author: ![sukoon](https://avatars.discourse-cdn.com/v4/letter/s/e9bcb4/32.png) [@sukoon](https://discuss.elastic.co/u/sukoon)
#### Post date: [February 18, 2016, 10:38am UTC](https://discuss.elastic.co/t/logstash-does-not-output-to-elasticsearch-only-flushing-buffer-at-interval-in-log/41345/4 "2016-02-18T10:38:28Z")

</div>

Can you please provide a detailed explanation of your solution. I am getting the exact same error. What type of networking issue it was? How to reboot the machine?

---

<div class="post-metadata">

### Author: ![s0mb00n](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@s0mb00n](https://discuss.elastic.co/u/s0mb00n)
#### Post date: [February 29, 2016, 4:43am UTC](https://discuss.elastic.co/t/logstash-does-not-output-to-elasticsearch-only-flushing-buffer-at-interval-in-log/41345/5 "2016-02-29T04:43:47Z")

</div>

sure, basically, I just literally power off the machine and power back on and the problem went away. I found out later that some other engineer has been trying to run logstash and elasticsearch as docker containers in the same machine so that might have caused the original issue.

---

<div class="post-metadata">

### Author: ![sarbjeet](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sarbjeet](https://discuss.elastic.co/u/sarbjeet)
#### Post date: [April 22, 2016, 12:25pm UTC](https://discuss.elastic.co/t/logstash-does-not-output-to-elasticsearch-only-flushing-buffer-at-interval-in-log/41345/6 "2016-04-22T12:25:13Z")

</div>

Can you please provide a detailed explanation of your solution. I am getting the exact same error. What type of networking issue it was? How to reboot the machine?

---

<div class="post-metadata">

### Author: ![gayathri](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@gayathri](https://discuss.elastic.co/u/gayathri)
#### Post date: [August 17, 2016, 8:49am UTC](https://discuss.elastic.co/t/logstash-does-not-output-to-elasticsearch-only-flushing-buffer-at-interval-in-log/41345/7 "2016-08-17T08:49:10Z")

</div>

rebooted the server, but getting the same issue

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 4:43am UTC](https://discuss.elastic.co/t/logstash-does-not-output-to-elasticsearch-only-flushing-buffer-at-interval-in-log/41345/8 "2017-07-06T04:43:07Z")

</div>