# After upgrade to 6.3.2, nothing emitted until 2nd retart

**URL:** https://discuss.elastic.co/t/after-upgrade-to-6-3-2-nothing-emitted-until-2nd-retart/141609
**Category:** Logstash
**Created:** [July 25, 2018, 3:06pm UTC](https://discuss.elastic.co/t/after-upgrade-to-6-3-2-nothing-emitted-until-2nd-retart/141609 "2018-07-25T15:06:52Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)
#### Post date: [July 25, 2018, 3:06pm UTC](https://discuss.elastic.co/t/after-upgrade-to-6-3-2-nothing-emitted-until-2nd-retart/141609/1 "2018-07-25T15:06:53Z")

</div>

I upgraded from logstash 6.2.2 to 6.3.2 (deleting queue directories). After first start, events were received but none showed emitted, queue files were growing in size. I couldn't find any errors, After restart, it looks OK.

The longer flat line is the first good start of 6.3.2. (the little blip is where it didn't run as root for port 514, my systemd error)

![image](https://us1.discourse-cdn.com/elastic/original/3X/2/1/21dd5faa44b47671d51ae64777c867bd0b94f908.png)

I have several logstash instances behind a network load balancer or in a beats list.

Is there any way to monitor the queue size in logstash?

---

<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: [August 22, 2018, 3:06pm UTC](https://discuss.elastic.co/t/after-upgrade-to-6-3-2-nothing-emitted-until-2nd-retart/141609/2 "2018-08-22T15:06:58Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.