Transaction was not mined within750 seconds, please make sure your transaction was properly sent

Archive SDK
1

My token deployment on Main network timedout after 750 seconds with zos create, while the whole process was confirmed on public blockchain after 830 seconds.
Can we increase this timeout-value somehow, maybe as an argument on CLI?

2 Likes
2

Since we use the Proxy contracts, I’m not sure which contract address I can use as the token-address for my CrowdSale-Crontract.

Is this the “to”-address on Etherscan.io that is labeled with “contract”?

https://etherscan.io/tx/0xe56d6fb13da4acaba165c7d9fdaba29441feadf857d64e9bb88cdd78ebb9c219

1 Like
3

You can specify the timeout.

https://docs.zeppelinos.org/docs/cli_create.html
--timeout <timeout> timeout in seconds for each blockchain transaction (defaults to 600s)

2 Likes
4

Hi @itinance

When interacting with the contract, use the Proxy contract address.

You can always open a truffle console to test this.

5

Although I used zos create --network main --timeout 123123123123, it timedout with

Transaction was not mined within750 seconds, please make sure your transaction was properly sent. Be aware that it might still be mined!

Is there any chance to make it work longer than 750 seconds? ^^

1 Like
6

You have logged the timeout as https://github.com/zeppelinos/zos/issues/1065

1 Like
7

@abcoathup obviously this parameter is not used, as the timeout still is happening. Although I can find out the contract address later on etherscan.io, I can’t interact with zos-cli as long as no valid contract addresses are known to the tool.

I would patch my zos.mainnet.json by myself now according to the values in zos.ropsten.json, but with address values from etherscan.io.

The second attempt for the token contract went through, but still not for token sale contract.

"ncdt/NCDToken": [
  {
    "address": "0x5ac288CC5Ae7a81A01fdD5985bc6B28d4e1A736A",
    "version": "v1.3.0",
    "implementation": "0x0456Cf3Df2e4922808d6a00b0c20bA0D75E938ea",
    "admin": "0x731FE02eCa76de08EA9F1A9A68A5d863124c4D41",
    "kind": "Upgradeable"
  }
]

So I will adapt the same structure in the json-file for TokenSale-contract as well with values found on etherscan.io… Would be really cool if CLI-tool could wait until the process on-chain is completed without any timeout :slight_smile:

1 Like
8

I assume that something else is causing the timeout, e.g. 50 blocks would be approximately 750 seconds.

The gas market has been fluctuating, which doesn’t help matters.
https://ethgasstation.info/

9

My settings for gas consumtions are:

  gas: 8000000,
  gasPrice: 10000000000

Do you think, I should raise in order to avoid the timeout?

1 Like
10

It depends what the gas market is like when submitting your transaction.
I recommend looking at https://ethgasstation.info/

11

medium gasprice: 10 gwei

Although I doubled to 20 gwei, I’m constantly running into this 750 seconds timeout.

1 Like
12

I just hit the 750 seconds timeout too when attempting to deploy a sample contract.

13

Thanks for testing it, @abcoathup!

Could you add your experience also on the github issue please: https://github.com/zeppelinos/zos/issues/1065

Will give it more attention hopefully.

1 Like
14

I have executed a “addMinter”-Method in the Token contract, it was running into 750-second-timeout too, is still get mined for over 14 minutes now: https://etherscan.io/tx/0xb8c3b95fd8642c4e7245348e092eefec7fb97fc2d858f5126b7bfda52f0cdd59

1 Like
15

As of a sudden everything worked really fast. Contract deployment, creation and executing methods was done within seconds. I don’t know what happened before, but according to etherscan.io there was seemingly an airdrop happening, that flooded the transaction log. Maybe some traffic jam on the chain back then ^^

1 Like
16

Hi @itinance
It appeared to be congestion yesterday that was causing the deployment issues we both experienced. I check ethgasstation.info

There is still an underlying issue of the 750 second timeout, though glad for now it is not impacting you. (I deployed my sample contract this morning with no issues)

17

Same here :slight_smile: The underlying issue with fix 750 seconds timeout is still there as you wrote. That’s why I don’t closed my issue on GitHub regarding this. But I think it needs to my escalated to Web3

1 Like
18

I am not clear if the issue is with zos, truffle or web3. It will need some investigation to track down. So agree, it is worth keeping the issue open.

1 Like