# Logstash JMX input plugin configuration error

**URL:** <https://discuss.elastic.co/t/logstash-jmx-input-plugin-configuration-error/140225>\
**Category:** Logstash\
**Created:** [July 16, 2018, 10:44pm UTC](https://discuss.elastic.co/t/logstash-jmx-input-plugin-configuration-error/140225 "2018-07-16T22:44:32Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**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:** [July 23, 2018, 6:17pm UTC](https://discuss.elastic.co/t/logstash-jmx-input-plugin-configuration-error/140225/21 "2018-07-23T18:17:43Z")

</div>

> [@vamana](#):
>
> No such directory

Does /usr/share/logstash/data exist?

---

<div class="post-metadata">

**Author:** ![vamana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vamana/32/25411_2.png) [@vamana](https://discuss.elastic.co/u/vamana)\
**Post date:** [July 23, 2018, 6:28pm UTC](https://discuss.elastic.co/t/logstash-jmx-input-plugin-configuration-error/140225/22 "2018-07-23T18:28:21Z")

</div>

Yep, this is connecting to the container:

```
~ $ docker exec -it 38ae222 /bin/bash
bash-4.2$ pwd
/usr/share/logstash
bash-4.2$ ls -l
total 164
drwxr-xr-x. 2 logstash logstash 4096 Apr 12 22:35 bin
drwxr-xr-x. 1 logstash logstash 4096 Jul 23 18:19 config
-rw-r--r--. 1 logstash logstash 2276 Apr 12 22:25 CONTRIBUTORS
drwxr-xr-x. 1 logstash logstash 4096 Jul 23 18:20 data
-rw-r--r--. 1 logstash logstash 3918 Jul 9 19:59 Gemfile
-rw-r--r--. 1 logstash logstash 21598 Jul 9 19:59 Gemfile.lock
drwxr-xr-x. 6 logstash logstash 4096 Apr 12 22:35 lib
-rw-r--r--. 1 logstash logstash 589 Apr 12 22:25 LICENSE
drwxr-xr-x. 4 logstash logstash 4096 Apr 12 22:35 logstash-core
drwxr-xr-x. 3 logstash logstash 4096 Apr 12 22:35 logstash-core-plugin-api
drwxr-xr-x. 4 logstash logstash 4096 Apr 12 22:35 modules
-rw-rw-r--. 1 logstash logstash 28122 Apr 12 22:29 NOTICE.TXT
drwxr-xr-x. 1 logstash logstash 4096 Jul 23 18:19 pipeline
drwxr-xr-x. 3 logstash logstash 4096 Apr 12 22:35 tools
drwxr-xr-x. 1 logstash logstash 4096 Apr 12 22:35 vendor
bash-4.2$ ls -l data/
total 32
drwxr-xr-x. 2 logstash logstash 4096 Jul 23 18:20 dead_letter_queue
drwxr-xr-x. 2 logstash logstash 4096 Jul 23 18:20 queue
-rw-r--r--. 1 logstash logstash 36 Jul 23 18:20 uuid
-rw-r--r--. 1 logstash logstash 172 Jul 19 01:31 zmx.conf
bash-4.2$
```

---

<div class="post-metadata">

**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:** [July 23, 2018, 6:47pm UTC](https://discuss.elastic.co/t/logstash-jmx-input-plugin-configuration-error/140225/23 "2018-07-23T18:47:04Z")

</div>

That . at the end of the permissions may indicate an alternate access method such as an access control list applies to the file. The details will depend on your OS.

---

<div class="post-metadata">

**Author:** ![vamana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vamana/32/25411_2.png) [@vamana](https://discuss.elastic.co/u/vamana)\
**Post date:** [July 23, 2018, 7:51pm UTC](https://discuss.elastic.co/t/logstash-jmx-input-plugin-configuration-error/140225/24 "2018-07-23T19:51:16Z")

</div>

ok.

I am using the logstash container from the [elastic.co](http://elastic.co) repository:  
[docker.elastic.co/logstash/logstash:6.2.4](http://docker.elastic.co/logstash/logstash:6.2.4)

If I look at the permissions of all the files in folder, including the ones that were created today it would appear they have the same permissions:

```
bash-4.2$ getfacl --all-effective data/*
# file: data/dead_letter_queue
# owner: logstash
# group: logstash
user::rwx
group::r-x
other::r-x

# file: data/queue
# owner: logstash
# group: logstash
user::rwx
group::r-x
other::r-x

# file: data/uuid
# owner: logstash
# group: logstash
user::rw-
group::r--
other::r--

# file: data/zmx.conf
# owner: logstash
# group: logstash
user::rw-
group::r--
other::r--

bash-4.2$ 

```

If I examine the permissions of the /usr/share/logstash/config/ files, which we know logstash is able to read I see the permissions are the same:

```
bash-4.2$ getfacl --all-effective data/*
# file: data/dead_letter_queue
# owner: logstash
# group: logstash
user::rwx
group::r-x
other::r-x

# file: data/queue
# owner: logstash
# group: logstash
user::rwx
group::r-x
other::r-x

# file: data/uuid
# owner: logstash
# group: logstash
user::rw-
group::r--
other::r--

# file: data/zmx.conf
# owner: logstash
# group: logstash
user::rw-
group::r--
other::r--

bash-4.2$ 

```

I didn't modify the user's permissions in the container, you can see from the Dockerfile.

Just to check for the location of the file, I moved it back to the '/usr/share/logstash/' directory again to test and I'm still seeing the same error message.

[2018-07-23T19:45:45,308][ERROR][logstash.inputs.jmx] No such file or directory - No such directory: /usr/share/logstash/zmx.conf

I understand that JMX may not be a popular plugin to use. Are there any additional restrictions I should be aware of? Does it not work in a docker image? I can try installing it on a virtual server and see if I get the same results.

---

<div class="post-metadata">

**Author:** ![vamana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vamana/32/25411_2.png) [@vamana](https://discuss.elastic.co/u/vamana)\
**Post date:** [July 24, 2018, 2:07am UTC](https://discuss.elastic.co/t/logstash-jmx-input-plugin-configuration-error/140225/25 "2018-07-24T02:07:46Z")

</div>

I do sincerely appreciate all of your efforts to assist Badger! Definitely could not have made it this far without you.

I have discovered that the only problem I had with the file not found error is my inability to read and follow the excellent documentation provided ([Jmx input plugin | Logstash Reference [8.11] | Elastic](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-jmx.html)).

> ...a directory absolute path containing json files...

I assumed it was looking for a filename not a directory. Obviously I was wrong.

After I created a jmx specific folder and dropped my config files there (as documented) I am no longer getting an error regarding the configuration of logstash but it's not emiting any events.

I'm only seeing this warning when trying to parse the jmx configuration file:

> [2018-07-24T01:54:26,415][WARN][logstash.inputs.jmx] Issue loading configuration from file {:file=\>"/usr/share/logstash/jmx/server", :exception=\>"Unexpected character ('"' (code 34)): was expecting comma to separate Object entries\n at [Source: (byte)"{\n "host" : "10.10.10.10",\n "port" : 7051,\n "username" : "user",\n "password": "pass",\n "alias" : "server.my.domain"\n "queries" : [\n {\n "object\_name" : "Catalina:type=Manager,host=localhost,context=/mywebapp1",\n "attributes" : ["activeSessions"],\n }, {\n "object\_name" : "Catalina:type=Manager,host=localhost,context=/mywebapp2",\n "attributes" : ["activeSessions"],\n }, {\n "object\_name" : "Catalina:type=Manager,host=localhost,context=/mywebapp3",\n"[truncated 308 bytes]; line: 7, column: 4]", :backtrace=\>["/usr/share/logstash/logstash-core/lib/logstash/json.rb:17:in `jruby_load'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-jmx-3.0.6/lib/logstash/inputs/jmx.rb:332:in `block in run'", "org/jruby/RubyDir.java:383:in `foreach'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-jmx-3.0.6/lib/logstash/inputs/jmx.rb:326:in `run'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:514:in `inputworker'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:507:in `block in start\_input'"]}

Any chance someone may understand what is missing?  
Maybe a second pair of eyes can confirm where the file has the incorrect syntax:

```
{
  "host" : "10.10.10.10",
  "port" : 7051,
  "username" : "user",
  "password": "pass",
  "alias" : "server.my.domain"
  "queries" : [
  {
    "object_name" : "Catalina:type=Manager,host=localhost,context=/mywebapp1",
    "attributes" : ["activeSessions"],
  }, {
    "object_name" : "Catalina:type=Manager,host=localhost,context=/mywebapp2",
    "attributes" : ["activeSessions"],
  }, {
    "object_name" : "Catalina:type=Manager,host=localhost,context=/mywebapp3",
    "attributes" : ["activeSessions"],
  }, {
    "object_name" : "Catalina:type=Manager,host=localhost,context=/mywebapp4",
    "attributes" : ["activeSessions"],
  }, {
    "object_name" : "Catalina:type=Manager,host=localhost,context=/mywebapp5"
    "attributes" : ["activeSessions"]
  } ]
}

```

---

<div class="post-metadata">

**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:** [July 24, 2018, 11:25am UTC](https://discuss.elastic.co/t/logstash-jmx-input-plugin-configuration-error/140225/26 "2018-07-24T11:25:34Z")

</div>

> [@vamana](#):
>
> "attributes" : ["activeSessions"],

There should not be a comma at the end of that line (or the 3 others like it).

---

<div class="post-metadata">

**Author:** ![vamana](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vamana/32/25411_2.png) [@vamana](https://discuss.elastic.co/u/vamana)\
**Post date:** [July 24, 2018, 5:34pm UTC](https://discuss.elastic.co/t/logstash-jmx-input-plugin-configuration-error/140225/27 "2018-07-24T17:34:23Z")

</div>

For all of the entries identifying the host, port, username, password, alias. They must also have a comma after them. All of the entries for object\_name must also have a comma when you have attributes following them.

Thanks a lot for all your help on this one!

I need to read more on the syntax utilized within the configuration files. Probably wouldn't have had as much trouble with this as I have.

---

<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:** [August 21, 2018, 5:34pm UTC](https://discuss.elastic.co/t/logstash-jmx-input-plugin-configuration-error/140225/28 "2018-08-21T17:34:25Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/logstash-jmx-input-plugin-configuration-error/140225.md?page=1)