Here are some questions that usually get asked by the community.
What is a minimal test of localnet using the Powergate CLI?¶
$ <generate or use a ~10MB “new” file> $ pow ffs -t 9d9f2fb8-c559-4394-98c9-12b2144124fc stage new > Success! Staged asset in FFS hot storage with cid: QmSKfdYojdncCkq7FCnhATvzPrtS4HSdQno7TxTKTgegFt $ pow ffs -t 9d9f2fb8-c559-4394-98c9-12b2144124fc config push QmSKfdYojdncCkq7FCnhATvzPrtS4HSdQno7TxTKTg > Success! Pushed cid storage config for QmSKfdYojdncCkq7FCnhATvzPrtS4HSdQno7TxTKTgegFt to FFS with job id: e2 $ pow ffs -t 9d9f2fb8-c559-4394-98c9-12b2144124fc log QmSKfdYojdncCkq7FCnhATvzPrtS4HSdQno7TxTKTgegFt > 2020-09-28T09:12:15 - Pushing new configuration... > 2020-09-28T09:12:15 - Configuration saved successfully > 2020-09-28T09:12:15 - Executing job e27f1366-f3d0-484d-a0b3-b3abe71c150c... > 2020-09-28T09:12:15 - Ensuring Hot-Storage satisfies the configuration... > 2020-09-28T09:12:15 - Hot-Storage execution ran successfully. > 2020-09-28T09:12:15 - Ensuring Cold-Storage satisfies the configuration... > 2020-09-28T09:12:15 - Current replication factor is lower than desired, making 1 new deals... > 2020-09-28T09:12:15 - Calculating piece size... > 2020-09-28T09:12:16 - Estimated piece size is 16777216 bytes. > 2020-09-28T09:12:16 - Proposing deal to miner t01000 with 500000000 attoFIL per epoch... > 2020-09-28T09:12:17 - Watching deals unfold... > 2020-09-28T09:12:47 - Deal with miner t01000 changed state to StorageDealSealing > 2020-09-28T09:14:47 - Deal 2 with miner t01000 is active on-chain > 2020-09-28T09:14:47 - Cold-Storage execution ran successfully. > 2020-09-28T09:14:47 - Job e27f1366-f3d0-484d-a0b3-b3abe71c150c execution finished with status Success.
Why is my custom StorageConfig being ignored?¶
In SR2 we're using a custom miner-selector strategy by default: SR2-MinerSelector.
Every time Powergate needs to create a deal, it will fetch this JSON file, and it will take
amount miners at random from each region and make deals with them.
This list is maintained by the Slingshot team to include miners that should be reasonably reliable to increase the odds of deal success. Powergate fetches this file every time it needs to do a deal. It will always select miners from the most up to date version of it.
As you can notice, if you set
RepFactor in your storage config those will be ignored by Powergate. If you want full control using your StorageConfig, you can run
--ffsminerselector="reputation" (or env
POWD_FFSMINERSELECTOR) which switches to the previous unopinionated miner selector strategy used before SR2.
I see a log error
miner XXX not in ask-cache and query-ask errored:, what does this mean?¶
This usually means two possible problems: - The targeted miners don't exist in the network, or your Lotus node is not completely synced. - Your Lotus node doesn't have connectivity with them to query ask their storage price.
In most cases, if the miner or your Lotus node are in China there might be reachability challenges related to the second bullet point. If you're not using any custom config and just the SR2 miner selector using the remote JSON file and experiencing problems reaching some of that miners, please report this in a support channel since we should understand why that particular miner might have problems for your Lotus node.
When I start Powergate, I see a fatal error:
verifying sr2 url content: getting miners list from url: Get https://xxxxx, what does this mean?¶
Since Powergate is now using SR2 miner selector by default, when it starts quickly checks if the miners JSON file is reachable. This file is located in Github, so it usually should be highly available. Some Powergate community members running Powergate from China had experienced these exact problems since there might be constraints in fetching this file from Github.
You can override this URL by specifying the flag/env
POWD_FFSMINERSELECTORPARAMS with any URL that might be reachable from your location.
I see a log error
computing commP failed: generating CommP: blockstore: block not found, what does this mean?¶
This is a sign of your Lotus node not being properly configured to use
go-ipfs from Powergate as the underlying blockstore to find and store data.
You should configure the following in your Lotus
[Client] UseIpfs = true IpfsMAddr = "/ip4/127.0.0.1/tcp/5001" IpfsUseForRetrieval = true
Note that if you are running the Powergate stack with
make up, this is already wired automatically.
pow ffs log commands mention an error
... adding markets funds failed:, how can I fix this?¶
You should check that your FFS wallet address used for making deals has enough funds.
What does the following log error mean:
rpc go-jsonrpc: xxxx?¶
Usually, this is related to a reported issue. As a solution, Powergate switched to another style of connecting to Lotus which is more reliable and avoids that problem to get in the way. You could ignore those errors since Powergate is not relying on the Lotus client to have stable connections now. Whenever you see those errors not impacting other logs related to powergate screaming other business errors, you should be fine; if that isn't the case please report in a support channel.
We preferred not to completely hide errors this external package just in case we discover new problems.
I've made a deal in Mainnet/Testnet/SR2, how can I know everything is working okay?¶
We recommend using the
pow ffs -t <ffs-token> log <pushed-cid> which provides a human-friendy output.
Creating deals on any Filecoin network can take more than 10hrs in the usual case, and many things can go wrong since Powergate is being relatively open to miners that provide storage in the network, so they might go offline at any time, be unreliable, or have network problems.
I see a log error
already tracking identifier: <cid>, what should I do?¶
Please refer to this Slack thread.