[Action Required] Flow Testnet: Please ensure the pebble-dir flag is set correctly on the Testnet Access Node

[vishal]

Hello Testnet Access Node Operators,

Please ensure that you have the –pebble-dir flag set correctly on the Testnet Access Node - see earlier announcement.

If the pebble-dir flag is not set, it will default to /data/protocol-pebble. If you are using docker and do not have a directory mounted to /data inside the container, the data will be lost when the container restarts.

Please set pebble-dir to <your mount>/data/protocol (you can skip the `-pebble` suffix).

If you have already started the node without setting `pebble-dir` appropriately, you will have to

1. Stop the node

2. Delete the data directory.

3. Redownload the root-snapshot file

./boot-tools/transit pull -b ./bootstrap -t testnet-53 -r access --concurrency 10 --timeout 50m

4. Set the pebble-dir correctly.

5. Start the node.

If the pebble-dir is already pointing to a mounted directory, then no action is needed.

Thank you,

Flow Team

PS: this is a follow up from the previous announcement today: [Action Required] Flow Testnet: Upgrade your Testnet Access Node and EVM GW node

[gflow33]

What if you are running without docker do we need to still set this flag especially if we do not see any errors such as this

could not create pebble db (path: /data/protocol-pebble): mkdir /data: permission denied"

[vishal]

you do not have to set this flag anymore. We are in the process of deprecating this flag (pebble-dir completely and reverting to using the old datadir flag).

Announcement to follow soon.