# V5.3 won't start on CentOS 7.3 **URL:** \ **Category:** Logstash\ **Created:** [March 28, 2017, 6:47pm UTC](https://discuss.elastic.co/t/v5-3-wont-start-on-centos-7-3/80348 "2017-03-28T18:47:24Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![gtirloni](https://avatars.discourse-cdn.com/v4/letter/g/7feea3/32.png) [@gtirloni](https://discuss.elastic.co/u/gtirloni)\ **Post date:** [March 28, 2017, 6:47pm UTC](https://discuss.elastic.co/t/v5-3-wont-start-on-centos-7-3/80348/1 "2017-03-28T18:47:24Z")
Installed logstash 5.3 from the official repository and tried to run the following command (from [https://www.elastic.co/guide/en/logstash/current/first-event.html](https://www.elastic.co/guide/en/logstash/current/first-event.html)): ``` # /usr/share/logstash/bin/logstash -e 'input { stdin { } } output { stdout {} }' OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N hello world ^C ``` Nothing happens. After starting the java process uses 100% CPU for 10-15 seconds and that's it. Nothing in /var/log/messages or /var/log/logstash. Java packages installed: java-1.8.0-openjdk-1.8.0.121-0.b13.el7\_3.x86\_64 java-1.8.0-openjdk-headless-1.8.0.121-0.b13.el7\_3.x86\_64 Any ideas about what I'm doing wrong here? ---
**Author:** ![gtirloni](https://avatars.discourse-cdn.com/v4/letter/g/7feea3/32.png) [@gtirloni](https://discuss.elastic.co/u/gtirloni)\ **Post date:** [March 28, 2017, 6:56pm UTC](https://discuss.elastic.co/t/v5-3-wont-start-on-centos-7-3/80348/2 "2017-03-28T18:56:25Z")
Also tried Oracle's JDK 1.8.0\_112 but no luck. Same behavior. I tried logstash 5.3.0 on Fedora 25 with Oracle JDK 1.8.0\_112 and it worked, so it seems the behavior is limited to CentOS. ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [March 28, 2017, 6:59pm UTC](https://discuss.elastic.co/t/v5-3-wont-start-on-centos-7-3/80348/3 "2017-03-28T18:59:22Z")
How did you install? An RPM? Did you try adding `--path.settings /etc/logstash`, since you're executing from the command-line, rather than the default systemd startup method? ---
**Author:** ![gtirloni](https://avatars.discourse-cdn.com/v4/letter/g/7feea3/32.png) [@gtirloni](https://discuss.elastic.co/u/gtirloni)\ **Post date:** [March 28, 2017, 7:36pm UTC](https://discuss.elastic.co/t/v5-3-wont-start-on-centos-7-3/80348/4 "2017-03-28T19:36:37Z")
I installed it through the RPM package ([https://artifacts.elastic.co/packages/5.x/yum](https://artifacts.elastic.co/packages/5.x/yum)). The `--path.settings` options doesn't seem to have an effect. However, after 15-20min or so, it started! I'm currently re-running with strace to try to identify what's trying to do all that time. ---
**Author:** ![gtirloni](https://avatars.discourse-cdn.com/v4/letter/g/7feea3/32.png) [@gtirloni](https://discuss.elastic.co/u/gtirloni)\ **Post date:** [March 28, 2017, 7:50pm UTC](https://discuss.elastic.co/t/v5-3-wont-start-on-centos-7-3/80348/5 "2017-03-28T19:50:29Z")
```auto # date; /usr/share/logstash/bin/logstash -e 'input { stdin { } } output { stdout {} }'; date Tue Mar 28 19:40:15 UTC 2017 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 to console 19:44:09.125 [[main]-pipeline-manager] INFO logstash.pipeline - Starting pipeline {"id"=>"main", "pipeline.workers"=>1, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>5, "pipeline.max_inflight"=>125} 19:44:09.223 [[main]-pipeline-manager] INFO logstash.pipeline - Pipeline main started The stdin plugin is now waiting for input: 19:44:09.458 [Api Webserver] INFO logstash.agent - Successfully started Logstash API endpoint {:port=>9600} abc 2017-03-28T19:45:56.075Z hostname abc ``` And specifying the path, it seems to die (with default settings, although I am specifying '-e' so this is weird): ```auto # date; /usr/share/logstash/bin/logstash --path.settings /etc/logstash -e 'input { stdin { } } output { stdout {} }'; date Tue Mar 28 19:47:27 UTC 2017 Sending Logstash's logs to /var/log/logstash which is now configured via log4j2.properties Tue Mar 28 19:49:38 UTC 2017 ``` ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [March 28, 2017, 8:01pm UTC](https://discuss.elastic.co/t/v5-3-wont-start-on-centos-7-3/80348/6 "2017-03-28T20:01:08Z")
Sounds like you're on a VM. That means you probably have insufficient entropy. [https://github.com/elastic/logstash/issues/6117](https://github.com/elastic/logstash/issues/6117) Has some workarounds. ---
**Author:** ![gtirloni](https://avatars.discourse-cdn.com/v4/letter/g/7feea3/32.png) [@gtirloni](https://discuss.elastic.co/u/gtirloni)\ **Post date:** [March 28, 2017, 8:07pm UTC](https://discuss.elastic.co/t/v5-3-wont-start-on-centos-7-3/80348/7 "2017-03-28T20:07:22Z")
I think that was exactly it! I kept the VM busy and now I'm getting a consistent \<1min startup time. Thank you! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 25, 2017, 8:07pm UTC](https://discuss.elastic.co/t/v5-3-wont-start-on-centos-7-3/80348/8 "2017-04-25T20:07:32Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.