# After upgrading Logstash to 6.4.1 It could not be started there is already another instance using the configured data directory **URL:** \ **Category:** Logstash\ **Created:** [September 26, 2018, 12:54pm UTC](https://discuss.elastic.co/t/after-upgrading-logstash-to-6-4-1-it-could-not-be-started-there-is-already-another-instance-using-the-configured-data-directory/150013 "2018-09-26T12:54:47Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![emna](https://avatars.discourse-cdn.com/v4/letter/e/3ab097/32.png) [@emna](https://discuss.elastic.co/u/emna)\ **Post date:** [September 26, 2018, 12:54pm UTC](https://discuss.elastic.co/t/after-upgrading-logstash-to-6-4-1-it-could-not-be-started-there-is-already-another-instance-using-the-configured-data-directory/150013/1 "2018-09-26T12:54:47Z")
Hi, After upgrading Logstash to version 6.4.1 using the package managers procedure bellow : [https://www.elastic.co/guide/en/logstash/current/upgrading-using-package-managers.html](https://www.elastic.co/guide/en/logstash/current/upgrading-using-package-managers.html) Logstash version has changed successfully to 6.4.1 using ./logstash -V command , but did't show up on kibana logstash list. So I enabled the debug mode on logstash.yml file and got this message Error telling me that there is more than one instance on my server : [2018-09-26T15:05:17,514][FATAL][logstash.runner] Logstash could not be started because there is already another instance using the configured data directory. If you wish to run multiple instances, you must change the "path.data" setting. [2018-09-26T15:05:17,539][ERROR][org.logstash.Logstash] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit Knowing that i did't configure multiple instances of logstash and i have only one logstash.yml file and one path.data specified in it. need your help please Thanks, Emna. ---
**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\ **Post date:** [September 26, 2018, 5:56pm UTC](https://discuss.elastic.co/t/after-upgrading-logstash-to-6-4-1-it-could-not-be-started-there-is-already-another-instance-using-the-configured-data-directory/150013/2 "2018-09-26T17:56:29Z")
Are you using a service manager to run Logstash, or are you invoking it directly on the command line? Is it possible that you have it running in a different shell, or that the service manager has one running? On Linux, it is possible to find a running process by name with `ps aux | grep -i logstash`. ---
**Author:** ![emna](https://avatars.discourse-cdn.com/v4/letter/e/3ab097/32.png) [@emna](https://discuss.elastic.co/u/emna)\ **Post date:** [September 27, 2018, 9:20am UTC](https://discuss.elastic.co/t/after-upgrading-logstash-to-6-4-1-it-could-not-be-started-there-is-already-another-instance-using-the-configured-data-directory/150013/3 "2018-09-27T09:20:43Z")
Thanks for your return 🙂 Im invoking it directly on the command line. I already tried your command and got more than one process and tried to kill the process with kill -9 command but it won't always work for me . So my current situation is that : sometimes the logstash appears on kibana and most of the time is not there and when ever it appears it has : 0 Events Ingested any help ? Thanks, Emna. ---
**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\ **Post date:** [September 27, 2018, 5:15pm UTC](https://discuss.elastic.co/t/after-upgrading-logstash-to-6-4-1-it-could-not-be-started-there-is-already-another-instance-using-the-configured-data-directory/150013/4 "2018-09-27T17:15:47Z")
My best guess is that your service manager is attempting to manage the service, so each time you kill it, the service manager brings it back up. I would advise tailing the logs to see what it is doing, and/or using your system's service manager to shut it down. ---
**Author:** ![emna](https://avatars.discourse-cdn.com/v4/letter/e/3ab097/32.png) [@emna](https://discuss.elastic.co/u/emna)\ **Post date:** [September 28, 2018, 8:45am UTC](https://discuss.elastic.co/t/after-upgrading-logstash-to-6-4-1-it-could-not-be-started-there-is-already-another-instance-using-the-configured-data-directory/150013/5 "2018-09-28T08:45:23Z")
I enabled the debug mode on logstash.yml file and tailed the log This is the result : [2018-09-28T11:13:04,148][DEBUG][logstash.runner] xpack.monitoring.elasticsearch.username: "logstash\_system" [2018-09-28T11:13:04,149][DEBUG][logstash.runner] xpack.monitoring.elasticsearch.ssl.verification\_mode: "certificate" [2018-09-28T11:13:04,149][DEBUG][logstash.runner] xpack.monitoring.elasticsearch.sniffing: false [2018-09-28T11:13:04,149][DEBUG][logstash.runner] xpack.monitoring.collection.pipeline.details.enabled: true [2018-09-28T11:13:04,149][DEBUG][logstash.runner] xpack.monitoring.collection.config.enabled: true [2018-09-28T11:13:04,149][DEBUG][logstash.runner] node.uuid: "" [2018-09-28T11:13:04,149][DEBUG][logstash.runner] --------------- Logstash Settings ------------------- [2018-09-28T11:13:04,199][DEBUG][logstash.config.source.multilocal] Reading pipeline configurations from YAML {:location=\>"/etc/logstash/pipelines.yml"} [2018-09-28T11:13:04,241][FATAL][logstash.runner] Logstash could not be started because there is already another instance using the configured data directory. If you wish to run multiple instances, you must change the "path.data" setting. [2018-09-28T11:13:04,251][ERROR][org.logstash.Logstash] java.lang.IllegalStateException: Logstash stopped processing because of an error: (SystemExit) exit i got the same result when i run this command /usr/share/logstash/bin/logstash --path.settings /etc/logstash --debug Thanks, Emna. ---
**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\ **Post date:** [September 28, 2018, 10:53pm UTC](https://discuss.elastic.co/t/after-upgrading-logstash-to-6-4-1-it-could-not-be-started-there-is-already-another-instance-using-the-configured-data-directory/150013/6 "2018-09-28T22:53:59Z")
Have you tried telling your service manager to stop the service? ---
**Author:** ![emna](https://avatars.discourse-cdn.com/v4/letter/e/3ab097/32.png) [@emna](https://discuss.elastic.co/u/emna)\ **Post date:** [October 1, 2018, 8:33am UTC](https://discuss.elastic.co/t/after-upgrading-logstash-to-6-4-1-it-could-not-be-started-there-is-already-another-instance-using-the-configured-data-directory/150013/7 "2018-10-01T08:33:51Z")
Yes i did , i used this command `systemctl stop logstash` I made sure to kill other processes using : `killall -9 --user user_name` The logstash is active and stable on kibana but like i mentioned is not ingesting any events ( 0 Events Received and 0 Events Emitted ) ---
**Author:** ![emna](https://avatars.discourse-cdn.com/v4/letter/e/3ab097/32.png) [@emna](https://discuss.elastic.co/u/emna)\ **Post date:** [October 1, 2018, 12:12pm UTC](https://discuss.elastic.co/t/after-upgrading-logstash-to-6-4-1-it-could-not-be-started-there-is-already-another-instance-using-the-configured-data-directory/150013/8 "2018-10-01T12:12:57Z")
I'm working with `6.4.1 version` for Elasticsearch , kibana and logstash but still working with a previous version for winlogbeats that i have installed on my Active directory servers. Could it be a version compatibility problem ? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 29, 2018, 12:13pm UTC](https://discuss.elastic.co/t/after-upgrading-logstash-to-6-4-1-it-could-not-be-started-there-is-already-another-instance-using-the-configured-data-directory/150013/9 "2018-10-29T12:13:08Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.