ubuntu@ip-172-31-49-103:~$ sudo journalctl -u heimdalld-bridge.service -f
– Logs begin at Fri 2021-01-08 05:43:00 UTC. –
May 18 06:06:25 ip-172-31-49-103 bridge[3218175]: github.com/spf13/cobra.(*Command).ExecuteC(0x28902c0, 0x463bea, 0x28c91c0, 0xc000000180)
May 18 06:06:25 ip-172-31-49-103 bridge[3218175]: /home/matic/go/pkg/mod/github.com/spf13/[email protected]/command.go:914 +0x30b
May 18 06:06:25 ip-172-31-49-103 bridge[3218175]: github.com/spf13/cobra.(*Command).Execute(…)
May 18 06:06:25 ip-172-31-49-103 bridge[3218175]: /home/matic/go/pkg/mod/github.com/spf13/[email protected]/command.go:864
May 18 06:06:25 ip-172-31-49-103 bridge[3218175]: github.com/maticnetwork/heimdall/bridge/cmd.Execute()
May 18 06:06:25 ip-172-31-49-103 bridge[3218175]: /home/matic/heimdall/bridge/cmd/root.go:56 +0x31
May 18 06:06:25 ip-172-31-49-103 bridge[3218175]: main.main()
May 18 06:06:25 ip-172-31-49-103 bridge[3218175]: /home/matic/heimdall/bridge/bridge.go:6 +0x25
May 18 06:06:25 ip-172-31-49-103 systemd[1]: heimdalld-bridge.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
May 18 06:06:25 ip-172-31-49-103 systemd[1]: heimdalld-bridge.service: Failed with result ‘exit-code’.
Issue is most likely with the rabbit mq server. The data there may have gotten corrupted. Running the following solved the issue for us.
sudo service rabbitmq-server stop
mv /var/lib/rabbitmq/mnesia /var/lib/rabbitmq/mnesia-old
sudo service rabbitmq-server start
sudo service heimdalld-bridge start
Check logs to ensure bridge is running.
If all is good, you can delete the origingal mnesia directory:
sudo rm -R /var/lib/rabbitmq/mnesia-old