A new version is available for heimdall. This release contains all changes in v0.2.8 and sets the block height for the hard fork on Mumbai Testnet. It is a hard fork for heimdall. Please upgrade heimdall on all your Mumbai Testnet nodes before block number 10,205,000 which is expected to be mined on Wed, 30th Mar 2022 around 9 AM UTC.
These are the instructions to upgrade heimdall on your nodes:
Stop heimdall processes:
sudo service heimdalld stop sudo service heimdalld-rest-server stop sudo service heimdalld-bridge stop
Upgrade heimdall to the latest version:
cd ~/heimdall git pull git checkout v0.2.8-mumbai make install network=mumbai
You should see output like this
==================================================== ==================Build Successful================== ====================================================
Ensure that you are on the latest version:
heimdalld version # It should return # v0.2.8-mumbai
Restart heimdall services
sudo service heimdalld restart sudo service heimdalld-rest-server restart # Only on validator nodes: sudo service heimdalld-bridge restart
These are the instructions to setup telemetry for heimdall to monitor the nodes in https://heimdall-mumbai.vitwit.com/
Clone and setup the config
git clone https://github.com/vitwit/matic-telemetry.git cd matic-telemetry mkdir -p ~/.telemetry/config cp example.config.toml ~/.telemetry/config/config.toml
Update the config for your node located in
~/.telemetry/config/config.toml. Update the [stats_details] block in config.
Secret key and net stats ip will remain same as mentioned below. Update the node key with the name of your node.
[stats_details] secret_key = "heimdall_testnet" node = "<node-name>" net_stats_ip = "heimdall-mumbai.vitwit.com:3000"
Please use the following naming convention for node name:
unique_identifier is just an identifier for you to distinguish between different nodes you are running (if you have multiple nodes).
Build the binary (from the
go mod tidy go build -o telemetry mv telemetry $GOBIN
Create a service (You can use different service name to resolve conflicts with your local system if any. If you do so, make sure you use that name in subsequent commands below)
echo "[Unit] Description=Telemetry After=network-online.target [Service] User=$USER ExecStart=$(which telemetry) Restart=always RestartSec=3 LimitNOFILE=4096 [Install] WantedBy=multi-user.target" | sudo tee "/lib/systemd/system/telemetry.service"
Start the telemetry service
sudo systemctl enable telemetry.service sudo systemctl start telemetry.service
You can monitor the service using journalctl. If everything works well, it should start exporting metrics.
journalctl -u telemetry -f