An error for start access node

[email protected]:/data/flow# VER=0.13.1
[email protected]:/data/flow# cd /data/flow
[email protected]:/data/flow# FLOW_GO_NODE_ID=cat bootstrap/public-root-information/node-id
[email protected]:/data/flow# docker run --rm \

-v /data/flow/bootstrap:/bootstrap:ro \
-v /data/flow:/data:rw \
--name flow-${VER} \
-p 62089:9000 \
gcr.io/flow-container-registry/access:v${VER} \
--bootstrapdir=/bootstrap \
--datadir=/data/protocol \
--nodeid=${FLOW_GO_NODE_ID} \
--script-addr=execution-001.mainnet4.nodes.onflow.org:3569 \
--rpc-addr=0.0.0.0:9000 \
--http-addr=0.0.0.0:8000 \
--collection-ingress-port=9000 \
--bind 0.0.0.0:3569 \
--loglevel=error

{“level”:“info”,“bind”:“0.0.0.0:3569”,“block-limit”:“1000”,“bootstrapdir”:"/bootstrap",“collection-ingress-port”:“9000”,“collection-limit”:“1000”,“datadir”:"/data/protocol",“http-addr”:“0.0.0.0:8000”,“log-tx-time-to-executed”:“false”,“log-tx-time-to-finalized”:“false”,“log-tx-time-to-finalized-executed”:“false”,“loglevel”:“error”,“metricport”:“8080”,“node-info-file”:"",“nodeid”:“debd9d96e38a84b04d48414882b7825a8a61a63d3affcb042afb9b67ce3ba3f8”,“ping-enabled”:“false”,“profiler-dir”:“profiler”,“profiler-duration”:“10s”,“profiler-enabled”:“false”,“profiler-interval”:“15m0s”,“receipt-limit”:“1000”,“retry-enabled”:“false”,“rpc-addr”:“0.0.0.0:9000”,“script-addr”:“execution-001.mainnet4.nodes.onflow.org:3569”,“static-collection-ingress-addr”:"",“timeout”:“1m0s”,“message”:“flags loaded”}
{“level”:“info”,“node_role”:“access”,“node_id”:“debd9d96e38a84b04d48414882b7825a8a61a63d3affcb042afb9b67ce3ba3f8”,“time”:“2021-02-07T10:55:08Z”,“message”:“flow access node starting up”}
{“level”:“fatal”,“node_role”:“access”,“node_id”:“debd9d96e38a84b04d48414882b7825a8a61a63d3affcb042afb9b67ce3ba3f8”,“error”:“could not read file: open /bootstrap/public-root-information/root-block.json: no such file or directory”,“time”:“2021-02-07T10:55:08Z”,“message”:“could not load root block”}

You need to get the root-block.json by running the transit script but it requires a pull token which is currently only given to whitelisted node operators (Node Validators form).

As my understanding, the access node is not used to do block validator. Why should I need follow the node validator guide? or in another way, why access node needs root-block.json which used by validator node?

While access nodes are not part of the actual running of the network, each access node still needs to be whitelisted and included in the network in order to be able to run properly. I recommend using one of the public access nodes for now until we are able to allow more access nodes.

Many thanks. Is there any introduction lists available nodes?

@yondercode Hi, I fill the validators form 10days before and still has no email tell me the progress.