# Logstash 5.6 Plugin Installation Conflicts with JMX Remote Port
**URL:** https://discuss.elastic.co/t/logstash-5-6-plugin-installation-conflicts-with-jmx-remote-port/108474
**Category:** Logstash
**Created:** [November 20, 2017, 11:15pm UTC](https://discuss.elastic.co/t/logstash-5-6-plugin-installation-conflicts-with-jmx-remote-port/108474 "2017-11-20T23:15:27Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Jorn](https://discuss.elastic.co/u/Jorn)
#### Post date: [November 20, 2017, 11:15pm UTC](https://discuss.elastic.co/t/logstash-5-6-plugin-installation-conflicts-with-jmx-remote-port/108474/1 "2017-11-20T23:15:27Z")
Good afternoon all,
I'm currently chasing a scenario where our puppet config management client runs fail due to an issue installing newer versions of the logstash-output-s3 plugin. The error cited in the logstash-plugin executable cites the jmxremote.port is already in use. This seems to be occurring because the JMX remote port was already bound on the currently running logstash process. Both the logstash and logstash-plugin processes seem to share JVM\_options when run, so I cannot manage plugins without first shutting down logstash. Is there a way around this? We are using the puppet community logstash management module to be specific.
Specific Error:
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9010; nested exception is:
java.net.BindException: Address already in use (Bind failed)
Community Module:
> **[elastic/puppet-logstash](https://github.com/elastic/puppet-logstash)**
>
> puppet-logstash - Puppet module to manage Logstash
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 18, 2017, 11:15pm UTC](https://discuss.elastic.co/t/logstash-5-6-plugin-installation-conflicts-with-jmx-remote-port/108474/2 "2017-12-18T23:15:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.