lambda_ethereum_consensus icon indicating copy to clipboard operation
lambda_ethereum_consensus copied to clipboard

Endpoint persistent term not available when calling /health the first couple of times

Open Arkenan opened this issue 1 year ago • 0 comments

Might be a configuration issue, but when first starting the node, the following error usually appears a couple of times:

ERROR 09:49:52.347 #PID<0.700.0> running BeaconApi.Endpoint (connection #PID<0.699.0>, stream id 1) terminated
Server: 172.16.0.16:4000 (http)
Request: GET /eth/v1/node/health
** (exit) an exception was raised:
    ** (RuntimeError) could not find persistent term for endpoint BeaconApi.Endpoint. Make sure your endpoint is started and note you cannot access endpoint functions at compile-time
        (lambda_ethereum_consensus 0.1.0) deps/phoenix/lib/phoenix/endpoint.ex:544: BeaconApi.Endpoint.persistent!/0
        (lambda_ethereum_consensus 0.1.0) deps/phoenix/lib/phoenix/endpoint.ex:584: BeaconApi.Endpoint.script_name/0
        (lambda_ethereum_consensus 0.1.0) lib/beacon_api/endpoint.ex:1: BeaconApi.Endpoint.call/2
        (plug_cowboy 2.7.1) lib/plug/cowboy/handler.ex:11: Plug.Cowboy.Handler.init/2
        (cowboy 2.12.0) /consensus/deps/cowboy/src/cowboy_handler.erl:37: :cowboy_handler.execute/2
        (cowboy 2.12.0) /consensus/deps/cowboy/src/cowboy_stream_h.erl:306: :cowboy_stream_h.execute/3
        (cowboy 2.12.0) /consensus/deps/cowboy/src/cowboy_stream_h.erl:295: :cowboy_stream_h.request_process/3
        (stdlib 5.2.3) proc_lib.erl:241: :proc_lib.init_p_do_apply/3 

It looks like the Endpoint is not available yet, which might be because it's the last thing to be started in the app supervisor.

Arkenan avatar May 22 '24 10:05 Arkenan