# Error Running Logstash in Windows

**URL:** <https://discuss.elastic.co/t/error-running-logstash-in-windows/129270>\
**Category:** Logstash\
**Created:** [April 24, 2018, 9:15am UTC](https://discuss.elastic.co/t/error-running-logstash-in-windows/129270 "2018-04-24T09:15:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kannanraghupathy](https://avatars.discourse-cdn.com/v4/letter/k/c4cdca/32.png) [@kannanraghupathy](https://discuss.elastic.co/u/kannanraghupathy)\
**Post date:** [April 24, 2018, 9:15am UTC](https://discuss.elastic.co/t/error-running-logstash-in-windows/129270/1 "2018-04-24T09:15:04Z")

</div>

Hi,

I am getting the following error while I am trying to run Logstash for the first time. I am following the logstash configuration link to do the same ([https://www.elastic.co/guide/en/logstash/current/configuration.html](https://www.elastic.co/guide/en/logstash/current/configuration.html))

While running logstash -f logstash.conf (I have created the logstash.conf file under the C:\Java\logstash-6.2.4\bin folder) and getting this error.

**C:\Java\logstash-6.2.4\bin\>logstash -f logstash.conf**  
**[ERROR] 2018-04-24 14:36:24.286 [main] Logstash - java.lang.IllegalStateException: org.jruby.exceptions.RaiseException: (RuntimeError)**

\*\* you might need to reinstall the gem which depends on the missing jar or in case there is Jars.lock then resolve the jars with `lock_jars` command\*\*

**no such file to load -- /Users/kannan.pathy/.m2/repository/commons-logging/commons-logging/1.2/commons-logging-1.2 (LoadError)**

**C:\Java\logstash-6.2.4\bin\>**

Please help me resolve this issue.  
Thanks,  
KR

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 22, 2018, 9:15am UTC](https://discuss.elastic.co/t/error-running-logstash-in-windows/129270/2 "2018-05-22T09:15:18Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
