[bisq-network/bisq] Adjust NetworkSize metric installer (#4004)

[Florian Reimair]

<!-- 
- make yourself familiar with the CONTRIBUTING.md if you have not already (https://github.com/bisq-network/bisq/blob/master/CONTRIBUTING.md)
- make sure you follow our [coding style guidelines][https://github.com/bisq-network/style/issues)
- pick a descriptive title
- provide some meaningful PR description below
- create the PR
- in case you receive a "Change request" and/or a NACK, please react within 30 days. If not, we will close your PR and it can not be up for compensation.
- After addressing the change request, __please re-request a review!__ Otherwise we might miss your PR as we tend to only look at pull requests tagged with a "review required".
-->

This is a work in progress.

notes to self:
cannot make the JVM fire up a jmx-service.

standin jar works
```
% jcmd 28970 PerfCounter.print
[snip]
java.rt.vmArgs="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.local.only=true -Dcom.sun.management.jmxremote.port=6969 -Dcom.sun.management.jmxremote.rmi.port=6969 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
[snip]
sun.management.JMXConnectorServer.0.authenticate="false"
sun.management.JMXConnectorServer.0.remoteAddress="service:jmx:rmi:///jndi/rmi://workstation:6969/jmxrmi"
sun.management.JMXConnectorServer.0.ssl="false"
sun.management.JMXConnectorServer.0.sslNeedClientAuth="false"
sun.management.JMXConnectorServer.0.sslRegistry="false"
sun.management.JMXConnectorServer.address="service:jmx:rmi://127.0.0.1/stub/rO0ABXNyAC5qYXZheC5tYW5hZ2VtZW50LnJlbW90ZS5ybWkuUk1JU2VydmVySW1wbF9TdHViAAAAAAAAAAICAAB4cgAaamF2YS5ybWkuc2VydmVyLlJlbW90ZVN0dWLp/tzJi+FlGgIAAHhyABxqYXZhLnJtaS5zZXJ2ZXIuUmVtb3RlT2JqZWN002G0kQxhMx4DAAB4cHc5AAtVbmljYXN0UmVmMgAADjE5Mi4xNjguOTMuMTAyAACyuWmYcsfkIQJcg+K0sQAAAXB3S81MgAIAeA=="
sun.management.JMXConnectorServer.remote.enabled=0
```
[snip]

price node does not
```
root at bisqserver ~ # /usr/lib/jvm/openjdk-10.0.2/bin/jcmd 18831 PerfCounter.print
[snip]
java.rt.vmArgs="-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.local.only=true -Dcom.sun.management.jmxremote.port=6969 -Dcom.sun.management.jmxremote.rmi.port=6969 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false"
[snip]
```

I can exclude these from the list of reasons
- java version
- using it with a .jar
- running with an unprivileged user
- is caused by service hardening

still open:
- there seems to be an embedded tomcat within the pricenode, can that be the reason? but why should it be?

I currently tend to just leave it. It takes too much efforts to find the cause. We did not have any JVM heap data on pricenodes until now, we might visit that again once it issues show up.
You can view, comment on, or merge this pull request online at:

  https://github.com/bisq-network/bisq/pull/4004

-- Commit Summary --

  * Add pricenode one-command installer script, systemd service, README
  * Adjust the pricenode installer
  * Amended pricenode readme

-- File Changes --

    M monitor/install_collectd_debian.sh (15)
    M pricenode/README.md (66)
    A pricenode/bisq-pricenode.env (3)
    A pricenode/bisq-pricenode.service (22)
    A pricenode/install_pricenode_debian.sh (90)

-- Patch Links --

https://github.com/bisq-network/bisq/pull/4004.patch
https://github.com/bisq-network/bisq/pull/4004.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/4004
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200224/1abbb375/attachment.html>