# Stuck at Successfully started Logstash API endpoint {:port=\>9600} (can’t load data in Kibana/ElasticSearch) **URL:** \ **Category:** Logstash\ **Created:** [July 10, 2019, 4:41pm UTC](https://discuss.elastic.co/t/stuck-at-successfully-started-logstash-api-endpoint-port-9600-can-t-load-data-in-kibana-elasticsearch/189830 "2019-07-10T16:41:13Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![LL22](https://avatars.discourse-cdn.com/v4/letter/l/8c91f0/32.png) [@LL22](https://discuss.elastic.co/u/LL22)\ **Post date:** [July 10, 2019, 4:41pm UTC](https://discuss.elastic.co/t/stuck-at-successfully-started-logstash-api-endpoint-port-9600-can-t-load-data-in-kibana-elasticsearch/189830/1 "2019-07-10T16:41:13Z")
Hello, I'm new to ELK and I'm having an issue to load my data Here is my imput file (it's just to test, it won't remain that empty) > input { > file { > codec =\> json > path =\> "/home/Json\_Data/\*.json" > start\_position =\> "beginning" > sincedb\_path =\>"/dev/null" > } > } > filter{ > json { > source =\> "message" > } > } > output{ > elasticsearch > { > action =\> "index" > hosts =\> ["localhost:9200"] > index =\> "test-%{+YYYY.MM.dd}" > }stdout {} > } By running logstash i'm having the following result on terminal > sudo /usr/share/logstash/bin/logstash -f lucas.conf > Thread.exclusive is deprecated, use Thread::Mutex > WARNING: Could not find logstash.yml which is typically located in $LS\_HOME/config or /etc/logstash. You can specify the path using --path.settings. Continuing using the defaults > Could not find log4j2 configuration at path /usr/share/logstash/config/log4j2.properties. Using default config which logs errors to the console > [WARN] 2019-07-10 15:49:58.620 [LogStash::Runner] multilocal - Ignoring the 'pipelines.yml' file because modules or command line options are specified > [INFO] 2019-07-10 15:49:58.638 [LogStash::Runner] runner - Starting Logstash {"logstash.version"=\>"7.2.0"} > [INFO] 2019-07-10 15:50:07.015 [[main]-pipeline-manager] elasticsearch - Elasticsearch pool URLs updated {:changes=\>{:removed=\>, :added=\>[[http://localhost:9200/](http://localhost:9200/)]}} > [WARN] 2019-07-10 15:50:07.252 [[main]-pipeline-manager] elasticsearch - Restored connection to ES instance {:url=\>"[http://localhost:9200/](http://localhost:9200/)"} > [INFO] 2019-07-10 15:50:07.457 [[main]-pipeline-manager] elasticsearch - ES Output version determined {:es\_version=\>7} > [WARN] 2019-07-10 15:50:07.460 [[main]-pipeline-manager] elasticsearch - Detected a 6.x and above cluster: the `type` event field won't be used to determine the document \_type {:es\_version=\>7} > [INFO] 2019-07-10 15:50:07.491 [[main]-pipeline-manager] elasticsearch - New Elasticsearch output {:class=\>"LogStash::Outputs::Elasticsearch", :hosts=\>["[//localhost:9200](https://localhost:9200/)"]} > [INFO] 2019-07-10 15:50:07.562 [Ruby-0-Thread-5: :1] elasticsearch - Using default mapping template > [WARN] 2019-07-10 15:50:07.616 [[main]-pipeline-manager] LazyDelegatingGauge - A gauge metric of an unknown type (org.jruby.specialized.RubyArrayOneObject) has been create for key: cluster\_uuids. This may result in invalid serialization. It is recommended to log an issue to the responsible developer/development team. > [INFO] 2019-07-10 15:50:07.620 [[main]-pipeline-manager] javapipeline - Starting pipeline {:pipeline\_id=\>"main", "pipeline.workers"=\>8, "pipeline.batch.size"=\>125, "pipeline.batch.delay"=\>50, "pipeline.max\_inflight"=\>1000, :thread=\>"#\"} > [INFO] 2019-07-10 15:50:07.684 [Ruby-0-Thread-5: :1] elasticsearch - Attempting to install template {:manage\_template=\>{"index\_patterns"=\>"logstash- _", "version"=\>60001, "settings"=\>{"index.refresh\_interval"=\>"5s", "number\_of\_shards"=\>1}, "mappings"=\>{"dynamic\_templates"=\>[{"message\_field"=\>{"path\_match"=\>"message", "match\_mapping\_type"=\>"string", "mapping"=\>{"type"=\>"text", "norms"=\>false}}}, {"string\_fields"=\>{"match"=\>"_ ", "match\_mapping\_type"=\>"string", "mapping"=\>{"type"=\>"text", "norms"=\>false, "fields"=\>{"keyword"=\>{"type"=\>"keyword", "ignore\_above"=\>256}}}}}], "properties"=\>{"@timestamp"=\>{"type"=\>"date"}, "@version"=\>{"type"=\>"keyword"}, "geoip"=\>{"dynamic"=\>true, "properties"=\>{"ip"=\>{"type"=\>"ip"}, "location"=\>{"type"=\>"geo\_point"}, "latitude"=\>{"type"=\>"half\_float"}, "longitude"=\>{"type"=\>"half\_float"}}}}}}} > [INFO] 2019-07-10 15:50:08.053 [[main]-pipeline-manager] javapipeline - Pipeline started {"pipeline.id"=\>"main"} > [INFO] 2019-07-10 15:50:08.146 [[main]\ [INFO] 2019-07-10 15:50:08.146 [Ruby-0-Thread-1: /usr/share/logstash/lib/bootstrap/environment.rb:6] agent - Pipelines running {:count=\>1, :running\_pipelines=\>[:main], :non\_running\_pipelines=\>} > [INFO] 2019-07-10 15:50:08.522 [Api Webserver] agent - Successfully started Logstash API endpoint {:port=\>9600} I'm sure that it is reading the files, i checked it with --log.level trace. I'm just not having anything when I try to "check for new data" on Kibana ![Screenshot (2).png](https://us1.discourse-cdn.com/elastic/original/3X/b/7/b7e6f20c5a660a27ec424012f3e8053c81972e12.png) I'm working on a VM I'll be very thankful with every help you can give me since I'm on an internship and can't really start my work until i figure how to make this work 😬 Thanks in advance ---
**Author:** ![mancharagopan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mancharagopan/32/60266_2.png) [@mancharagopan](https://discuss.elastic.co/u/mancharagopan)\ **Post date:** [July 11, 2019, 1:36am UTC](https://discuss.elastic.co/t/stuck-at-successfully-started-logstash-api-endpoint-port-9600-can-t-load-data-in-kibana-elasticsearch/189830/2 "2019-07-11T01:36:58Z")
Hi LL22, By reading the logstash output you can solve most of the issues. First, you are running logstash directly from the installation directory, it failed to find your logstash.yml and log4j2.properties —\> start the logstash as service Ubuntu: Sudo service start logstash Centos: Sudo systemctl start logstash Or specify the logstash.yml config location with --path.settings Second, if you have enabled module in logstash: Module concept in logstash is in beta state and now it is moved to beats. When you enable module, your other pipeline configurations are ignored therefor your .conf files won’t be considered by logstash. —\> if you enabled module... easy way to fix is to uninstall logstash and install it from the scratch. Could you share the logstash.yml file config from /etc/logstash/logstash.yml ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 8, 2019, 1:37am UTC](https://discuss.elastic.co/t/stuck-at-successfully-started-logstash-api-endpoint-port-9600-can-t-load-data-in-kibana-elasticsearch/189830/3 "2019-08-08T01:37:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.