# Cron in http\_poller still triggering after changing the pipeline configuration **URL:** \ **Category:** Logstash\ **Created:** [November 5, 2020, 7:57am UTC](https://discuss.elastic.co/t/cron-in-http-poller-still-triggering-after-changing-the-pipeline-configuration/254367 "2020-11-05T07:57:43Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![fbenaven](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fbenaven/32/78442_2.png) [@fbenaven](https://discuss.elastic.co/u/fbenaven)\ **Post date:** [November 5, 2020, 7:57am UTC](https://discuss.elastic.co/t/cron-in-http-poller-still-triggering-after-changing-the-pipeline-configuration/254367/1 "2020-11-05T07:57:43Z")
Hi, We have a pipeline configuration using some http\_poller as inputs. After changing the config from "cron" format (at '15 of all hours) to "every" (hourly basis), we see that the poller triggers hourly as intended but it also triggers at minute 15 as it was previously configured. This happens in 2 machines, one running Ubuntu and other RHEL Is the cron config cached somewhere? How can we get rid of it? We tried both restarting the service and the full machine but the issue is still there. ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/f/3f65fc40397ac926c4445ce4837f1bc077c7f7da.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/7/d7b7b5df40589740bba527441b24996d1848d978.png) In the logs we only see the new config ("every") ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/d/fde5f90a4a5ace519db54693ee7d7e603180c7aa.png) Thanks ---
**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:** [November 5, 2020, 3:41pm UTC](https://discuss.elastic.co/t/cron-in-http-poller-still-triggering-after-changing-the-pipeline-configuration/254367/2 "2020-11-05T15:41:28Z")
Are you using config.reload\_automatic, or are you restarting the logstash process. I am wondering if it is similar to [this](https://github.com/logstash-plugins/logstash-input-http_poller/issues/122) issue. ---
**Author:** ![fbenaven](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fbenaven/32/78442_2.png) [@fbenaven](https://discuss.elastic.co/u/fbenaven)\ **Post date:** [November 5, 2020, 4:21pm UTC](https://discuss.elastic.co/t/cron-in-http-poller-still-triggering-after-changing-the-pipeline-configuration/254367/3 "2020-11-05T16:21:18Z")
Thanks Badger for this. We are required to restart the process to get the config changes, they are not loaded automatically. The weird thing is that the issue remains both even if I reboot the machine and also if I remove the affected pipeline from the pipelines.yml file. I don't know what to do to clean this up ---
**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:** [November 5, 2020, 4:36pm UTC](https://discuss.elastic.co/t/cron-in-http-poller-still-triggering-after-changing-the-pipeline-configuration/254367/4 "2020-11-05T16:36:33Z")
Then I suspect that you are not running the configuration you think you are running. Can you try --log.level debug --config.debug? ---
**Author:** ![fbenaven](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fbenaven/32/78442_2.png) [@fbenaven](https://discuss.elastic.co/u/fbenaven)\ **Post date:** [November 5, 2020, 5:17pm UTC](https://discuss.elastic.co/t/cron-in-http-poller-still-triggering-after-changing-the-pipeline-configuration/254367/5 "2020-11-05T17:17:54Z")
It is reading it ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/7/17ee11e0f57850217725583770aede0a3fefc194.png) in fact it is responding to changes we are doing in that file. The problem is it is doing things that were in previous versions of that file on top of the current ones. And they are related to the previous cron config. It seems the cron config is cached somewhere and not deleted even it is not in the config file anymore ---
**Author:** ![fbenaven](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fbenaven/32/78442_2.png) [@fbenaven](https://discuss.elastic.co/u/fbenaven)\ **Post date:** [November 5, 2020, 10:34pm UTC](https://discuss.elastic.co/t/cron-in-http-poller-still-triggering-after-changing-the-pipeline-configuration/254367/6 "2020-11-05T22:34:46Z")
After reinstalling from scratch and seen that the symptoms were still there (and not believing in witches) I had to think in another possibilities. I finally discovered that a collegue of mine instantiated another logstash instance with the old config in a different environment pointing to the same elasticsearch cluster by mistake. Thanks Badger for your support and sorry ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 3, 2020, 10:34pm UTC](https://discuss.elastic.co/t/cron-in-http-poller-still-triggering-after-changing-the-pipeline-configuration/254367/7 "2020-12-03T22:34:54Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.