2020-07-28T20:47:37.686Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}
2020-07-28T20:47:37.691Z INFO Operator email {"Address": "?????????"}
2020-07-28T20:47:37.691Z INFO Operator wallet {"Address": "?????????"}
2020-07-28T20:47:38.496Z INFO Telemetry enabled
2020-07-28T20:47:38.515Z INFO db.migration Database Version {"version": 42}
2020-07-28T20:47:39.107Z INFO preflight:localtime start checking local system clock with trusted satellites' system clock.
2020-07-28T20:47:44.973Z INFO preflight:localtime local system clock is in sync with trusted satellites' system clock.
2020-07-28T20:47:44.974Z INFO bandwidth Performing bandwidth usage rollups
2020-07-28T20:47:44.974Z INFO trust Scheduling next refresh {"after": "5h6m45.450694457s"}
2020-07-28T20:47:44.975Z INFO Node ??????????? started
2020-07-28T20:47:44.975Z INFO Public server started on [::]:28967
2020-07-28T20:47:44.975Z INFO Private server started on 127.0.0.1:7778
okay, ports really open, I used my VPS to check my home port connection.
articulateape@server:~$ nc -vz MY-IP 28967
Connection to MY-IP 28967 port [tcp/*] succeeded!
articulateape@server:~$ nc -vz MY IP 28968
Connection to MY-IP 28968 port [tcp/*] succeeded!
Not necessarily, but it’s much convenient to use the same name. The main point - it should be different from the current one, if you create it on the same machine and did not move the previous.
The name in the identity create NAME is a name for the folder. For Windows it would be %APPDATA%\Storj\Identity\NAME
Hoping I could get someone to confirm that I have things laid out correctly for a new machine that I’m planning on running two more nodes on. These will be nodes 5 and 6, and this is the first time I’ll be running more than one node on the same machine. Also for a little background, all first four nodes seem to be working properly, so what I have below is based on what I’ve done in the past…
Then what about for my storj-exporter docker commands?
sudo docker run -d --link=storagenode1 --name=storj-exporter1 -p 9651:9651 anclrii/storj-exporter:latest
sudo docker run -d --link=storagenode2 --name=storj-exporter2 -p 9652:9652 anclrii/storj-exporter:latest
And lastly, my promethus.yml (truncated with only target info listed):
static_configs:
Notice that in -p 9652:9651 the internal exporter port is always 9651. Also if storagenode container has a different name you might need to override STORJ_HOST_ADDRESS as well.
so then in prometheus.yml file, would that storagenode2 have a target of IP:9651 or IP:9652?
BTW, have you have ever considered registering as a content creator with Brave and connecting it to your github page? I ventured over the other day to send a tip your way, but it said you weren’t registered. Just thought I’d ask, as I know you have many places where you have a “donate” option listed.
It’s still 9652 in prometheus. Basically the script inside every exporter container listens on port 9651, but we can’t expose the same port for multiple containers or processes. With -p 9651:9651 docker will expose this internal port on host port 9651. With -p 9652:9651 docker will expose 9652 instead.
Personally I use docker-compose to have all containers from one storagenode within the same configuration file and network. Then I don’t need to expose any ports either and in the prometheus.yml I can use the container name because I connect all of them to a prometheus network (because I start prometheus with docker-compose too):
