You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When accessing the /healthz monitoring endpoint of a healthy beacon node with TLS enabled, it will always report an error for the gateway, e.g.
*powchain.Service: OK
*sync.Service: OK
*gateway.Gateway: ERROR grpc server is TRANSIENT_FAILURE
*prometheus.Service: OK
*p2p.Service: OK
*attestations.Service: OK
*blockchain.Service: OK
*initialsync.Service: OK
*rpc.Service: OK
This only occurs when TLS is enabled on a beacon node; if TLS is not enabled on the beacon node, it will correctly report on the status of the gateway.
Has this worked before in a previous version?
Have not tested in a prior version.
🔬 Minimal Reproduction
Run two different beacon nodes - one with TLS enabled and one with TLS disabled:
The node running with TLS enabled should fail to return a passing status for the gateway even when otherwise healthy, while the node without TLS will be able to return a passing status once healthy.
🔥 Error
*gateway.Gateway: ERROR grpc server is TRANSIENT_FAILURE
🌍 Your Environment
Operating System:
Ubuntu 18.04
What version of Prysm are you running? (Which release)
v1.1.0
Anything else relevant (validator index / public key)?
There doesn't appear to be any connection to validator or public keys.
The text was updated successfully, but these errors were encountered:
This is fixed in #8418. If you aren't using the gRPC gateway for JSON requests, you may disable it entirely to unblock yourself until that PR can be included in the next release. --disable-grpc-gateway
🐞 Bug Report
Description
When accessing the /healthz monitoring endpoint of a healthy beacon node with TLS enabled, it will always report an error for the gateway, e.g.
This only occurs when TLS is enabled on a beacon node; if TLS is not enabled on the beacon node, it will correctly report on the status of the gateway.
Has this worked before in a previous version?
Have not tested in a prior version.
🔬 Minimal Reproduction
Run two different beacon nodes - one with TLS enabled and one with TLS disabled:
and
The node running with TLS enabled should fail to return a passing status for the gateway even when otherwise healthy, while the node without TLS will be able to return a passing status once healthy.
🔥 Error
🌍 Your Environment
Operating System:
What version of Prysm are you running? (Which release)
Anything else relevant (validator index / public key)?
There doesn't appear to be any connection to validator or public keys.
The text was updated successfully, but these errors were encountered: