Skip to content

Log messages

Jump to bottom
Joseph Bagaric edited this page Aug 17, 2018 · 3 revisions

When running the TimeNode you may notice a lot of incoming messages (logs) shown in your terminal / dapp. Let's take a look and put more descriptions.

  • INFO [address] Discovered - this indicates that TimeNode found a transaction that is scheduled within current or next bucket. buckets are the period of time/blocks that we used to optimize discoverability (more here)

Claiming

  • INFO [address] Claiming: Skipped - Claiming disabled - this indicates that TimeNode does not have claiming enabled. In order to enabled claiming run the timenode with --claiming option.

  • INFO [address] Claiming... - this indicates that all conditions (economic conditions + pending transaction + wallet availability) are met and TimeNode is attempting to claim the transaction

  • INFO [address] CLAIMED. - this indicates that transaction has been successfully claimed

  • INFO [address] Claiming: Skipped - Other claiming found - this indicates that there is already pending claim transaction from another node with the high chance to succeed, in this case, our TimeNode is not going to try to claim and it may end up with failed transaction (with some failing cost)

  • INFO [address] Claiming: Skipped - Account is busy - this indicates that all Ethereum accounts used by TimeNode waiting for transactions to be mined thus we need to wait for their availability

  • INFO [address] Claiming: Skipped - Transaction not profitable. - this indicates that the transaction that is being claimed is not profitable for the TimeNode to claim. Bounties gained by executing this transaction are lower than the cost of claiming/execution. This setting can be adjusted using the minProfitability setting in the TimeNode Economic Strategy.

  • INFO [address] Claiming: Skipped - Not enough balance to claim. - this indicates that the balance the TimeNode has is lower than the minBalance set in the Economic Strategy. This setting can be adjusted using the minBalance setting in the TimeNode Economic Strategy.

  • INFO [address] Claiming: Skipped - The transaction deposit is too high. - this indicates that the deposit t being requested by the transaction is higher than what is set in the TimeNode settings. maxDeposit is 1 ETH by default but can be overwritten using the maxDeposit setting in the TimeNode Economic Strategy.

  • ERROR [address] Claiming: Transaction already claimed - this indicates that TimeNode attempted to claim transaction but we lost the "race" and thus our transaction failed. This happens because information about pending transactions is imperfect and is depending on node connectivity, before attempting the claiming TimeNode is checking the txpool, tx status in order to avoid such situations, still this cannot be guaranteed to have 100% success rate.

Execution

  • INFO [address] Executing... - this indicates that all conditions (pending transaction + wallet availability) are met and TimeNode is attempting to execute the transaction

  • INFO [address] EXECUTED. - this indicates that transaction has been successfully executed

  • INFO [address] Execution: Skipped - Other execution found - this indicates that there is already pending execution transaction from another node with the high chance to succeed, in this case, our TimeNode is not going to try to execute and it may end up with failed transaction (with some failing cost)

  • INFO [address] Execution: Skipped - Account is busy - this indicates that all Ethereum accounts used by TimeNode waiting for transactions to be mined thus we need to wait for their availability

Clone this wiki locally