# \[WEIRD\] Only some Pipelines in Pipelines.yml stopped working, without making any changes to the conf **URL:** \ **Category:** Logstash\ **Created:** [July 17, 2020, 8:15pm UTC](https://discuss.elastic.co/t/weird-only-some-pipelines-in-pipelines-yml-stopped-working-without-making-any-changes-to-the-conf/241719 "2020-07-17T20:15:59Z")\ **Posts on this page:** 3\ **Page:** 1
**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:** [July 17, 2020, 8:16pm UTC](https://discuss.elastic.co/t/weird-only-some-pipelines-in-pipelines-yml-stopped-working-without-making-any-changes-to-the-conf/241719/1 "2020-07-17T20:16:00Z")
Hi, In monday about half of pipelines in my pipelines.yml, stopped working. I didn make any changes to the single pipelines configurations and to pipelines.yml. When I run them separately they work, when I run them via logstash service or with the command `/usr/share/logstash/bin/logstash --path.settings /etc/logstash ` they dont. half of my pipelines are ingesting data from a database with zabbix data. the other half is ingesting data from another zabbix database. The only diference with the databases is that (the one that is not working) get more data than the other one. could this influence the logstahs behavior? ---
**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:** [July 18, 2020, 1:35am UTC](https://discuss.elastic.co/t/weird-only-some-pipelines-in-pipelines-yml-stopped-working-without-making-any-changes-to-the-conf/241719/2 "2020-07-18T01:35:22Z")
I changed the location of the postgres JDBC, from a custom location to `/usr/share/logstash/logstash-core/lib/jars` now is working but erratically, some pipelines doesnt start on schedule, and the quantity of indexed documents is not regular. I dont know why changing the path of the JDBC make it work again I dont know why they stopped working I dont know why some JDBC schedule are are behaving erratically does someone have any idea? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 15, 2020, 1:35am UTC](https://discuss.elastic.co/t/weird-only-some-pipelines-in-pipelines-yml-stopped-working-without-making-any-changes-to-the-conf/241719/3 "2020-08-15T01:35:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.