# Logstash Even Hub input. error when running as a service, but not when I run single pipeline

**URL:** <https://discuss.elastic.co/t/logstash-even-hub-input-error-when-running-as-a-service-but-not-when-i-run-single-pipeline/298423>\
**Category:** Logstash\
**Created:** [February 28, 2022, 3:43pm UTC](https://discuss.elastic.co/t/logstash-even-hub-input-error-when-running-as-a-service-but-not-when-i-run-single-pipeline/298423 "2022-02-28T15:43:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ElasticLiver](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elasticliver/32/64869_2.png) [@ElasticLiver](https://discuss.elastic.co/u/ElasticLiver)\
**Post date:** [February 28, 2022, 3:43pm UTC](https://discuss.elastic.co/t/logstash-even-hub-input-error-when-running-as-a-service-but-not-when-i-run-single-pipeline/298423/1 "2022-02-28T15:43:10Z")

</div>

Hi Im trying to consume data from Azure Event Hub, I have 15 different logstash pipelines pointing to different storages, and Even Hubs, they all work well,and I can get data when I run the single pipelines alone, but when I run the pipelines.yml or logstash as a service I get this error on all pipelines

```auto
][logstash.inputs.azureeventhubs
][metrics-bkp-arzo
][ece431cc89008326a8e46c6b0e0ec28357f92c64c183e722de71771ea1aca4c8
] Event Hub encountered an error. {
    :event_hub_name=>"eve-arzo",
    :exception=>java.util.concurrent.CompletionException: com.microsoft.azure.eventhubs.IllegalEntityException: Failure getting partition ids for event hub,
    :backtrace=>[
        "com.microsoft.azure.eventprocessorhost.PartitionManager.lambda$cachePartitionIds$4(PartitionManager.java:80)",
        "java.base/java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:930)",
        "java.base/java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:907)",
        "java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:478)",
        "java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)",
        "java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)",
        "java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)",
        "java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)",
        "java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)",
        "java.base/java.lang.Thread.run(Thread.java:829)"
    ]
}

```

This in one of my logstash inputs:

```auto
input {
   azure_event_hubs {
     codec => json{ }
     decorate_events => true
     config_mode => "advanced"

     storage_connection => "<redacted>"
     event_hubs => [{
     "eventb" => {
     event_hub_connection => "<redacted>"

     initial_position => "beginning"
     consumer_group => "eventb"
     storage_container => "stglogsb"
        }
     }]

   }
}

```

At the end I receive these messages and nothing else happens

```auto
[
    2022-02-28T10: 47: 36,
    866
][WARN
][com.microsoft.azure.eventhubs.impl.MessagingFactory
][<pipeline-name>
][14edef9298d9eecd0699f2ef64afda41428d26d85c7f02d7fb62fa
] messagingFactory[MessagingFactory5d2108
], hostName[eventallpa.servicebus.windows.net
], message[Processing all pending tasks and closing old reactor.
]
[
    2022-02-28T10: 47: 36,
    866
][INFO
][com.microsoft.azure.eventhubs.impl.ReactorHandler
][<pipeline-name>
][14edef9298d9eecd0699f2ef64afda41428d26d85c7f02d7fb62fa
] reactor.onReactorFinal

```

---

<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:** [March 28, 2022, 3:44pm UTC](https://discuss.elastic.co/t/logstash-even-hub-input-error-when-running-as-a-service-but-not-when-i-run-single-pipeline/298423/2 "2022-03-28T15:44:04Z")

</div>

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