# No configuration found in the configured sources

**URL:** <https://discuss.elastic.co/t/no-configuration-found-in-the-configured-sources/258029>\
**Category:** Logstash\
**Tags:** docker\
**Created:** [December 8, 2020, 4:46pm UTC](https://discuss.elastic.co/t/no-configuration-found-in-the-configured-sources/258029 "2020-12-08T16:46:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![djb000m](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/djb000m/32/67940_2.png) [@djb000m](https://discuss.elastic.co/u/djb000m)\
**Post date:** [December 8, 2020, 4:46pm UTC](https://discuss.elastic.co/t/no-configuration-found-in-the-configured-sources/258029/1 "2020-12-08T16:46:48Z")

</div>

Hi,

I am running the standard 7.10.0 Logstash docker container and I want to use it to do its thing and send data on to an ECE elastic deployment.

I'm running into an odd error that I cannot find a solution for. When I start the container it throws the following error `[ERROR][logstash.config.sourceloader] No configuration found in the configured sources.`

I have logstash.yml and pipelines.yml file configured and mapped to /usr/share/logstash/config, individual cfg files mapped to /usr/share/logstash/pipeline

Here are the files:

```auto
## docker-compose.yml
version: "3.7"

services:
  logstash:
    image: docker.elastic.co/logstash/logstash:7.10.0
    container_name: logstash
    # restart: unless-stopped
    volumes:
      - /home/admin/docker/logstash/config/:/usr/share/logstash/config/:ro
      - /home/admin/docker/logstash/pipeline/:/usr/share/logstash/pipeline/
      - /home/admin/docker/certs/:/usr/share/logstash/config/certs/:ro
    ports:
      - "60000:8080"
      - "5044:5044"
      - "9600:9600"
    networks:
      - elastic-services

  metricbeat:
    image: docker.elastic.co/beats/metricbeat:7.10.0
    container_name: metricbeat
    # restart: unless-stopped
    command: ["--strict.perms=false"]
    user: root
    volumes:
      - /home/admin/docker/metricbeat/config/metricbeat.docker.yml:/usr/share/metricbeat/metricbeat.yml
      - /home/admin/docker/certs:/usr/share/metricbeat/config/certs
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /sys/fs/cgroup:/hostfs/sys/fs/cgroup:ro
      - /proc:/hostfs/proc:ro
      - /:/hostfs:ro
    network_mode: host

networks:
  elastic-services:
    name: elastic-services

```

```auto
## logstash.yml
log.level: "debug"
config.debug: true

http.host: 0.0.0.0
node.name: "logstash-1"
# config.reload.automatic: true
monitoring.enabled: false
pipeline.ecs_compatibility: v1
xpack:
  management:
    enabled: true
    elasticsearch:
      hosts: https://abcdef0123456789.ece.example.com:9243
      username: elastic
      password: password
      ssl:
        certificate_authority: /usr/share/logstash/config/certs/ca_ece.example.com.pem
        verification_mode: certificate

```

```auto
## pipelines.yml
- pipeline.id: main
  path.config: "/usr/share/logstash/pipeline/test.cfg"

```

```auto
## test.cfg
input {
  http {
    port => 60000
    response_headers => {
      "Access-Controle-Allow-Origin" => "*"
      "Content-Type" => "application/json"
      "Acess-Control-Allow-Headers" => "Origin, X-Requested-With, Content-Type, Accept"
    }
  }
}

output {
  elasticsearch {
    hosts => ["https://abcdef0123456789.ece.example.com:9243"]
    index => "test"
    user => "elastic"
    password => "password"
    ssl => true
    ssl_certificate_verification => none
    cacert => "/usr/share/logstash/config/certs/ca_ece.example.com.pem"
  }
}

```

```auto
logstash | [2020-12-08T16:51:45,122][DEBUG][org.apache.http.headers] http-outgoing-3 << HTTP/1.1 200 OK
logstash | [2020-12-08T16:51:45,122][DEBUG][org.apache.http.headers] http-outgoing-3 << Content-Encoding: gzip
logstash | [2020-12-08T16:51:45,122][DEBUG][org.apache.http.headers] http-outgoing-3 << Content-Length: 93
logstash | [2020-12-08T16:51:45,122][DEBUG][org.apache.http.headers] http-outgoing-3 << Content-Type: application/json; charset=UTF-8
logstash | [2020-12-08T16:51:45,122][DEBUG][org.apache.http.headers] http-outgoing-3 << X-Cloud-Request-Id: H9D2FmzqQYG-BOt_ttc0pA
logstash | [2020-12-08T16:51:45,122][DEBUG][org.apache.http.headers] http-outgoing-3 << X-Found-Handling-Cluster: 988449793d6040a3aae51e71dcbf2afe
logstash | [2020-12-08T16:51:45,122][DEBUG][org.apache.http.headers] http-outgoing-3 << X-Found-Handling-Instance: instance-0000000000
logstash | [2020-12-08T16:51:45,122][DEBUG][org.apache.http.headers] http-outgoing-3 << Date: Tue, 08 Dec 2020 16:51:45 GMT
logstash | [2020-12-08T16:51:45,122][DEBUG][org.apache.http.impl.execchain.MainClientExec] Connection can be kept alive indefinitely
logstash | [2020-12-08T16:51:45,122][DEBUG][org.apache.http.impl.auth.HttpAuthenticator] Authentication succeeded
logstash | [2020-12-08T16:51:45,122][DEBUG][org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection [id: 3][route: {s}->https://abcdef0123456789.ece.example.com:9243] can be kept alive indefinitely
logstash | [2020-12-08T16:51:45,123][DEBUG][org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection released: [id: 3][route: {s}->https://abcdef0123456789.ece.example.com:9243][total kept alive: 1; route allocated: 1 of 100; total allocated: 1 of 1000]
logstash | [2020-12-08T16:51:45,123][DEBUG][logstash.configmanagement.elasticsearchsource] Could not find a remote configuration for a specific `pipeline_id` {:pipeline_id=>"main"}
logstash | [2020-12-08T16:51:45,123][ERROR][logstash.config.sourceloader] No configuration found in the configured sources.
logstash | [2020-12-08T16:51:45,123][DEBUG][logstash.agent] Converging pipelines state {:actions_count=>0}
logstash | [2020-12-08T16:51:49,887][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ParNew"}
logstash | [2020-12-08T16:51:49,887][DEBUG][logstash.instrument.periodicpoller.jvm] collector name {:name=>"ConcurrentMarkSweep"}
logstash | [2020-12-08T16:51:50,111][DEBUG][org.apache.http.client.protocol.RequestAuthCache] Re-using cached 'basic' auth scheme for https://abcdef0123456789.ece.example.com:9243
logstash | [2020-12-08T16:51:50,111][DEBUG][org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection request: [route: {s}->https://abcdef0123456789.ece.example.com:9243][total kept alive: 1; route allocated: 1 of 100; total allocated: 1 of 1000]
logstash | [2020-12-08T16:51:50,111][DEBUG][org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection leased: [id: 3][route: {s}->https://abcdef0123456789.ece.example.com:9243][total kept alive: 0; route allocated: 1 of 100; total allocated: 1 of 1000]

```

I'd appreciate any insight into this. I've been going at it for a few hours and just seem to be going around in circles.

Thanks.

[edit] I'm not really sure what's going on with the code formatting, sorry it's a bit funky.

---

<div class="post-metadata">

**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:** [December 8, 2020, 5:22pm UTC](https://discuss.elastic.co/t/no-configuration-found-in-the-configured-sources/258029/2 "2020-12-08T17:22:17Z")

</div>

> [@djb000m](#):
>
> ```auto
> xpack:
> management:
> enabled: true
> 
> ```

You have [told logstash](https://www.elastic.co/guide/en/logstash/current/configuring-centralized-pipelines.html) to look in elasticsearch for the configuration. That is why you get `[logstash.configmanagement.elasticsearchsource] Could not find a remote configuration`. It is not looking at pipelines.yml.

---

<div class="post-metadata">

**Author:** ![djb000m](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/djb000m/32/67940_2.png) [@djb000m](https://discuss.elastic.co/u/djb000m)\
**Post date:** [December 8, 2020, 5:37pm UTC](https://discuss.elastic.co/t/no-configuration-found-in-the-configured-sources/258029/3 "2020-12-08T17:37:00Z")

</div>

Ok, thanks @Badger, I didn't realise that the management UI feature supplanted all local configs.

I have a pipeline configured through the Kibana Pipelines UI and I'm still getting the same errors. Is there anything else that may be causing them?

---

<div class="post-metadata">

**Author:** ![djb000m](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/djb000m/32/67940_2.png) [@djb000m](https://discuss.elastic.co/u/djb000m)\
**Post date:** [December 10, 2020, 2:28pm UTC](https://discuss.elastic.co/t/no-configuration-found-in-the-configured-sources/258029/4 "2020-12-10T14:28:27Z")

</div>

I've gone back to managing my pipelines via config files and pipelines.yml.  
It's all working fine now, when I have time I might try the new UI.

---

<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:** [January 7, 2021, 2:28pm UTC](https://discuss.elastic.co/t/no-configuration-found-in-the-configured-sources/258029/5 "2021-01-07T14:28:36Z")

</div>

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