# Logging to logstash gets timeout from laravel application once the logstash instance(EC2) goes down

**URL:** <https://discuss.elastic.co/t/logging-to-logstash-gets-timeout-from-laravel-application-once-the-logstash-instance-ec2-goes-down/322456>\
**Category:** Logstash\
**Created:** [January 4, 2023, 11:40am UTC](https://discuss.elastic.co/t/logging-to-logstash-gets-timeout-from-laravel-application-once-the-logstash-instance-ec2-goes-down/322456 "2023-01-04T11:40:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![yuguerthen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuguerthen/32/115539_2.png) [@yuguerthen](https://discuss.elastic.co/u/yuguerthen)\
**Post date:** [January 4, 2023, 11:40am UTC](https://discuss.elastic.co/t/logging-to-logstash-gets-timeout-from-laravel-application-once-the-logstash-instance-ec2-goes-down/322456/1 "2023-01-04T11:40:54Z")

</div>

Hello, I have a Laravel application that sends log data to Logstash on an AWS EC2 instance. Recently, the EC2 instance went down, and I noticed that the Laravel application started prompting timeouts when I tried to log which affects the whole laravel application. Is there a way to configure Laravel or Logstash to handle timeouts or connection failures, or do I need to handle this in my log shipping solution? i get this error :

```auto
Failed connecting to tcp://34.244.71.62:5044 (111: Connection refused)

```

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [January 4, 2023, 12:27pm UTC](https://discuss.elastic.co/t/logging-to-logstash-gets-timeout-from-laravel-application-once-the-logstash-instance-ec2-goes-down/322456/2 "2023-01-04T12:27:03Z")

</div>

If the Logstash being down impacts your application, this is an issue on the application, you need to handle it in your code.

---

<div class="post-metadata">

**Author:** ![yuguerthen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuguerthen/32/115539_2.png) [@yuguerthen](https://discuss.elastic.co/u/yuguerthen)\
**Post date:** [January 4, 2023, 1:53pm UTC](https://discuss.elastic.co/t/logging-to-logstash-gets-timeout-from-laravel-application-once-the-logstash-instance-ec2-goes-down/322456/3 "2023-01-04T13:53:28Z")

</div>

thanks for your reply, should i place this question somewhere else ?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [January 4, 2023, 6:04pm UTC](https://discuss.elastic.co/t/logging-to-logstash-gets-timeout-from-laravel-application-once-the-logstash-instance-ec2-goes-down/322456/4 "2023-01-04T18:04:55Z")

</div>

> [@yuguerthen](#):
>
> thanks for your reply, should i place this question somewhere else ?

Probably on a Laravel/PHP community since it is related to your code and it is not a Logstash 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:** [February 1, 2023, 6:05pm UTC](https://discuss.elastic.co/t/logging-to-logstash-gets-timeout-from-laravel-application-once-the-logstash-instance-ec2-goes-down/322456/5 "2023-02-01T18:05:53Z")

</div>

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