Tips and Troubleshooting

  • Many times new allocations are created and allocation error is still shown.Try to use ./zbox listallocations to cross-check whether an allocation is created

  • Check your wallet balance using ./zwallet getbalance before creating an allocation and see whether you have the required amount of tokens to lock for allocation. If not having tokens use the faucet./zwallet faucet --methodName pour --input "{Pay day}"command.

Error 1-Error creating allocation: transaction_not_found: Transaction was not found on any of the sharders

Cause 1:Your write tokens has expired

Write tokens are required and locked into a write pool using a --lock flag whenever the new allocation is created. There can be an instance where you are not able to create allocation since locked write tokens have expired with the allocation.

To get the write pool information(expiry, how many locked tokens) for all allocations.

Command:

  ./zbox wp-info

Sample Response:

- id:             6c2b94419c2b94b4dd4afc4d41f25509a33bd32c6150114edaf016f54e866eb0
  balance:        0.2
  expire_at:      2021-05-06 21:12:03 +0000 UTC
  allocation_id:  6c2b94419c2b94b4dd4afc4d41f25509a33bd32c6150114edaf016f54e866eb0
  locked:         true
  blobbers:
  - blobber_id:  090dc72b647638509a02185dcc2ac031ee35117e27cd2e332e38d8445edc740d
  - balance:     0.0422620713
  - blobber_id:  3b0551d5ecea77e9c9ed77c72eb114b2345fface766ef2ac5883096e160f64d7
  - balance:     0.0422620713
  - blobber_id:  76be262c6113a3b4656c6ecf5ed6bccff3fb2d7a1952891296ccc03be87a243e
  - balance:     0.0743812465
  - blobber_id:  b94cb2f4a689d1af305550a9ee69fc561ad49e699fe265fca4dc0a6a4b66a458
  - balance:     0.0410946107
- id:             bbb902ef735d4e1c904f096ccc1e3e52d5514ded32b0cc4f3cdcdb9d77203362
  balance:        0.2
  expire_at:      2021-05-06 20:59:26 +0000 UTC
  allocation_id:  bbb902ef735d4e1c904f096ccc1e3e52d5514ded32b0cc4f3cdcdb9d77203362
  locked:         true
  blobbers:
  - blobber_id:  2efc85d6a2f36380e1e77b843cd9f4fe55668271cae4925ab38a92504176e5df
  - balance:     0.0741096832
  - blobber_id:  91684b1f9b8d0e785afab38645e5bc6e2d77619d9b26c49325e15977568c2ade
  - balance:     0.042837967
  - blobber_id:  ac808ceeeba1026fbd9d1e495508af496aacc6f11a58fd202ea9f032a2419648
  - balance:     0.0421077739
  - blobber_id:  b94cb2f4a689d1af305550a9ee69fc561ad49e699fe265fca4dc0a6a4b66a458
  - balance:     0.0409445757
​
​

For a Particular allocation write pool information use:

If there are no write tokens locked in a pool with an allocation. You can lock them using

All the tokens will be divided between allocation blobbers depending on their write price.

To unlock an expired write pool, associated with an allocation use

Cause 2:Blobber has run out of Staked Capacity

If unable to create new allocations as shown below:

Command:

Response:

To fix this issue, You must lock some tokens on the blobber. Through zbox, it can be done using the sp-lock command

You have to get the blobber id which can be found using ./zbox ls-blobberscommand. The response will output all active blobbers but here in the sample response we have mentioned one of the blobbers

Response:

Now lets use the sp-lock command with above blobber_id to lock tokens.

Command:

Response:

You can also use sp-info command for finding the stake pool info(total stake, capacity and write price) for a blobber.

Response:

To Unlock tokens from stake pool again you can use the sp-unlock command.

Cause 3: Your allocation has expired

Every allocation created using ./zbox newallocation command has an expire time .By default it is (720h0m0s) but you can specify a particular duration using an --expireflag as well. To know the expiration of the allocation use ./zbox listallocations

Sample Response:

If your allocation has expired you can finalize an expired allocation to get the unused tokens back. The command for finalizing the allocation is :

Error 2: Error in file operation: File content didn't match with uploaded file

Cause1: You didn’t lock any read tokens.

Read Tokens are required and has to be locked in a read pool to perform Zbox operations on dStorage.

If unable to download files from dstorage as shown below

Command:

Response:

You must check whether you have read tokens created. Through zbox, it can be done using the rp-info and rp-create command.

If running ./zbox rp-info shows a below response:

You have to lock some tokens using rp-lock and command .Flags for the command can be viewed using `

./zbox rp-lock --help

Sample Command:

Try executing Zbox operations again after locking read pools.

Cause 2:Your read tokens might have expired

There can be many instances where you are not able to perform Zbox operations on dStorage due to expired read pool for the allocation. Allocations are associated with a read pool which is locked using ./zbox rp-lockcommand for a certain duration as shown above. To check the read pool details for a particular allocation , the command is

Response:

Here you will be able to see the pool_id,allocations ,expiry date,locked tokens and blobbers associated with the pool.

To Unlock tokens from the expired read pool mark the pool id to the variable using:

then use the rp-unlock command.

Error 3:Not able to use read pool rp-info and rp-lock commands

This can happen if read pool is not yet created for wallet. Read pool is usually created when new wallet is created by zbox or zwallet. However, if wallet is created through zwallet recoverwallet, read pool may not have been created. Simply run zbox rp-create.

PreviousLock and Unlock TokensNextZwallet CLI

Last updated