Skip to content
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

relayer services stopped and not resumed #1249

Open
omritoptix opened this issue Feb 8, 2025 · 1 comment
Open

relayer services stopped and not resumed #1249

omritoptix opened this issue Feb 8, 2025 · 1 comment
Assignees

Comments

@omritoptix
Copy link
Collaborator

as reported by mzonder:

ERROR   failed to fetch rollapp information from hub:  command execution failed: exit status 1, stderr: Error: post failed: Post "[https://rpc-dymension.mzonder.com:443](https://rpc-dymension.mzonder.com/)": dial tcp: lookup rpc-dymension.mzonder.com on 127.0.0.53:53: read udp 127.0.0.1:60349->127.0.0.53:53: read: connection refused
          Usage:
            dymd query rollapp show [rollapp-id] [flags]

          Examples:
          dymd query rollapp show ROLLAPP_CHAIN_ID

          Flags:
                --grpc-addr string   the gRPC endpoint to use for this chain
                --grpc-insecure      allow gRPC over insecure channels, if not TLS the server must use TLS
                --height int         Use a specific height to query state at (this can error if the node is pruning state)
            -h, --help               help for show
                --node string        <host>:<port> to Tendermint RPC interface for this chain (default "tcp://localhost:26657")
                --omit-apps          Omit the list of apps associated with the rollapp
            -o, --output string      Output format (text|json) (default "text")

          Global Flags:
                --chain-id string     The network chain ID
                --home string         directory for config and data (default "/home/allinbets/.dymension")
                --log_format string   The logging format (json|plain) (default "plain")
                --log_level string    The logging level (trace|debug|info|warn|error|fatal|panic) (default "info")
                --log_no_color        Disable colored logs
                --trace               print out full stack trace on errors
relayer.service: Deactivated successfully.
Started relayer.service - Roller relayer service.

i think thats why relayer stopped
2:09
idk why it happened
2:10
i have changed Restart=on-failure to Restart=always
in the relayer.service (edited)
2:13
roller's services management is not reliable, roller shouldnt gracefully stop the service in case of error
2:17
mb this is a part of the health agent thought

bottom line is that the system services are set to only restart on on-failure vs always.
a note is that zonder shut down the health agent. not sure if this component should restart the relayer?

@anhductn2001
Copy link

anhductn2001 commented Feb 11, 2025

I want to know if you reset hub-rpc? Because according to the code, Service Relayer is only restart when reset hub-rpc. In the unhealthy case, DA-light-client will be restarted. @omritoptix @maxzonder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants