If there is a /etc/systemd/system/influxdb/file.conf that defines Environment=“INFLUXDB_HTTP_BIND_ADDRESS=127.0.0.1:8086” but /etc/influxdb/influxdb.conf defines both enabled = true and bind-address = “0.0.0.0:8086” in the [http] section of the /etc/systemd/system/influxdb/file.conf, the Environment parameter overrides the /etc/influxdb/influxdb.conf parameters. The reason this is a problem for me is that one of my applications defines the Environment parameter yet that affects all other programs that attempt to access this influxdb database. So when and if the one application decided to overwrite /etc/systemd/system/influxdb/file.conf then the connection is lost for other application. In other applications the, it seems the /etc/influxdb/influxdb.conf would take preference. Is this reasonable for influxdb or is there other considerations that make /etc/influxdb/influxdb.conf take preference undesirable?
Hmm I’m not sure I entirely understand your question.
Why are other applications overwriting the file.conf?
But yes usually the config for influxdb is influxdb.conf not file.conf. I can’t think of something that would make that undesirable.
the application that initially established the influxdb might change the Environmental parameter in its normal updates. It may be just an overwrite of that file. To be able to interrogate that same database with Grafana, I need access from a remote computer. Yes I can always go back and change it (assuming I remember what the solution to the access problem is) on the server. That is why I wanted to have the /etc/influxdb/influxdb.conf that defines both enabled = true and bind-address = “0.0.0.0:8086” as the controlling entity. But there may be other reasons why influxdb is not setup that way. Which is why I asked the question I did.