-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RPC] Can not start relayer #756
Comments
I have not gotten a response for this either. |
looking. thanks. |
I tried again today. Every time I run below sequentially: sudo systemctl kill sequencer; sudo systemctl kill relayer
systemctl disable relayer; systemctl disable sequencer
roller config set hub-rpc "<rpc-url-with-port>"
systemctl enable relayer; systemctl enable sequencer
sudo systemctl start sequencer; sudo journalctl -fu sequencer.service
sudo systemctl start relayer; sudo journalctl -fu relayer.service . With https://rpc.dymension-froopyland-2.silentvalidator.com:443
https://froopyland.rpc.silknodes.io:443
https://rpc-dymension-testnet.mzonder.com:443
https://jsonrpc.dymension.nodestake.org:443
https://froopyland.blockpi.network:443/rpc/v1/public , the error occurs about the
With https://jsonrpc-dymension.mzonder.com:443
https://dymension-evm.blockpi.network:433/v1/rpc/public , the error occurs about the
Maybe the above information could help you better. |
hi bro,have you finally solved it? Is there a stable rpc? |
Still bricked? |
Roller version
v1.0.6-beta
OS
Ubuntu 22.04.3 LTS
Processor Architecture
x86_64
Others
No response
Steps to reproduce it
I run the commands as follows:
, where the is tried among the following URLs:
.
Expected result
After executing
, it should be
, it should be
Actual result
With the use of either one in
, it returns similarly as
after
With the same setup, it would try to restart. By using the command
, it follows
By using the command
tail -f ~/.roller/relayer/relayer.log
, it follows
With the use of
, it returns
after
With the same setup, it would try to restart. By using the command
, it follows
By using the command
tail -f ~/.roller/relayer/relayer.log
, it follows
With the use of
, it returns
With the same setup, it would try to restart. By using the command
, it follows
With the use of
, by using the command
, it follows
, which would not end.
Relevant log output
No response
Notes
No response
The text was updated successfully, but these errors were encountered: